Files
s3/test/foundationdb/docker-compose.simple.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

101 lines
3.0 KiB
YAML

version: '3.9'
services:
# Simple single-node FoundationDB for testing
foundationdb:
image: foundationdb/foundationdb:7.1.61
platform: linux/amd64 # Force amd64 platform
container_name: foundationdb-single
environment:
- FDB_NETWORKING_MODE=host
ports:
- "4500:4500"
volumes:
- fdb_data:/var/fdb/data
- fdb_config:/var/fdb/config
networks:
- test_network
healthcheck:
test: ["CMD", "fdbcli", "-C", "/var/fdb/config/fdb.cluster", "--exec", "status"]
interval: 5s
timeout: 3s
retries: 10
start_period: 20s
command: >
bash -c "
echo 'Starting FoundationDB single node...' &&
echo 'docker:docker@foundationdb:4500' > /var/fdb/config/fdb.cluster &&
# Start the server
/usr/bin/fdbserver --config_path=/var/fdb/config --datadir=/var/fdb/data --logdir=/var/fdb/logs --public_address=foundationdb:4500 --listen_address=0.0.0.0:4500 --class=storage &
# Wait a moment for server to start
sleep 10 &&
# Configure the database
echo 'Configuring database...' &&
fdbcli -C /var/fdb/config/fdb.cluster --exec 'configure new single memory' &&
echo 'FoundationDB ready!' &&
fdbcli -C /var/fdb/config/fdb.cluster --exec 'status' &&
# Keep running
wait
"
# Test runner with Go environment and FoundationDB dependencies
test-runner:
build:
context: ../..
dockerfile: test/foundationdb/Dockerfile.test
depends_on:
foundationdb:
condition: service_healthy
volumes:
- fdb_config:/var/fdb/config
- test_results:/test/results
networks:
- test_network
environment:
- FDB_CLUSTER_FILE=/var/fdb/config/fdb.cluster
- S3_FOUNDATIONDB_ENABLED=true
- S3_FOUNDATIONDB_CLUSTER_FILE=/var/fdb/config/fdb.cluster
- S3_FOUNDATIONDB_API_VERSION=740
command: >
bash -c "
echo 'FoundationDB is ready, starting tests...' &&
echo 'Testing FoundationDB connection...' &&
fdbcli -C /var/fdb/config/fdb.cluster --exec 'status' &&
echo 'Running integration tests...' &&
cd /app/test/foundationdb &&
# Run validation tests (always work)
echo '=== Running Validation Tests ===' &&
go test -v ./validation_test.go &&
# Run mock tests (always work)
echo '=== Running Mock Integration Tests ===' &&
go test -v ./mock_integration_test.go &&
# Try to run actual integration tests with FoundationDB
echo '=== Running FoundationDB Integration Tests ===' &&
go test -tags foundationdb -v . 2>&1 | tee /test/results/integration_test_results.log &&
echo 'All tests completed!' &&
echo 'Results saved to /test/results/' &&
# Keep container running for debugging
tail -f /dev/null
"
volumes:
fdb_data:
fdb_config:
test_results:
networks:
test_network:
driver: bridge