docs: add node1 runbooks, consolidation artifacts, and maintenance scripts
This commit is contained in:
@@ -0,0 +1,28 @@
|
||||
# Open Questions and Assumptions
|
||||
|
||||
## Decisions Confirmed in This Session
|
||||
1. Production authority is per-node compose manifests (NODE1/NODE3/Staging), not merged universal compose.
|
||||
2. `ingest-service`, `parser-pipeline`, `control-plane` are currently not active on NODE1 runtime.
|
||||
3. Canonical run subject policy is namespaced: `agent.run.requested.{agent_id}` with wildcard subscriber strategy.
|
||||
4. Production must have single edge proxy owner for 80/443.
|
||||
|
||||
## Remaining Open Items
|
||||
1. Exact deployment location (host/node/manifest) for `ingest-service`, `parser-pipeline`, `control-plane` when they become DEPLOYED.
|
||||
2. Final production proxy owner choice (nginx or Caddy) for canonical runtime profile.
|
||||
3. Timeline/PR sequence for NATS subject migration completion and legacy deprecation cutoff.
|
||||
4. Missing referenced services in default compose (`node-registry`, `city-service`, `agent-cabinet-service`, `devtools-backend`, `orchestrator`, `microdao`): same repo future work vs external repo ownership.
|
||||
|
||||
## Verification Artifacts Required to Close Items
|
||||
- Node-specific compose/service unit link proving deployment location.
|
||||
- Runtime `docker ps` + health snapshot for each node.
|
||||
- NATS stream/consumer metrics showing legacy subject traffic = 0 before deprecation.
|
||||
- Proxy port ownership verification (`80/443`) on runtime host.
|
||||
|
||||
## Source pointers
|
||||
- `docs/SESSION_STARTER.md`
|
||||
- `docker-compose.node1.yml`
|
||||
- `docker-compose.node3.yml`
|
||||
- `docker-compose.staging.yml`
|
||||
- `services/crewai-worker/main.py`
|
||||
- `ops/nginx/node1-api.conf`
|
||||
- `infra/compose/Caddyfile`
|
||||
Reference in New Issue
Block a user