WIP: Hermes three-lane accelerator placement #17

Draft
hermes-automation wants to merge 1 commits from feature/hermes-three-lane-placement into main

Runs three concurrent agent.hermes CLI lanes while keeping one authoritative stateful coordinator. The pod now prefers the larger ARM64 accelerator nodes titan-20/titan-21, retains healthy rpi5 fallback, and reserves 500m CPU/512Mi for the lane runner with a 3 CPU limit. This deliberately does not scale the RWO/SQLite coordinator to multiple replicas. Validation: 214 Hermes tests passed; focused lane/runtime suite 91 passed; Ruff and diff checks passed; Kustomize render, client dry-run, Flux-manager server dry-run, and admission dry-run passed.

Runs three concurrent agent.hermes CLI lanes while keeping one authoritative stateful coordinator. The pod now prefers the larger ARM64 accelerator nodes titan-20/titan-21, retains healthy rpi5 fallback, and reserves 500m CPU/512Mi for the lane runner with a 3 CPU limit. This deliberately does not scale the RWO/SQLite coordinator to multiple replicas. Validation: 214 Hermes tests passed; focused lane/runtime suite 91 passed; Ruff and diff checks passed; Kustomize render, client dry-run, Flux-manager server dry-run, and admission dry-run passed.
hermes-automation added 1 commit 2026-08-17 08:46:54 +00:00
This pull request has changes conflicting with the target branch.
  • services/hermes/agent-deployment.yaml
  • testing/tests/test_hermes_cli_lanes.py

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feature/hermes-three-lane-placement:feature/hermes-three-lane-placement
git checkout feature/hermes-three-lane-placement
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: titan/atlas-iac#17
No description provided.