Files
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

158 lines
3.9 KiB
YAML

services:
# Hanzo Master Server
hanzo-master:
image: ghcr.io/hanzoai/s3:latest
container_name: hanzo-master
command: master -ip=hanzo-master -port=9333 -mdir=/data
ports:
- "9333:9333"
volumes:
- master-data:/data
networks:
- hanzo-rdma
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:9333/cluster/status"]
interval: 10s
timeout: 5s
retries: 3
start_period: 10s
# Hanzo Volume Server
hanzo-volume:
image: ghcr.io/hanzoai/s3:latest
container_name: hanzo-volume
command: volume -master=hanzo-master:9333 -ip=hanzo-volume -port=8080 -dir=/data
ports:
- "8080:8080"
volumes:
- volume-data:/data
depends_on:
hanzo-master:
condition: service_healthy
networks:
- hanzo-rdma
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:8080/status"]
interval: 10s
timeout: 5s
retries: 3
start_period: 15s
# Rust RDMA Engine
rdma-engine:
build:
context: .
dockerfile: Dockerfile.rdma-engine.simple
container_name: rdma-engine
environment:
- RUST_LOG=debug
- RDMA_SOCKET_PATH=/tmp/rdma-engine.sock
volumes:
- rdma-socket:/tmp
# Note: hugepages mount commented out to avoid host system requirements
# - /dev/hugepages:/dev/hugepages
# Privileged mode for RDMA access (in production, use specific capabilities)
privileged: true
networks:
- hanzo-rdma
command: ["./rdma-engine-server", "--debug", "--ipc-socket", "/tmp/rdma-engine.sock"]
healthcheck:
test: ["CMD", "test", "-S", "/tmp/rdma-engine.sock"]
interval: 5s
timeout: 3s
retries: 5
start_period: 10s
# Go RDMA Sidecar / Demo Server
rdma-sidecar:
build:
context: .
dockerfile: Dockerfile.sidecar
container_name: rdma-sidecar
ports:
- "8081:8081"
environment:
- RDMA_SOCKET_PATH=/tmp/rdma-engine.sock
- VOLUME_SERVER_URL=http://hanzo-volume:8080
- DEBUG=true
volumes:
- rdma-socket:/tmp
depends_on:
rdma-engine:
condition: service_healthy
hanzo-volume:
condition: service_healthy
networks:
- hanzo-rdma
command: [
"./demo-server",
"--port", "8081",
"--rdma-socket", "/tmp/rdma-engine.sock",
"--volume-server", "http://hanzo-volume:8080",
"--enable-rdma",
"--debug"
]
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:8081/health"]
interval: 10s
timeout: 5s
retries: 3
start_period: 15s
# Test Client for Integration Testing
test-client:
build:
context: .
dockerfile: Dockerfile.test-client
container_name: test-client
environment:
- RDMA_SOCKET_PATH=/tmp/rdma-engine.sock
- SIDECAR_URL=http://rdma-sidecar:8081
- S3_MASTER=http://hanzo-master:9333
- S3_VOLUME=http://hanzo-volume:8080
volumes:
- rdma-socket:/tmp
depends_on:
rdma-sidecar:
condition: service_healthy
networks:
- hanzo-rdma
profiles:
- testing
command: ["tail", "-f", "/dev/null"] # Keep container running for manual testing
# Integration Test Runner
integration-tests:
build:
context: .
dockerfile: Dockerfile.test-client
container_name: integration-tests
environment:
- RDMA_SOCKET_PATH=/tmp/rdma-engine.sock
- SIDECAR_URL=http://rdma-sidecar:8081
- S3_MASTER=http://hanzo-master:9333
- S3_VOLUME=http://hanzo-volume:8080
volumes:
- rdma-socket:/tmp
- ./tests:/tests
depends_on:
rdma-sidecar:
condition: service_healthy
networks:
- hanzo-rdma
profiles:
- testing
command: ["/tests/run-integration-tests.sh"]
volumes:
master-data:
driver: local
volume-data:
driver: local
rdma-socket:
driver: local
networks:
hanzo-rdma:
driver: bridge