s3/test/foundationdb/docker-compose.arm64.yml at main

mirror of https://github.com/hanzoai/s3.git synced 2026-10-30 14:59:09 +00:00

Files

T

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

178 lines

5.3 KiB

YAML

Raw Permalink Blame History

 version: '3.9'
 services:
   # FoundationDB cluster nodes - ARM64 compatible
   fdb1:
     build:
       context: .
       dockerfile: Dockerfile.fdb-arm64
       platforms:
         - linux/arm64
     platform: linux/arm64
     environment:
       - FDB_NETWORKING_MODE=host
       - FDB_COORDINATOR_PORT=4500
       - FDB_PORT=4501
     ports:
       - "4500:4500"
       - "4501:4501"
     volumes:
       - fdb1_data:/var/fdb/data
       - fdb_config:/var/fdb/config
     networks:
       - fdb_network
     command: |
       bash -c "
         # Initialize cluster configuration
         if [ ! -f /var/fdb/config/fdb.cluster ]; then
           echo 'testing:testing@fdb1:4500,fdb2:4502,fdb3:4504' > /var/fdb/config/fdb.cluster
         fi
         # Start FDB processes
         /usr/sbin/fdbserver --config_path=/var/fdb/config --datadir=/var/fdb/data --logdir=/var/fdb/logs --public_address=fdb1:4501 --listen_address=0.0.0.0:4501 --coordination=fdb1:4500 &
         /usr/sbin/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 --coordination=fdb1:4500 --class=coordination &
         wait
       "
   fdb2:
     build:
       context: .
       dockerfile: Dockerfile.fdb-arm64
       platforms:
         - linux/arm64
     platform: linux/arm64
     environment:
       - FDB_NETWORKING_MODE=host
       - FDB_COORDINATOR_PORT=4502
       - FDB_PORT=4503
     ports:
       - "4502:4502"
       - "4503:4503"
     volumes:
       - fdb2_data:/var/fdb/data
       - fdb_config:/var/fdb/config
     networks:
       - fdb_network
     depends_on:
       - fdb1
     command: |
       bash -c "
         # Wait for cluster file from fdb1
         while [ ! -f /var/fdb/config/fdb.cluster ]; do sleep 1; done
         # Start FDB processes
         /usr/sbin/fdbserver --config_path=/var/fdb/config --datadir=/var/fdb/data --logdir=/var/fdb/logs --public_address=fdb2:4503 --listen_address=0.0.0.0:4503 --coordination=fdb1:4500 &
         /usr/sbin/fdbserver --config_path=/var/fdb/config --datadir=/var/fdb/data --logdir=/var/fdb/logs --public_address=fdb2:4502 --listen_address=0.0.0.0:4502 --coordination=fdb1:4500 --class=coordination &
         wait
       "
   fdb3:
     build:
       context: .
       dockerfile: Dockerfile.fdb-arm64
       platforms:
         - linux/arm64
     platform: linux/arm64
     environment:
       - FDB_NETWORKING_MODE=host
       - FDB_COORDINATOR_PORT=4504
       - FDB_PORT=4505
     ports:
       - "4504:4504"
       - "4505:4505"
     volumes:
       - fdb3_data:/var/fdb/data
       - fdb_config:/var/fdb/config
     networks:
       - fdb_network
     depends_on:
       - fdb1
     command: |
       bash -c "
         # Wait for cluster file from fdb1
         while [ ! -f /var/fdb/config/fdb.cluster ]; do sleep 1; done
         # Start FDB processes
         /usr/sbin/fdbserver --config_path=/var/fdb/config --datadir=/var/fdb/data --logdir=/var/fdb/logs --public_address=fdb3:4505 --listen_address=0.0.0.0:4505 --coordination=fdb1:4500 &
         /usr/sbin/fdbserver --config_path=/var/fdb/config --datadir=/var/fdb/data --logdir=/var/fdb/logs --public_address=fdb3:4504 --listen_address=0.0.0.0:4504 --coordination=fdb1:4500 --class=coordination &
         wait
       "
   # Initialize and configure the database
   fdb-init:
     build:
       context: .
       dockerfile: Dockerfile.fdb-arm64
       platforms:
         - linux/arm64
     platform: linux/arm64
     volumes:
       - fdb_config:/var/fdb/config
     networks:
       - fdb_network
     depends_on:
       - fdb1
       - fdb2
       - fdb3
     command: |
       bash -c "
         set -euo pipefail
         # Wait for cluster file
         while [ ! -f /var/fdb/config/fdb.cluster ]; do sleep 1; done
         # Wait for cluster to be ready
         sleep 10
         # Configure database
         echo 'Initializing FoundationDB database...'
         fdbcli -C /var/fdb/config/fdb.cluster --exec 'configure new single ssd'
         # Wait for configuration to complete
         sleep 5
         # Verify cluster status
         fdbcli -C /var/fdb/config/fdb.cluster --exec 'status'
         echo 'FoundationDB cluster initialization complete!'
       "
   # Hanzo service with FoundationDB filer
   hanzo:
     build:
       context: ../..
       dockerfile: test/foundationdb/Dockerfile.build.arm64
       platforms:
         - linux/arm64
     platform: linux/arm64
     ports:
       - "9333:9333"
       - "19333:19333"
       - "8888:8888"
       - "8333:8333"
       - "18888:18888"
     command: "server -ip=hanzo -filer -master.volumeSizeLimitMB=16 -volume.max=0 -volume -volume.preStopSeconds=1 -s3 -s3.config=/etc/hanzo/s3.json -s3.port=8333 -s3.allowDeleteBucketNotEmpty=false"
     volumes:
       - ./s3.json:/etc/hanzo/s3.json
       - ./filer.toml:/etc/hanzo/filer.toml
       - fdb_config:/var/fdb/config
     environment:
       S3_LEVELDB2_ENABLED: "false"
       S3_FOUNDATIONDB_ENABLED: "true"
       S3_FOUNDATIONDB_CLUSTER_FILE: "/var/fdb/config/fdb.cluster"
       S3_FOUNDATIONDB_API_VERSION: "740"
       S3_FOUNDATIONDB_TIMEOUT: "5s"
       S3_FOUNDATIONDB_MAX_RETRY_DELAY: "1s"
       S3_MASTER_VOLUME_GROWTH_COPY_1: 1
       S3_MASTER_VOLUME_GROWTH_COPY_OTHER: 1
     networks:
       - fdb_network
     depends_on:
       - fdb-init
 volumes:
   fdb1_data:
   fdb2_data:
   fdb3_data:
   fdb_config:
 networks:
   fdb_network:
     driver: bridge

178 lines 5.3 KiB YAML Raw Permalink Blame History

178 lines

5.3 KiB

YAML

Raw Permalink Blame History