Skip to content

Run a Time-Bounded Cloud Lab Access Session

  • Purpose: Make session expiry an explicit lifecycle decision rather than an unobserved timeout.
  • Owner: Platform operations
  • Impact: Keeps access in the foreground and may preserve and release the environment at expiry.
  • Rollback strategy: Extend or cancel the session before expiry. Cancellation removes the scheduled action but does not close access or destroy resources.

Pre-checks

Confirm that the lab is healthy and that its recovery path is configured:

ENV=<environment>
REF=<gcp-lab-blueprint>
hyops blueprint preflight --env "$ENV" --ref "$REF"

Execute

Start a supervised session:

hyops blueprint access \
  --env "$ENV" \
  --ref "$REF" \
  --session-minutes 90 \
  --on-expiry protected-release

Inspect it from another terminal:

hyops blueprint session status --env "$ENV" --ref "$REF"

Extend the current deadline:

hyops blueprint session extend \
  --env "$ENV" \
  --ref "$REF" \
  --minutes 30

Cancel only the expiry action:

hyops blueprint session cancel --env "$ENV" --ref "$REF"

Verify

Status output must show the environment, session identifier, deadline, expiry action, and current outcome. At expiry, protected release must verify recovery state before resources are removed. A failed preservation gate retains the environment.

Records

Session state is scoped by environment and blueprint. Its final record includes the deadline, extension or cancellation history, release result, and cost estimate when available.

Rollback

Run session cancel before expiry if automatic release is no longer intended. Use the normal protected-release runbook for a later manual teardown.

References