Professional
Capstone
One cumulative system, not a new tool: an NTP server migration, from a NetBox-sourced fleet through detection, generated remediation, Git evidence, and a staged, gated rollout with rollback -- closing the original curriculum roadmap.
The Capstone isn't a new tool -- it's every mechanism from this curriculum connected into one real pipeline, run against one concrete problem: an NTP server migration. You'll start from a NetBox-sourced, multi-vendor Nornir inventory, use NAPALM to detect which devices are actually non-compliant, and generate remediation only for the devices that need it -- never hand-typed, never applied to a device that was already correct. That change is committed to Git as approved evidence, then rolled out through the same staged, gated canary process from Production Automation, with automatic rollback wired in.
Next up
From Source of Truth to an Actionable Problem
0 / 5 completeLessons
- 1
From Source of Truth to an Actionable Problem
The Capstone's first stage: a NetBox-shaped source of truth loads a dynamic, multi-vendor Nornir inventory, NAPALM collects each device's current NTP configuration, and the fleet is classified compliant vs. non-compliant against one real migration requirement -- three already-proven mechanisms, connected for the first time as one pipeline's opening stage.
Advanced14 min readNext up - 2
Generating Remediation from Detected State
The Capstone's second stage: turning Lesson 1's exact detection result into a remediation artifact -- one derived configuration line, generated only for the devices detect_noncompliance() actually flagged, never hand-typed and never applied to a device that was already compliant.
Advanced10 min read - 3
Recording the Approved Change
The Capstone's third stage: the generated remediation is written to a real local Git repository, committed as approved evidence, and read back directly from the commit object -- so the configuration the rollout applies is provably the same thing that was committed, not a retyped copy of it.
Advanced11 min read - 4
Canary Rollout and Validation Gates
The Capstone's fourth stage: the affected devices from Lessons 1-2 and the Git-evidenced configuration from Lesson 3 are staged through a canary, gate, expand-or-rollback sequence -- Production Automation's exact mechanics, wired for the first time to a dynamically-detected subset instead of a statically-tagged one, with both real outcomes genuinely executed.
Advanced16 min read - 5
Capstone: Source of Truth to Safe Network Change
Every piece of this module -- NetBox-sourced multi-vendor inventory, NAPALM state collection, detection, generated remediation, Git evidence, canary rollout, a validation gate, and rollback -- combined into one real, runnable pipeline, executed on BOTH outcomes: a canary that passes and expands, and one that fails and rolls back. The final lesson of the original 20-module curriculum.
Advanced20 min read