Skip to content

Resolve Containerlab Recovery Authority

  • Purpose: Resolve competing topology authorities before execution begins.
  • Owner: Network operations
  • Impact: Selects which topology definition governs the next deployment.
  • Rollback strategy: Stop before deployment and inspect both definitions. Neither source is changed by the comparison.

Pre-checks

Validate the environment blueprint and retain both topology sources:

ENV=<environment>
REF=<containerlab-blueprint>
hyops blueprint validate --env "$ENV" --ref "$REF"

Execute

For an interactive deployment, run the normal command and select the source when prompted:

hyops blueprint deploy --env "$ENV" --ref "$REF" --execute

For unattended recovery, select the archive explicitly:

hyops blueprint deploy \
  --env "$ENV" \
  --ref "$REF" \
  --execute \
  --restore-labs

To deploy the current controller topology without replaying retained recovery state:

hyops blueprint deploy \
  --env "$ENV" \
  --ref "$REF" \
  --execute \
  --skip-lab-restore

Use --overwrite-labs with --restore-labs only when replacing an active lab is intended.

Verify

Confirm the deployed topology identity and device set match the selected source. Verify saved device state separately; topology equality alone is not a continuity test.

Records

The deploy record retains the selected recovery authority through final dispatch. The archive and controller source remain separately identifiable inputs.

Rollback

Destroy the newly deployed lab while retaining recovery data, then redeploy with the other explicit authority.

References