Files
s3/test/foundationdb/docker-compose.build.yml
zeekayandHanzo Dev af0f387bbe Remove weed and SeaweedFS naming from the tree
The binary is s3 and the product is Hanzo S3; the rest of the tree now
says so too.

- Environment: WEED_* and SEAWEEDFS_* are S3_*, no aliases. fla9's flag
  prefix is S3, matching viper's existing "s3" prefix, so the S3_S3_SSE_*
  names mini.go exports are the ones viper reads (WEED_S3_SSE_KEK was never
  seen once viper moved to "s3").
- Java and Hadoop: packages, fs.hanzofs.* keys and the hanzofs:// scheme
  under the hanzofs namespace the protos already declare; classes take a
  neutral Filer prefix and file names match them again (the earlier pass left
  Seas3*.java holding Seaweed* classes). Client, hdfs3, examples, s3copier,
  random_access and the Spark tests compile.
- Helm chart: helpers are hanzo.*, values live under global.s3; the chart
  renders and lints, which it did not before.
- Terraform: the s3.service.tftpl reference matches the file; 12/12 render
  tests pass. Config paths point at /etc/hanzo, which the binary reads.
- loadtest.pb.go regenerated from loadtest.proto.
- Upstream logo, sponsor images and unreferenced diagrams removed from note/.

Kept: NOTICE attribution, LICENSE, the erasure-coding fixture
s3/storage/erasure_coding/1.dat (test bytes), and unmaintained/ and
third_party/ (vendored). No on-disk format, wire protocol or metadata key
changed.

Co-authored-by: Hanzo Dev <[email protected]>
2026-10-02 08:06:48 -07:00

102 lines
3.0 KiB
YAML

version: '3.9'
services:
# Build Hanzo with FoundationDB support
hanzo-fdb-builder:
build:
context: ../.. # Build from hanzo root
dockerfile: test/foundationdb/Dockerfile.build
image: hanzo:foundationdb
container_name: hanzo-fdb-builder
volumes:
- hanzo-build:/build/output
command: >
sh -c "
echo '๐Ÿ”จ Building Hanzo with FoundationDB support...' &&
cp /usr/local/bin/s3 /build/output/s3-foundationdb &&
cp /usr/local/bin/fdb_store_test /build/output/fdb_store_test &&
echo 'โœ… Build complete! Binaries saved to volume.' &&
/usr/local/bin/s3 version &&
echo '๐Ÿ“ฆ Available binaries:' &&
ls -la /build/output/
"
networks:
- fdb_network
# FoundationDB cluster for testing
fdb1:
image: foundationdb/foundationdb:7.1.61
hostname: fdb1
environment:
- FDB_NETWORKING_MODE=container
networks:
- fdb_network
volumes:
- fdb_data1:/var/fdb/data
- fdb_config:/var/fdb/config
command: >
bash -c "
echo 'docker:docker@fdb1:4500' > /var/fdb/config/fdb.cluster &&
/usr/bin/fdbserver --config_path=/var/fdb/config --datadir=/var/fdb/data --logdir=/var/fdb/logs --public_address=fdb1:4500 --listen_address=0.0.0.0:4500 --class=storage
"
# FoundationDB client for database initialization
fdb-init:
image: foundationdb/foundationdb:7.1.61
depends_on:
- fdb1
volumes:
- fdb_config:/var/fdb/config
networks:
- fdb_network
command: >
bash -c "
sleep 10 &&
echo '๐Ÿ”ง Initializing FoundationDB...' &&
fdbcli -C /var/fdb/config/fdb.cluster --exec 'configure new single memory' &&
fdbcli -C /var/fdb/config/fdb.cluster --exec 'status' &&
echo 'โœ… FoundationDB initialized!'
"
# Test the built Hanzo with FoundationDB
hanzo-test:
image: hanzo:foundationdb
depends_on:
fdb-init:
condition: service_completed_successfully
hanzo-fdb-builder:
condition: service_completed_successfully
volumes:
- fdb_config:/var/fdb/config
- hanzo-build:/build/output
networks:
- fdb_network
environment:
S3_FOUNDATIONDB_ENABLED: "true"
S3_FOUNDATIONDB_CLUSTER_FILE: "/var/fdb/config/fdb.cluster"
S3_FOUNDATIONDB_API_VERSION: "740"
S3_FOUNDATIONDB_DIRECTORY_PREFIX: "hanzo_test"
command: >
bash -c "
echo '๐Ÿงช Testing FoundationDB integration...' &&
sleep 5 &&
echo '๐Ÿ“‹ Cluster file contents:' &&
cat /var/fdb/config/fdb.cluster &&
echo '๐Ÿš€ Starting Hanzo server with FoundationDB...' &&
/usr/local/bin/s3 server -filer -master.volumeSizeLimitMB=16 -volume.max=0 &
SERVER_PID=$! &&
sleep 10 &&
echo 'โœ… Hanzo started successfully with FoundationDB!' &&
echo '๐Ÿ Integration test passed!' &&
kill $SERVER_PID
"
volumes:
fdb_data1:
fdb_config:
hanzo-build:
networks:
fdb_network:
driver: bridge