Plan, execute and document a complete migration

capstone · 150 min · Objective 2.3

Task

Pull the whole Deployment domain together: assess a workload, define its target in code, migrate it, validate it, and produce the documentation a colleague could follow to repeat or reverse it.

Steps

  1. Choose a small multi-component application -- a web service, a database and a file store will do -- and run it by hand as the 'existing' estate. Produce lab/cap2/assessment.md covering sizing from measurement, observed dependencies, compatibility and licence position, and the disposition with its reason.
  2. Define the target environment entirely in code: network, identity, compute, data and traffic, built in that dependency order. Save the plan output to lab/cap2/plan.txt and confirm nothing is marked REPLACE that you did not intend.
  3. Migrate the data with a seed-and-replicate approach, recording lag until it is stable, then execute the cutover against the go/no-go criteria you wrote in advance.
  4. Validate function, performance and data integrity in order, comparing performance against the baseline you measured in step 1. Record all three in lab/cap2/validation.md.
  5. Produce lab/cap2/runbook.md: the cutover timeline, the point of no return, the rollback procedure with its MEASURED duration, and the verification that the environment can be destroyed and rebuilt from code alone. Then destroy it, rebuild it, and confirm the validation still passes.

Verify

for f in assessment plan validation runbook; do test -s lab/cap2/$f.* && echo "$f ok"; done
grep -Eci 'baseline' lab/cap2/assessment.md lab/cap2/validation.md
grep -Eci 'point of no return' lab/cap2/runbook.md
grep -Ec '[0-9]+ ?(s|sec|second|min)' lab/cap2/runbook.md
grep -Eci 'rebuilt|rebuild' lab/cap2/runbook.md

Every file present, a measured rollback duration, and evidence of the destroy-and-rebuild. That last step is what turns "it is in code" from a claim into a demonstrated property.

Notes

The rebuild in step 5 is the capstone's real assertion. An environment that cannot be destroyed and recreated from its own code is not actually described by that code, however clean the plan output looks.

This is an independent study companion for CompTIA Cloud+ CV0-004 and is not produced by or endorsed by CompTIA.