Files
mtusi2026lab2/evidence/limits.txt
T
ArtyomandClaude Opus 5.5 573220e12a Record level 4 evidence and fill in the report
evidence/level4.json: all 17 scenarios of levels 3 and 4 and the eight
invariants pass on 0b85edf; evidence/operator.txt shows the failed
registry, a replay to ready, a noop replay, an expired replay and the
DLQ. Smoke, topology, level3, persistence, failover, lab 4 scenarios,
limits, student tests and contract checks are refreshed on the same
commit. REPORT.md describes the variants, worker limits, jitter, lease
renewal, crash points, replay and retention, adds rows 4.1-4.4, the
level 4 failure experiments and the updated limitations.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-29 03:39:20 +03:00

32 lines
3.8 KiB
Plaintext

date: 2026-10-29T00:34:02Z
$ docker compose --profile bench --profile tools config --format json (declared)
service cpus/mem ports secrets volumes networks ro
-------- ---------- ------------------------------- ----------------------------------------------------------------------------------------------------------------------- ----------- ---------------------- -----
api 1/512MiB - cache_url,cursor_secret,database_url,s3_access_key_id,s3_secret_access_key - backend(internal) true
broker 1/512MiB 127.0.0.1:25672 rabbitmq_ops_password,rabbitmq_users broker-data backend(internal),edge true
k6 2/512MiB - - - edge false
lb 1/128MiB 127.0.0.1:18085,127.0.0.1:25085 - - backend(internal),edge true
migrate 0.5/256MiB - database_url - backend(internal) false
postgres 2/1024MiB - postgres_password pgdata backend(internal) false
relay 0.5/192MiB - broker_url_api,database_url,s3_access_key_id,s3_secret_access_key - backend(internal) true
s3 1/512MiB - s3_root_password,s3_root_user s3data backend(internal) true
s3-cli 0.5/64MiB - s3_access_key_id,s3_root_password,s3_root_user,s3_secret_access_key,s3_worker_access_key_id,s3_worker_secret_access_key - backend(internal) true
s3-init 0.5/64MiB - s3_access_key_id,s3_root_password,s3_root_user,s3_secret_access_key,s3_worker_access_key_id,s3_worker_secret_access_key - backend(internal) true
valkey 0.5/128MiB - valkey.conf valkeydata backend(internal) false
worker 2/1024MiB - broker_url_worker,database_url,s3_worker_access_key_id,s3_worker_secret_access_key - backend(internal) true
$ docker inspect (running containers: hostname = X-Instance-Id, applied limits)
service hostname cpus memory published
-------- ------------ ---- ------- ---------------------------------------------------
api 095cb9cc85bd 1 512MiB
api 70cfba801128 1 512MiB
broker broker 1 512MiB 127.0.0.1:25672->15672/tcp
lb c0fb1baf1003 1 128MiB 127.0.0.1:18085->8080/tcp,127.0.0.1:25085->8404/tcp
postgres 0a58a30d4f0f 2 1024MiB
relay 36f8b7c0afb7 0.5 192MiB
s3 bed02ee8e4fc 1 512MiB
valkey 1d3e7af5a234 0.5 128MiB
worker 56c0ce59c97a 2 1024MiB
PASS: limits, ports, secrets, volumes and networks match the policy