Case study · CI/CD · Network automation
Network Change & Configuration Pipeline
Pipeline-driven configuration generation, validation and deployment for data-centre and enterprise networks.
discovery · snmp + ssh + api · 214 devices
Context
Enterprise and data-centre teams making frequent network changes by hand: copy-pasted CLI, inconsistent peer review and no reliable way to prove a change did what it was supposed to.
01
The challenge
- Manual configuration changes with human error as the leading cause of incidents.
- No consistent pre- and post-change verification; rollbacks improvised under pressure.
- Change records, configuration and design intent lived in different places and drifted apart.
02
Our approach
- Source of truth (IPAM / inventory) drives Jinja-templated configuration for ACI, NX-OS and IOS-XE platforms.
- Git-based workflow: every change is a pull request; the pipeline lints, renders and validates the configuration before a human approves.
- Deployment via Ansible and vendor APIs with a snapshot of pre-change state; post-change checks compare reachability, routing and fabric health, rolling back automatically on failure.
03
The outcome
- Every network change reviewed, tested and auditable in version control.
- Change windows shortened and incident rate from configuration error sharply reduced.
- Same pipeline pattern reused for on-demand bulk changes and migrations.
More case studies