Step 12: Execution Plan
Version 11537 — Generate a sequenced execution plan across all regions
How This Step Works
- Complete Step 8 (MOP Analysis) and Step 10 (Playbook Mapping) first so the system knows which MOPs exist and which playbooks to run.
- Click Generate Plan to build a sequenced execution plan. The system reads the Overview MOP to determine ordering, groups MOPs into phases, assigns time estimates, and sequences them across regions.
- Review the generated plan below — check phase ordering, playbook assignments, and time estimates.
- Continue to Step 13 (MOP Ordering) to fine-tune dependencies, then Step 14 (Approval & Scheduling) to add approval gates and validations before execution.
Legend
All Regions Phase runs on every region before continuing
Per Region Phase runs independently on each region
Approval gate — manual approval required between regions
Phase must complete on all regions before next phase
Deployment region runs first in this phase
Automated validation | Manual validation
Execution Plan
8
Total MOPs2
Type(s)1448
Est. MinutesDRAFT
Status62
Total Validations50
Automated12
Manual448
Validation Minutesmarkdown_lea LEA 3 MOPs across 2 regions
Phase 1 (2.1) — Upgrade resources on all regions in the deployment
All Regions
| # | MOP | Category | Playbooks | Play Min | Val Min | Total | Vals | Source |
|---|---|---|---|---|---|---|---|---|
| 1 | r1153leauploadartifacts |
infrastructure | edit_yaml.yml commit_to_git.yml run_manual_pipeline.yml | 60 | +35 | 95 | 4 | auto |
|
Validations:
Wait for deployment to propagate
(5m)
after run_manual_pipeline.yml
Verify services healthy after deployment
(10m)
after run_manual_pipeline.yml
Validate Azure resources in expected state
(5m)
after run_manual_pipeline.yml
Operator verifies infrastructure change
(15m)
|
||||||||
Phase 2 (2.3) — Upgrade the region specific resources
Per Region
Approval Gate
| # | MOP | Category | Playbooks | Play Min | Val Min | Total | Vals | Source |
|---|---|---|---|---|---|---|---|---|
| 1 | r1153leaupgradeconfiguration |
git-ops | edit_yaml.yml commit_to_git.yml | 20 | +2 | 22 | 1 | auto |
|
Validations:
Verify git commit pushed successfully
(2m)
after commit_to_git.yml
|
||||||||
| 2 | r1153leaupgradeclitools |
infrastructure | edit_yaml.yml commit_to_git.yml run_manual_pipeline.yml | 60 | +35 | 95 | 4 | auto |
|
Validations:
Wait for deployment to propagate
(5m)
after run_manual_pipeline.yml
Verify services healthy after deployment
(10m)
after run_manual_pipeline.yml
Validate Azure resources in expected state
(5m)
after run_manual_pipeline.yml
Operator verifies infrastructure change
(15m)
|
||||||||
markdown_main MAIN 5 MOPs across 4 regions
Phase 1 (2.1) — Upgrade resources on all regions in the deployment
All Regions
| # | MOP | Category | Playbooks | Play Min | Val Min | Total | Vals | Source |
|---|---|---|---|---|---|---|---|---|
| 1 | r1153uploadartifacts |
infrastructure | edit_yaml.yml commit_to_git.yml run_manual_pipeline.yml | 60 | +35 | 95 | 4 | auto |
|
Validations:
Wait for deployment to propagate
(5m)
after run_manual_pipeline.yml
Verify services healthy after deployment
(10m)
after run_manual_pipeline.yml
Validate Azure resources in expected state
(5m)
after run_manual_pipeline.yml
Operator verifies infrastructure change
(15m)
|
||||||||
Phase 2 (2.3) — Upgrade the region specific resources
Per Region
Approval Gate
| # | MOP | Category | Playbooks | Play Min | Val Min | Total | Vals | Source |
|---|---|---|---|---|---|---|---|---|
| 1 | r1153upgradeconfiguration |
git-ops | edit_yaml.yml commit_to_git.yml | 20 | +2 | 22 | 1 | auto |
|
Validations:
Verify git commit pushed successfully
(2m)
after commit_to_git.yml
|
||||||||
| 2 | r1153upgradeccm |
git-ops | edit_yaml.yml commit_to_git.yml | 20 | +2 | 22 | 1 | auto |
|
Validations:
Verify git commit pushed successfully
(2m)
after commit_to_git.yml
|
||||||||
| 3 | r1153upgradecmm |
git-ops | edit_yaml.yml commit_to_git.yml | 20 | +2 | 22 | 1 | auto |
|
Validations:
Verify git commit pushed successfully
(2m)
after commit_to_git.yml
|
||||||||
| 4 | r1153upgradeclitools |
infrastructure | edit_yaml.yml commit_to_git.yml run_manual_pipeline.yml | 60 | +35 | 95 | 4 | auto |
|
Validations:
Wait for deployment to propagate
(5m)
after run_manual_pipeline.yml
Verify services healthy after deployment
(10m)
after run_manual_pipeline.yml
Validate Azure resources in expected state
(5m)
after run_manual_pipeline.yml
Operator verifies infrastructure change
(15m)
|
||||||||