Professional
Real-world Projects
Three end-to-end projects combining previously-separate modules -- config backup with drift history, a multi-vendor compliance report sourced from NetBox, and a Git-reviewed change driving a staged, gated rollout -- plus guidance for scoping and presenting a project of your own.
This module is a change of pace: three end-to-end projects that each combine two or three earlier modules around one named problem, rather than teaching a new tool. You'll pull configuration with NAPALM and track drift over time with Git, build a multi-vendor compliance report sourced from a NetBox-shaped fleet, and connect a Git-reviewed, approved change directly into a staged, gated rollout -- closing a link Git/NetDevOps and Production Automation each deliberately left open. A closing, code-free lesson then walks through choosing a realistic problem and presenting the result as real portfolio evidence.
Next up
What Makes a Real-world Network Automation Project?
0 / 5 completeLessons
- 1
What Makes a Real-world Network Automation Project?
The difference between a guided exercise, a single-module capstone, and a real-world project -- and the eight-step frame (problem, requirements, inputs, workflow, validation, failure handling, report, portfolio) the next three projects each follow.
Advanced9 min readNext up - 2
Project 1: Configuration Backup & Drift History
Pull running configuration with NAPALM, commit each pull to a real local Git repository only when it actually changed, and generate a real diff-based drift report between the two most recent backups -- NAPALM's config retrieval and GitPython's commit/diff, connected for the first time in this curriculum.
Advanced14 min read - 3
Project 2: Multi-Vendor Configuration Compliance Report
A fleet spanning three vendors, sourced dynamically from a freshly-built NetBox-shaped mock, evaluated against one required baseline line through NAPALM's normalized get_config() -- NetBox as source of truth and multi-vendor NAPALM getters, combined into one compliance report, genuinely showing both a compliant and a non-compliant result.
Advanced15 min read - 4
Project 3: Reviewed Change to Staged Rollout
The one connection Git / NetDevOps and Production Automation each deliberately left for later: a real, committed, approved change read directly from a Git commit object, fed straight into a canary-staged rollout with a gate, and closed with one audit report combining the change's Git evidence and its rollout outcome -- both the pass-and-expand and fail-and-rollback paths genuinely executed.
Advanced17 min read - 5
Building Your Own Real-world Project
A closing, portfolio-focused lesson -- no new automation code. How to choose a realistic problem, define requirements and validation criteria, reuse tools from across this curriculum instead of reinventing them, handle failure honestly, and present the result as real portfolio evidence.
Advanced10 min read
Practice this module
Apply what you just covered -- hands-on practice and a knowledge check for this module.
Apply your skills
Network Configuration Backup Analyzer
Combine multi-device text-config validation, structured fact extraction, and line-by-line comparison into one backup analysis pipeline that safely handles a missing or corrupted backup instead of crashing on it.
Multi-Device Compliance Report
Build a data-driven compliance engine that evaluates every device in a fleet against a shared set of policy rules, safely isolating a rule failure caused by missing device data from a device record too malformed to evaluate at all.