Skip to content

Controlling the fleet

The fleet control service runs operator test actions against a running Narwhal fleet:

  • engine pause, resume, stop, start, drain and readmit
  • configuration overlays
  • cold restarts and baseline restores
  • AIPerf load jobs

The service records each action, with its time and effect, in a private run record. The console runs on its own page. The Narwhal Orchestrator dashboard links to it and marks each action on its charts.

The service runs on the router host, listens on loopback, and authenticates API requests with a bearer token. Operators reach the console and Grafana from a workstation through the operator tunnel.

Hooks are the commands, defined in the private configuration, that perform each change, such as stopping an engine or restarting the router. Drains and readmits use the router's lifecycle API instead.

Work happens in sessions. Starting a session copies the baseline fleet configuration. Ending it closes the session's record and leaves the fleet as it is. Restore baseline undoes the session's changes.

Walkthrough

Fleet control walkthrough title frame.

Pages