Network Automation Forum · Change desk
- Intent
- Execute
- Collect
- Interpret
Define the acceptance checks
Rehearse the proposed change
Orchestration schedules the change and its checks. The executor applies the proposed configuration to the simulated network when you spin.
Collect branch evidence
Interpret the observations
Compare each observed result with its accepted requirement. Does this configuration meet the ticket’s intent at every branch?
Observability · Change and rollback
Rollback restores the pre-change snapshot. Both runs use the ticket’s original access requirements.
| Branch | Intent | Observed | Check |
|---|
Choose your next ticket
Answer explanation
Change & rollout evidence
Change ticket
| Source allowlist | Subnet (CIDR) | Action |
|---|
Rollout evidence
How to rate this risk
Compare the recovery estimate with the service tolerance. Use the rehearsal row to read the risk of this rollout.
| Rehearsal | Within tolerance | Over, up to 2× | Over 2× |
|---|
Terraform Current vs. proposed
Current configuration
Proposed configuration
Network atlas
Drag or use arrow keys to rotate. Select a gold site to explore another ticket. Teal paths lead to the simulated service region.
Ride the packet
Inspect traffic pathBefore change
Hints & worked solution
Review these five answers
Assessment scorecard
Risk ratings by actual band
| Actual risk | Rated low | Rated moderate | Rated high |
|---|
Skills
Each drill has five tickets, including related changes for smaller topics. Seeing a solution marks that ticket as assisted for a future campaign forecast.
Network oddities
First forecasts
Each ticket keeps its first forecast. Assisted tickets appear as practice. Accuracy uses independent first forecasts.