Skip to content

Inspect and Import a Network-Lab Migration Bundle

  • Purpose: Prevent an unverified or substituted migration artifact from becoming reconstruction authority.
  • Owner: Platform operations
  • Impact: Copies verified artifacts into environment-managed migration state. It does not deploy infrastructure.
  • Rollback strategy: Remove or replace the staged record before deployment. Keep the source bundle unchanged.

Pre-checks

Initialise the target environment blueprint and identify all companion files:

ENV=<environment>
REF=<same-platform-blueprint>
hyops blueprint init --env "$ENV" --ref "$REF"

Execute

Inspect the primary archive:

hyops lab migrate inspect \
  --platform <eve-ng|gns3|containerlab> \
  --archive <lab-archive.tar.gz>

Include companion files when present:

hyops lab migrate inspect \
  --platform eve-ng \
  --archive <lab-archive.tar.gz> \
  --node-state <lab-archive.node-state.tar.gz> \
  --images <lab-archive.images.tar.gz>

Add the recorded --expected-sha256, --node-state-expected-sha256, and --images-expected-sha256 values when independent transport verification is required.

Stage the verified set:

hyops lab migrate import \
  --env "$ENV" \
  --ref "$REF" \
  --platform <eve-ng|gns3|containerlab> \
  --archive <lab-archive.tar.gz> \
  --node-state <optional-node-state.tar.gz> \
  --images <optional-images.tar.gz>

Omit companion arguments that do not apply. Use --force only to replace a different active migration record for the same blueprint.

Verify

Import must report status=ready, the selected blueprint, checksum, and definition count. Then run the restore command printed by the CLI.

Records

The environment stores a migration record bound to its platform, blueprint, artifact identity, and companion-state checksums. Those values remain the inputs to reconstruction.

Rollback

Do not deploy if inspection reports an incompatibility, unsafe member path, or checksum mismatch. Correct the source bundle and capture it again.

References