In this article, I will discuss 5 steps that you can take today to start working your way to a Full Stack Networker or NetDevOps or a Network Automation Engineer.
In this article, I will describe the process of continuous integration (CI) and how you can commit your first NetDevOps config-as-code build using Gitea. It is also my hope that this inspires readers to really commit to transforming their career to network automation engineer or NetDevOps given the enormous potential.
As we know, CLI was created for humans and is optimized for manual interaction where you configure one device at a time. Given the nature of manual modification, it is obviously prone to error and tasks are NOT easily repeatable. Future network operations with NetDevOps toolchain would allow us to apply version controls to all configuration changes and where it is the single source of truth.
Building upon our DevOps knowledge base, in this article, I will go over a practical version of a complete NetDevOps delivery pipeline.
In this post, I will discuss good old DevOps and how it compares with NetDevOps along with my take on why network programmability is NOT NetDevOps.
Before we go into what, where and how to get started, let me address one crucial topic which is the proverbial elephant in the room, i.e. job security. I can’t tell you how many times have I heard that network automation will take my network admin or network engineering job away?