CROWDB
CROWDB / DEPLOYMENT

Chunk layer

Bring up DiskIO, DiskDB and ChunkDB after Group 0.

Development preview · not production-ready

Start with a healthy KV cluster. Each storage service needs its own absolute configuration, workspace and launch-registry entry. Group 0 owns disk groups, ownership and bindings; local launch policy must not be used as a topology fallback.

Prepare service configuration

Copy the tracked templates, assign distinct listener addresses and instance IDs, then point every Group 0 seed at reachable KV management URLs. DiskIO uses [group0].kv_seeds; DiskDB and ChunkDB use [server].kv_server_mgmt_seeds. Keep durable DiskIO and DiskDB data under their own mounted or backed-up workspaces.

cp app/crowdb-diskio/conf/crowdb_diskio_config.toml /srv/crowdb/diskio.toml
cp app/crowdb-diskdb/conf/crowdb_diskdb_config.toml /srv/crowdb/diskdb.toml
cp app/crowdb-chunkdb/conf/crowdb_chunkdb_config.toml /srv/crowdb/chunkdb.toml

Add diskio, diskdb and chunkdb launch records using the format in the KV launch example. Set each binary_path to the matching built executable, service_config_path to its edited TOML, and a distinct workspace. Do not pass another --config in args; the launcher supplies it.

Start and check registrations

Start DiskIO first, then DiskDB, then ChunkDB. DiskDB must see DiskIO ownership before reporting ready. The following commands control local launch policy and then read live service registrations from Group 0.

pixi run -- target/release/crowdb-cli --registry /srv/crowdb/launches.toml chunk stub diskio deploy --node 1
pixi run -- target/release/crowdb-cli --registry /srv/crowdb/launches.toml chunk diskdb deploy --node 1
pixi run -- target/release/crowdb-cli --registry /srv/crowdb/launches.toml chunk stub chunkdb deploy --node 1
pixi run -- target/release/crowdb-cli --registry /srv/crowdb/launches.toml chunk stub diskio list
pixi run -- target/release/crowdb-cli --registry /srv/crowdb/launches.toml chunk diskdb list
pixi run -- target/release/crowdb-cli --registry /srv/crowdb/launches.toml chunk stub chunkdb list

Use the edited HTTP listen addresses for curl -f http://HOST:PORT/ready on DiskDB and ChunkDB. A running PID alone is insufficient: require the expected live Group 0 registrations and bindings before sending data.

Current boundary

Disk-group and disk creation now use confirmed Group 0 console operations. Owner and binding setup still needs operator verification for the intended layout. This page verifies process configuration and registration, not a production storage layout or a complete bare-metal data-path deployment. Do not put valuable data on this setup. Continue to data access only after the storage topology and readiness checks are satisfied.