history buffer
Run a command to capture the last five entries here. Each row stays compact until you expand it.
Watch a real LAB failover drill: warm a tagged EC2 target, drain the VCF web deployment, verify the app from AWS, restore VCF, and clean the cloud lane back to zero.
This rehearsal uses the real LAB lanes. We read the live VCF modern workload, launch a tagged EC2 host, stage a lightweight failover page on that host, intentionally drain the VCF web deployment, prove the health endpoint is now answering from AWS, restore the VCF service, and then tear the cloud host back down. It is a compact failover drill, not a staged animation.
current raw commands
Step 1/10Read the VCF baseline
Confirm the VCF workload first
Confirm the app is live on VCF
Confirm the VCF workload first
Launch the EC2 failover host
Stand up the AWS failover lane
Verify the host is healthy
Stand up the AWS failover lane
Install the app on EC2
Stand up the AWS failover lane
Turn off the VCF app
Flip the service and clean up
Prove the app on EC2
Flip the service and clean up
Restore the VCF app
Flip the service and clean up
Verify VCF is healthy again
Flip the service and clean up
Tear the EC2 host back down
Flip the service and clean up
Guided demo workflow
Expand to see the phase-by-phase operator sequence for this tab.
Start from the real VCF workload so the audience sees the healthy lane before any AWS resources are touched.
Build the short-lived AWS landing zone, verify the host, and warm the failover page there before the VCF side is drained.
Drain the VCF service, prove the app from AWS, restore the VCF deployment, and return the cloud lane to zero.
Guided failover playback. Raw commands and response blocks advance automatically.
history buffer
Run a command to capture the last five entries here. Each row stays compact until you expand it.