The k6 profile from the prepared kit runs an open model against the balancer from the edge network: constant arrival rate, 80 % keyed message posts and 20 % history reads over 20 synthetic users and 10 chats, metrics only for the measure phase, and no setup data (tokens) in summary.json. scripts/k6.sh runs it with the host uid so the summary is writable on Linux too. scripts/probe.py gains three things. check --rounds repeats the same-key race with a new key per round and counts rounds with identical bodies, one stored copy and 409 on another body. load runs an action under k6 while a probe posts every 0.1 s and resends the same key after a failure and a poller reads the number of UP servers; it writes the action log, the probe and LB traces, the delta of the backend retry, redispatch and error counters, and a verdict: dip for a replica that leaves and returns, replace for a rolling update that must keep capacity and end on new replicas only. detect runs the action in the background and polls the balancer at the same time, so a drain that ends after the exclusion is visible, and checks the declared maximum, the LB answer after detection and the time to restore. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Инфраструктура студента
Здесь разместите конфигурации выбранных сервисов; основную топологию — в корневом compose.yaml/stack.yaml. compose.example.yaml — только worksheet ролей и намеренно не запускается. contracts/infrastructure.json задаёт минимальные роли, не готовые образы/пароли.
В REPORT.md сопоставьте роль → service name → версия/digest → health/readiness → volume → сеть/порт → способ передачи credentials. Приведите bootstrap (schema, bucket, broker topology, а с lab6 provisioning) и безопасное повторение этих команд.
Приложение строится из исходников. Не используйте заранее существующий образ преподавательского сервера вместо своей реализации. Restart hook перезапускает все соответствующие stores с volumes; failover hook останавливает только заданную API-реплику.