test: wire cf-orch agent registration into compose stack #48

New issue

Open

opened 2026-03-31 19:06:14 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-03-31 19:06:14 -07:00

Owner

Goal

Verify that Peregrine registers as a node with the cf-orch coordinator so GPU activity appears on the dashboard at http://10.1.10.71:7700/.

What to do

Add a cf-orch agent service to compose.override.yml (alongside the existing ollama/vllm adoption pattern)
The agent should start after the GPU services are up and register with the coordinator at http://heimdall:7700 (or CF_ORCH_COORDINATOR_URL env var)
Confirm peregrine’s GPU card appears on the dashboard with live VRAM readings
Run a cover letter generation task and confirm VRAM usage reflects on the dashboard

Config

cf-orch agent \
  --coordinator http://10.1.10.71:7700 \
  --node-id peregrine \
  --host 0.0.0.0 \
  --port 7701

Acceptance criteria

peregrine GPU card visible on dashboard
VRAM bar updates when vLLM/ollama is active
Agent reconnects after coordinator restart
No impact on existing task scheduler behaviour

## Goal Verify that Peregrine registers as a node with the cf-orch coordinator so GPU activity appears on the dashboard at `http://10.1.10.71:7700/`. ## What to do 1. Add a `cf-orch agent` service to `compose.override.yml` (alongside the existing ollama/vllm adoption pattern) 2. The agent should start after the GPU services are up and register with the coordinator at `http://heimdall:7700` (or `CF_ORCH_COORDINATOR_URL` env var) 3. Confirm peregrine’s GPU card appears on the dashboard with live VRAM readings 4. Run a cover letter generation task and confirm VRAM usage reflects on the dashboard ## Config ```bash cf-orch agent \ --coordinator http://10.1.10.71:7700 \ --node-id peregrine \ --host 0.0.0.0 \ --port 7701 ``` ## Acceptance criteria - [ ] `peregrine` GPU card visible on dashboard - [ ] VRAM bar updates when vLLM/ollama is active - [ ] Agent reconnects after coordinator restart - [ ] No impact on existing task scheduler behaviour