Skip to content

Air-gapped build (manual Zuul trigger)

Status: draft — content will evolve as procedures are finalized.

Runbook for triggering and monitoring an offline Kolla build through Zuul.

Pre-flight

  • Confirm mirror freshness and registry availability inside the disconnected site.
  • Ensure Nodepool labels for builders are ready and have sufficient disk.
  • Validate secrets (registry credentials, CA bundles) are current in Zuul.

Trigger build

Sequence overview for a manual enqueue:

sequenceDiagram
    autonumber
    actor Operator
    participant ZuulWeb as Zuul Web/API
    participant Scheduler
    participant Nodepool
    participant Executor
    participant Registry

    Operator->>ZuulWeb: Enqueue build pipeline (change/ref)
    ZuulWeb->>Scheduler: Submit build item
    Scheduler->>Nodepool: Request builder node
    Nodepool-->>Scheduler: Node allocated
    Scheduler->>Executor: Dispatch job playbooks
    Executor->>Registry: Push images to air-gapped registry
    Registry-->>Executor: Ack and mirror status
    Executor-->>Scheduler: Job result (logs and artifacts)
    Scheduler-->>Operator: Pipeline status updates
  1. Enqueue the build pipeline manually via Zuul web/API for the desired change or reference.
  2. Watch executor and Nodepool logs for node assignment and capacity.
  3. Monitor job output for registry authentication and mirror reachability checks.

Post-flight

  • Collect BOM artifacts, layer digests, and job logs into the results store.
  • Update release notes or promotion candidates based on job outcome.
  • File issues in troubleshooting if unexpected errors occurred.