In development · For working network engineers
Network DevOps: Git, Review, and Pipelines
Git taught as the change process you already run.
- 7
- lessons
- 3
- modules
- Alpha
- in development
This course is still being written. 7 lessons are drafted so far. The outline below is what it covers. You cannot buy it yet, and nothing on this page opens it.
Learning objectives
What you will be able to do
- Put a running config under version control and read its history back.
- Work a change on a branch, open it for review, and merge it once the checks pass.
- Roll a change back as a commit, so the recovery is in the history too.
What you leave with
Why choose this course?
Real git, not a simulator
Real git runs in the browser. The commands you type and the output you read match your workstation.
A review process you have run
A pull request is your change advisory board. You work both sides of it, as the author and as the reviewer.
One change across forty sites
The last module goes from one device to a whole estate. It also says where AI belongs in that.
Course content
Learning roadmap
7 lessons · 3 modules
This is the outline as it stands today. Lessons get added and moved while a course is being written, so it will change.
1. The Change Process, Written Down2 lessons
The archive says what a box looks like. It cannot say why, or what the other choice would have been. These two lessons put the change process you already run into git. A commit carries the reason, and a branch holds the change window.
- Your Config Archive Is Not Version Control
- A Branch Is a Change Window
2. Review and Validation2 lessons
The second set of eyes and the pre-change test, built as machinery rather than run as a meeting. A pull request is the CAB with an audit trail. CI is the check nobody skips because they were in a hurry.
- The Pull Request Is the CAB
- CI Is Pre-Change Validation
3. Recovery, Scale, and the AI3 lessons
This module covers what you do after a bad change deploys. It covers how one change reaches forty sites without forty chances to fat-finger it. It also defines what a model is allowed to decide.
- Rollback Is a Commit, Not a Restore
- One Change, Forty Sites
- Where the AI Goes, and Where It Does Not
From inside the course
Coming Soon
This course is not available yet. Browse the catalog for courses you can start today, including the free courses available with an account.