bmo
- GET /bmo/provision/node-status
Get provisioning status by node
Resolves a node’s provisioning status row from bmc_ip and batch_id, computing the job id server-side, and returns it sanitized for the client.
- Query Parameters:
bmc_ip (string) – BMC IP address
batch_id (string) – Provision batch ID
- Status Codes:
200 OK – OK
400 Bad Request – bmc_ip and batch_id are required
404 Not Found – Not found
- Response JSON Object:
bmc_ip (string)
code (string)
duration_ms (integer)
error (string)
failure_class (string)
hostname (string)
identity_verified (string) – IdentityVerified is stamped (first-write-wins) when a valid, unexpired firstboot token POSTs a source=”firstboot” report. It proves ONLY that something holding this node’s per-node 0600 firstboot token reached the report endpoint - i.e. the node’s own golden firstboot ran far enough to POST. It does NOT prove the golden booted correctly or converged; it is the c2 identity signal, nothing more.
job_id (string)
message (string)
next_steps (string)
phase (string)
possible_causes[] (string)
progress (integer)
source (string)
stage_id (string) – Structured, human-safe fields carried from the node’s kfblog record over Path B, so the dashboard renders a classified cause instead of the raw Error. StageID is the machine-stable stage/phase id (== kfblog phase) used for the phase->percent map.
state (string)
updated_at (string)
- POST /bmo/provision/report
Report node provisioning progress
Called by a provisioning node without a JWT: records a phase, state and progress report for a job authorized by the per-job token, or by the firstboot token when source is firstboot, and broadcasts it to SSE clients.
- Status Codes:
200 OK – ok, plus identity_verified for a firstboot report
400 Bad Request – Validation failed
401 Unauthorized – Unknown job or invalid token
403 Forbidden – bmc_ip does not match the job
500 Internal Server Error – Internal error
503 Service Unavailable – Provision status store unavailable
- Request Headers:
Authorization – Bearer per-job token (or firstboot token for source=firstboot)
X-Job-Token – Per-job token when no Authorization header is sent
- GET /bmo/provision/status
List provisioning status rows
Returns every provisioning status row, newest first, sanitized for the client.
- Status Codes:
200 OK – items: list of provisioning status rows
- GET /bmo/provision/status/{job_id}
Get provisioning status by job
Returns the provisioning status row for a job, sanitized for the client.
- Parameters:
job_id (string) – Provision job ID
- Status Codes:
200 OK – OK
404 Not Found – Not found
- Response JSON Object:
bmc_ip (string)
code (string)
duration_ms (integer)
error (string)
failure_class (string)
hostname (string)
identity_verified (string) – IdentityVerified is stamped (first-write-wins) when a valid, unexpired firstboot token POSTs a source=”firstboot” report. It proves ONLY that something holding this node’s per-node 0600 firstboot token reached the report endpoint - i.e. the node’s own golden firstboot ran far enough to POST. It does NOT prove the golden booted correctly or converged; it is the c2 identity signal, nothing more.
job_id (string)
message (string)
next_steps (string)
phase (string)
possible_causes[] (string)
progress (integer)
source (string)
stage_id (string) – Structured, human-safe fields carried from the node’s kfblog record over Path B, so the dashboard renders a classified cause instead of the raw Error. StageID is the machine-stable stage/phase id (== kfblog phase) used for the phase->percent map.
state (string)
updated_at (string)
- GET /bmo/view/sse
Stream all BMO events
Server-sent event stream on the bmo_unified channel carrying power_state, task_progress and capture_progress events for every BMC; clients filter by event type and bmc_ip.
- Status Codes:
200 OK – SSE stream of BMO events
500 Internal Server Error – SSE client could not be registered