# Lab 5 stand: client -> HAProxy (lb) -> API x N (scalable service `api`) # -> PostgreSQL (metadata, jobs, outbox: source of truth) + Valkey (sessions) # + SeaweedFS S3 (staging bucket and final bucket, both private) # relay : outbox in PostgreSQL -> RabbitMQ (publisher confirms) [service `relay`] # broker : RabbitMQ 4.3, durable quorum queue + dead-letter queue [service `broker`] # worker : RabbitMQ -> variants -> final bucket + PostgreSQL, then ack [service `worker`] # From a clean clone (details and Windows notes: REPORT.md, docs/WINDOWS.md): # python scripts/init_secrets.py # once: random local credentials into ./secrets (git-ignored) # cp .env.example .env # optional overrides (API_REPLICAS, limits, ...) # docker compose --env-file .env up -d --build --wait # Order: postgres/valkey/s3/broker healthy -> migrate + s3-init (ONE run each, exit 0) # -> api healthy -> lb; relay and worker start after migrate/s3-init. # Images are pinned by version AND digest. Passwords/keys are passed only as secret files, and # every service gets only the secrets it needs. Only the LB publishes ports (loopback only). # Networks: `edge` (lb <-> api); internal (no route outside): `data` (postgres/valkey), # `storage` (s3), `queue` (broker). The API is NOT on `queue`: it never talks to the broker. name: mtusi-lab5 x-api-env: &api-env APP_ENV: ${APP_ENV:-lab} LOG_LEVEL: ${LOG_LEVEL:-info} SESSION_TTL_SECONDS: ${SESSION_TTL_SECONDS:-3600} SESSION_STORE: ${SESSION_STORE:-valkey} DATABASE_URL_FILE: /run/secrets/database_url CACHE_URL_FILE: /run/secrets/cache_url DB_POOL_MIN: ${DB_POOL_MIN:-1} DB_POOL_MAX: ${DB_POOL_MAX:-10} DB_TIMEOUT_SECONDS: ${DB_TIMEOUT_SECONDS:-3} CACHE_TIMEOUT_SECONDS: ${CACHE_TIMEOUT_SECONDS:-0.5} PASSWORD_HASH_CONCURRENCY: ${PASSWORD_HASH_CONCURRENCY:-2} IDEMPOTENCY_TTL_SECONDS: ${IDEMPOTENCY_TTL_SECONDS:-86400} # Graceful stop: 3 s drain (readiness 503, still serving) + up to 8 s for in-flight requests. DRAIN_SECONDS: ${DRAIN_SECONDS:-3} SHUTDOWN_TIMEOUT_SECONDS: ${SHUTDOWN_TIMEOUT_SECONDS:-8} DOCS_ENABLED: ${DOCS_ENABLED:-true} MESSAGE_WRITE_PATH: ${MESSAGE_WRITE_PATH:-function} # S3: the API's own key pair (Write staging + Read final, see infra/seaweedfs/start.sh). S3_ENDPOINT: ${S3_ENDPOINT:-http://s3:8333} S3_REGION: ${S3_REGION:-us-east-1} S3_BUCKET: ${S3_BUCKET:-messenger-attachments} S3_STAGING_BUCKET: ${S3_STAGING_BUCKET:-messenger-staging} S3_ACCESS_KEY_ID_FILE: /run/secrets/s3_access_key_id S3_SECRET_ACCESS_KEY_FILE: /run/secrets/s3_secret_access_key S3_TIMEOUT_SECONDS: ${S3_TIMEOUT_SECONDS:-3} MAX_UPLOAD_BYTES: ${MAX_UPLOAD_BYTES:-10485760} MAX_IMAGE_PIXELS: ${MAX_IMAGE_PIXELS:-40000000} UPLOAD_CONCURRENCY: ${UPLOAD_CONCURRENCY:-4} UPLOAD_QUEUE_TIMEOUT_SECONDS: ${UPLOAD_QUEUE_TIMEOUT_SECONDS:-5} UPLOAD_READ_TIMEOUT_SECONDS: ${UPLOAD_READ_TIMEOUT_SECONDS:-30} IMAGE_VERIFY_TIMEOUT_SECONDS: ${IMAGE_VERIFY_TIMEOUT_SECONDS:-10} IMAGE_VERIFY_CONCURRENCY: ${IMAGE_VERIFY_CONCURRENCY:-1} JPEG_MAX_MEMORY_MB: ${JPEG_MAX_MEMORY_MB:-256} PENDING_GRACE_SECONDS: ${PENDING_GRACE_SECONDS:-900} JANITOR_INTERVAL_SECONDS: ${JANITOR_INTERVAL_SECONDS:-60} # Lab 5: pipeline version and attempt budget of the jobs created by uploads. PIPELINE_VERSION: ${PIPELINE_VERSION:-1} JOB_MAX_ATTEMPTS: ${JOB_MAX_ATTEMPTS:-5} # Failure experiments only (student-tests, bench/); empty = no injected failures. FAULT_POINTS: ${API_FAULT_POINTS:-} # Settings of the pipeline shared by relay and worker (docs/PIPELINE.md). x-pipeline-env: &pipeline-env APP_ENV: ${APP_ENV:-lab} LOG_LEVEL: ${LOG_LEVEL:-info} DATABASE_URL_FILE: /run/secrets/database_url BROKER_URL_FILE: /run/secrets/broker_url DB_POOL_MAX: ${PIPELINE_DB_POOL_MAX:-6} DB_TIMEOUT_SECONDS: ${DB_TIMEOUT_SECONDS:-3} S3_ENDPOINT: ${S3_ENDPOINT:-http://s3:8333} S3_REGION: ${S3_REGION:-us-east-1} S3_BUCKET: ${S3_BUCKET:-messenger-attachments} S3_STAGING_BUCKET: ${S3_STAGING_BUCKET:-messenger-staging} S3_TIMEOUT_SECONDS: ${S3_TIMEOUT_SECONDS:-3} MAX_UPLOAD_BYTES: ${MAX_UPLOAD_BYTES:-10485760} MAX_IMAGE_PIXELS: ${MAX_IMAGE_PIXELS:-40000000} JOB_MAX_ATTEMPTS: ${JOB_MAX_ATTEMPTS:-5} JOB_TIMEOUT_SECONDS: ${JOB_TIMEOUT_SECONDS:-60} JOB_LEASE_SECONDS: ${JOB_LEASE_SECONDS:-30} JOB_RETRY_BASE_SECONDS: ${JOB_RETRY_BASE_SECONDS:-2} JOB_RETRY_MAX_SECONDS: ${JOB_RETRY_MAX_SECONDS:-60} QUEUED_REPUBLISH_SECONDS: ${QUEUED_REPUBLISH_SECONDS:-300} services: postgres: image: postgres:18.6-bookworm@sha256:afc7e2d441324c0388fa80c3d24f733b4194a4eb7f47dd8ee2b08eb1a24a647c environment: POSTGRES_USER: messenger POSTGRES_DB: messenger POSTGRES_PASSWORD_FILE: /run/secrets/postgres_password # pg_stat_statements: per-statement counters for the experiments. command: ["postgres", "-c", "shared_preload_libraries=pg_stat_statements", "-c", "max_connections=${PG_MAX_CONNECTIONS:-100}"] secrets: [postgres_password] volumes: - pgdata:/var/lib/postgresql # PostgreSQL 18 image keeps PGDATA under this path healthcheck: test: ["CMD-SHELL", "pg_isready -U messenger -d messenger -q"] interval: 2s timeout: 3s retries: 30 start_period: 10s stop_grace_period: 30s # clean shutdown checkpoint instead of crash recovery restart: unless-stopped networks: [data] deploy: resources: limits: {cpus: "${PG_CPUS:-2.0}", memory: "${PG_MEMORY:-1g}"} valkey: image: valkey/valkey:8.1.3-bookworm@sha256:fea8b3e67b15729d4bb70589eb03367bab9ad1ee89c876f54327fc7c6e618571 # The password goes into a config include readable only by the valkey user, # so it never appears in the process arguments. docker-entrypoint.sh drops root. command: - sh - -c - >- umask 077 && printf 'requirepass %s\n' "$$(cat /run/secrets/valkey_password)" > /tmp/requirepass.conf && chown valkey /tmp/requirepass.conf && exec docker-entrypoint.sh valkey-server /etc/valkey/valkey.conf secrets: [valkey_password] volumes: - ./infra/valkey/valkey.conf:/etc/valkey/valkey.conf:ro - valkeydata:/data healthcheck: test: ["CMD-SHELL", "REDISCLI_AUTH=\"$$(cat /run/secrets/valkey_password)\" valkey-cli ping | grep -q PONG"] interval: 2s timeout: 3s retries: 30 start_period: 5s restart: unless-stopped networks: [data] deploy: resources: limits: {cpus: "${VALKEY_CPUS:-0.5}", memory: 256m} # S3-compatible object storage (SeaweedFS: master + volume + filer + S3 gateway in one process). # Bytes live ONLY here, on the named volume s3data: staging bucket (originals accepted before # 202) and final bucket (published originals and variants). Identities: infra/seaweedfs/start.sh. s3: image: chrislusf/seaweedfs:4.46@sha256:08d516132314207d10c8e37cbffc1f32b147d870169688734cc61c6231625b62 entrypoint: ["/bin/sh", "/etc/seaweedfs/start.sh"] environment: S3_BUCKET: ${S3_BUCKET:-messenger-attachments} S3_STAGING_BUCKET: ${S3_STAGING_BUCKET:-messenger-staging} # Go heap target below the container limit: the GC returns memory before the cgroup OOM. GOMEMLIMIT: ${S3_GOMEMLIMIT:-600MiB} secrets: - s3_admin_access_key_id - s3_admin_secret_access_key - s3_api_access_key_id - s3_api_secret_access_key - s3_worker_access_key_id - s3_worker_secret_access_key - s3_auditor_access_key_id - s3_auditor_secret_access_key volumes: - ./infra/seaweedfs/start.sh:/etc/seaweedfs/start.sh:ro - s3data:/data healthcheck: # Unauthenticated health endpoint of the S3 gateway (200 once it serves requests). test: ["CMD", "wget", "-q", "-O", "/dev/null", "http://127.0.0.1:8333/healthz"] interval: 2s timeout: 3s retries: 30 start_period: 10s stop_grace_period: 30s restart: unless-stopped networks: [storage] deploy: resources: limits: {cpus: "${S3_CPUS:-1.0}", memory: "${S3_MEMORY:-1g}"} # Lab 5: RabbitMQ. Topology (exchange, quorum queue, DLX/DLQ) and users come from definition # files imported at boot (infra/rabbitmq, secrets/rabbitmq_users.json). Messages of the quorum # queue live on the named volume rabbitmqdata. No management UI, no host port. broker: image: rabbitmq:4.3.7-alpine@sha256:b1f997f74103d08fc1f20a13890dc44fe6cfa51d528cf521b480ada988d3ffa5 hostname: broker # node name rabbit@broker: stable across container re-creation secrets: - source: rabbitmq_users target: /etc/rabbitmq/definitions.d/users.json volumes: - ./infra/rabbitmq/rabbitmq.conf:/etc/rabbitmq/conf.d/20-lab5.conf:ro - ./infra/rabbitmq/enabled_plugins:/etc/rabbitmq/enabled_plugins:ro - ./infra/rabbitmq/topology.json:/etc/rabbitmq/definitions.d/topology.json:ro - rabbitmqdata:/var/lib/rabbitmq healthcheck: # The node runs and the AMQP listener accepts connections. test: ["CMD-SHELL", "rabbitmq-diagnostics -q ping && rabbitmq-diagnostics -q check_port_connectivity"] interval: 5s timeout: 10s retries: 30 start_period: 20s stop_grace_period: 30s restart: unless-stopped networks: [queue] deploy: resources: limits: {cpus: "${BROKER_CPUS:-1.0}", memory: "${BROKER_MEMORY:-512m}"} # One-shot schema migration: runs ONCE per `up`, before any API replica starts # (api depends_on service_completed_successfully). Replicas never migrate themselves. migrate: build: context: . args: BUILD_REVISION: ${BUILD_REVISION:-dev} image: ${API_IMAGE:-mtusi-messenger:lab5} command: ["python", "-m", "messenger.migrate"] environment: DATABASE_URL_FILE: /run/secrets/database_url secrets: [database_url] depends_on: postgres: condition: service_healthy healthcheck: disable: true restart: "no" networks: [data] deploy: resources: limits: {cpus: "0.5", memory: 256m} # One-shot, idempotent S3 bootstrap: both buckets, sentinel object, verification of the access # model (private buckets, least-privilege keys). The ONLY holder of the admin key pair besides s3. s3-init: image: ${API_IMAGE:-mtusi-messenger:lab5} command: ["python", "-m", "messenger.s3_bootstrap"] environment: S3_ENDPOINT: ${S3_ENDPOINT:-http://s3:8333} S3_REGION: ${S3_REGION:-us-east-1} S3_BUCKET: ${S3_BUCKET:-messenger-attachments} S3_STAGING_BUCKET: ${S3_STAGING_BUCKET:-messenger-staging} S3_ADMIN_ACCESS_KEY_ID_FILE: /run/secrets/s3_admin_access_key_id S3_ADMIN_SECRET_ACCESS_KEY_FILE: /run/secrets/s3_admin_secret_access_key S3_ACCESS_KEY_ID_FILE: /run/secrets/s3_api_access_key_id S3_SECRET_ACCESS_KEY_FILE: /run/secrets/s3_api_secret_access_key S3_WORKER_ACCESS_KEY_ID_FILE: /run/secrets/s3_worker_access_key_id S3_WORKER_SECRET_ACCESS_KEY_FILE: /run/secrets/s3_worker_secret_access_key S3_AUDITOR_ACCESS_KEY_ID_FILE: /run/secrets/s3_auditor_access_key_id S3_AUDITOR_SECRET_ACCESS_KEY_FILE: /run/secrets/s3_auditor_secret_access_key secrets: - s3_admin_access_key_id - s3_admin_secret_access_key - s3_api_access_key_id - s3_api_secret_access_key - s3_worker_access_key_id - s3_worker_secret_access_key - s3_auditor_access_key_id - s3_auditor_secret_access_key depends_on: s3: condition: service_healthy migrate: condition: service_completed_successfully # same image: built once by `migrate` healthcheck: disable: true restart: "no" networks: [storage] deploy: resources: limits: {cpus: "0.5", memory: 256m} api: build: context: . args: BUILD_REVISION: ${BUILD_REVISION:-dev} image: ${API_IMAGE:-mtusi-messenger:lab5} environment: *api-env secrets: - database_url - cache_url - source: s3_api_access_key_id target: s3_access_key_id - source: s3_api_secret_access_key target: s3_secret_access_key # No `ports` and no container_name: replicas are reachable only through `lb`, # and `--scale api=N` / deploy.replicas works. X-Instance-Id = container hostname. expose: ["8080"] healthcheck: test: ["CMD", "python", "-m", "messenger.healthcheck"] interval: 2s timeout: 2s retries: 3 start_period: 5s depends_on: postgres: condition: service_healthy valkey: condition: service_healthy s3: condition: service_healthy migrate: condition: service_completed_successfully s3-init: condition: service_completed_successfully stop_grace_period: 15s # > DRAIN_SECONDS + SHUTDOWN_TIMEOUT_SECONDS (11 s) restart: unless-stopped networks: [edge, data, storage] deploy: replicas: ${API_REPLICAS:-2} resources: # 512m: UPLOAD_CONCURRENCY (4) x 10 MiB bodies + one djpeg (<= JPEG_MAX_MEMORY_MB) + runtime; # measured in lab 4 (bench/upload_memory.py). No resizing happens in the API. limits: {cpus: "${API_CPUS:-1.0}", memory: "${API_MEMORY:-512m}"} # No swap on top of the limit (Docker's default would allow as much swap again): the RAM bound # of the experiments is a real bound, and running out of it is visible, not hidden in swap. memswap_limit: ${API_MEMORY:-512m} lb: image: haproxy:3.2.26-alpine@sha256:254e6370f01cd654e0744edf607c67f33777c1b6a9dc0d4b28bcba7171460122 volumes: - ./infra/haproxy/haproxy.cfg:/usr/local/etc/haproxy/haproxy.cfg:ro ports: # The ONLY public entry point, on the loopback interfaces only. Both IPv4 and IPv6: # on Windows `localhost` resolves to ::1 first, and a refused ::1 connection costs ~2 s # per request before the fallback to 127.0.0.1 (measured in lab 3: 2.0 s vs 0.007 s). - "127.0.0.1:${APP_PUBLISH_PORT:-8080}:8080" - "[::1]:${APP_PUBLISH_PORT:-8080}:8080" - "127.0.0.1:${LB_STATS_PORT:-8404}:8404" # local status page (UP/DOWN of replicas) healthcheck: # Config is valid and the process answers; whether any API is ready is the LB's own job. test: ["CMD-SHELL", "haproxy -c -q -f /usr/local/etc/haproxy/haproxy.cfg && wget -q -O /dev/null http://127.0.0.1:8404/"] interval: 5s timeout: 3s retries: 3 depends_on: api: condition: service_healthy restart: unless-stopped networks: [edge] deploy: resources: limits: {cpus: "${LB_CPUS:-1.0}", memory: 128m} # Lab 5: outbox relay + lease reaper (src/messenger/relay.py). One process; a second one would # be safe (SKIP LOCKED) but is not needed. Database + broker only, no S3 keys. relay: image: ${API_IMAGE:-mtusi-messenger:lab5} command: ["python", "-m", "messenger.relay"] environment: <<: *pipeline-env RELAY_POLL_SECONDS: ${RELAY_POLL_SECONDS:-0.5} FAULT_POINTS: ${RELAY_FAULT_POINTS:-} secrets: - database_url - source: broker_url_relay target: broker_url healthcheck: test: ["CMD", "python", "-m", "messenger.healthcheck", "--file", "/tmp/heartbeat", "--max-age", "30"] interval: 5s timeout: 3s retries: 3 start_period: 10s depends_on: postgres: condition: service_healthy broker: condition: service_healthy migrate: condition: service_completed_successfully stop_grace_period: 10s restart: unless-stopped networks: [data, queue] deploy: resources: limits: {cpus: "${RELAY_CPUS:-0.5}", memory: 256m} # Lab 5: image worker (src/messenger/worker.py). Scalable (`--scale worker=2`): competing # consumers of one queue; the database lease decides who works on a job. worker: image: ${API_IMAGE:-mtusi-messenger:lab5} command: ["python", "-m", "messenger.worker"] environment: <<: *pipeline-env S3_ACCESS_KEY_ID_FILE: /run/secrets/s3_access_key_id S3_SECRET_ACCESS_KEY_FILE: /run/secrets/s3_secret_access_key WORKER_CONCURRENCY: ${WORKER_CONCURRENCY:-2} WORKER_SHUTDOWN_SECONDS: ${WORKER_SHUTDOWN_SECONDS:-20} IMAGE_MAX_MEMORY_MB: ${IMAGE_MAX_MEMORY_MB:-768} STAGING_RETENTION_SECONDS: ${STAGING_RETENTION_SECONDS:-86400} ORPHAN_GRACE_SECONDS: ${ORPHAN_GRACE_SECONDS:-600} CLEANUP_INTERVAL_SECONDS: ${CLEANUP_INTERVAL_SECONDS:-30} FAULT_POINTS: ${WORKER_FAULT_POINTS:-} secrets: - database_url - source: broker_url_worker target: broker_url - source: s3_worker_access_key_id target: s3_access_key_id - source: s3_worker_secret_access_key target: s3_secret_access_key healthcheck: test: ["CMD", "python", "-m", "messenger.healthcheck", "--file", "/tmp/heartbeat", "--max-age", "30"] interval: 5s timeout: 3s retries: 3 start_period: 10s depends_on: postgres: condition: service_healthy broker: condition: service_healthy s3: condition: service_healthy migrate: condition: service_completed_successfully s3-init: condition: service_completed_successfully stop_grace_period: 30s # > WORKER_SHUTDOWN_SECONDS (20 s) + release restart: unless-stopped networks: [data, storage, queue] deploy: replicas: ${WORKER_REPLICAS:-1} resources: # WORKER_CONCURRENCY (2) child processes x IMAGE_MAX_MEMORY_MB (768) address space + worker. limits: {cpus: "${WORKER_CPUS:-2.0}", memory: "${WORKER_MEMORY:-1536m}"} memswap_limit: ${WORKER_MEMORY:-1536m} # Track 2: read-only checker of the pipeline invariants (database in read-only transactions, # S3 auditor key: Read + List, no Write). On demand: docker compose run --rm auditor auditor: profiles: ["tools"] image: ${API_IMAGE:-mtusi-messenger:lab5} entrypoint: ["python", "-m", "messenger.audit"] command: [] environment: DATABASE_URL_FILE: /run/secrets/database_url DB_TIMEOUT_SECONDS: ${AUDIT_DB_TIMEOUT_SECONDS:-30} S3_ENDPOINT: ${S3_ENDPOINT:-http://s3:8333} S3_REGION: ${S3_REGION:-us-east-1} S3_BUCKET: ${S3_BUCKET:-messenger-attachments} S3_STAGING_BUCKET: ${S3_STAGING_BUCKET:-messenger-staging} S3_ACCESS_KEY_ID_FILE: /run/secrets/s3_access_key_id S3_SECRET_ACCESS_KEY_FILE: /run/secrets/s3_secret_access_key S3_TIMEOUT_SECONDS: ${S3_TIMEOUT_SECONDS:-3} secrets: - database_url - source: s3_auditor_access_key_id target: s3_access_key_id - source: s3_auditor_secret_access_key target: s3_secret_access_key depends_on: postgres: condition: service_healthy s3: condition: service_healthy restart: "no" networks: [data, storage] deploy: resources: limits: {cpus: "1.0", memory: 256m} # Operator CLI (replay of failed jobs, reprocess with a newer pipeline, failed registry): # docker compose run --rm jobctl list-failed # docker compose run --rm jobctl replay --operator alice --reason "..." jobctl: profiles: ["tools"] image: ${API_IMAGE:-mtusi-messenger:lab5} entrypoint: ["python", "-m", "messenger.jobctl"] command: [] environment: DATABASE_URL_FILE: /run/secrets/database_url JOB_MAX_ATTEMPTS: ${JOB_MAX_ATTEMPTS:-5} secrets: [database_url] depends_on: postgres: condition: service_healthy restart: "no" networks: [data] deploy: resources: limits: {cpus: "0.5", memory: 128m} networks: edge: data: internal: true # no route outside: stores talk only to the services above storage: internal: true # S3 API reachable only by api, s3-init, worker, auditor queue: internal: true # broker reachable only by relay and worker volumes: pgdata: valkeydata: s3data: rabbitmqdata: secrets: postgres_password: file: ./secrets/postgres_password valkey_password: file: ./secrets/valkey_password database_url: file: ./secrets/database_url cache_url: file: ./secrets/cache_url s3_admin_access_key_id: file: ./secrets/s3_admin_access_key_id s3_admin_secret_access_key: file: ./secrets/s3_admin_secret_access_key s3_api_access_key_id: file: ./secrets/s3_api_access_key_id s3_api_secret_access_key: file: ./secrets/s3_api_secret_access_key s3_worker_access_key_id: file: ./secrets/s3_worker_access_key_id s3_worker_secret_access_key: file: ./secrets/s3_worker_secret_access_key s3_auditor_access_key_id: file: ./secrets/s3_auditor_access_key_id s3_auditor_secret_access_key: file: ./secrets/s3_auditor_secret_access_key rabbitmq_users: file: ./secrets/rabbitmq_users.json broker_url_relay: file: ./secrets/broker_url_relay broker_url_worker: file: ./secrets/broker_url_worker