python-networking.com

Why I started this blog

I have noticed the steady use of programming and scripting languages in the network engineering realm for around 10 years now. I have also (sometimes heavily) used various self-built tools to make my job easier, and knew that someday would come, when the industry started to embrace not only the technology, but the concepts of having engineers perform regular operations through automation. It just makes sense after all, why would you keep wanting to have one person go out and individually touch 700 routers / switches, when they could write a script that could do it for them, and then re-use that the next time a mass push came up? But it goes a bit deeper than that too. The start was just writing code that physically ssh's into the cli of switches and makes changes or reports back show items... but the vendors started to realize that approach is very cumbersome and time consuming, so they started to develop API's that would allow a much more elegant and scalable approach to automation factors. So in all of this movement, I have found some resources online that show some of the tips and tricks, but not a good place that is dedicated to specifically coding for networking. Most trainers do some of this, and some of that. And don't get me wrong, there are tons of great resources from some of these trainers. But my site is not to try and boost my selling of my own training or something like that, it is more to share the techniques and experiences in my journey to becoming a good devops engineer. Some call them SRE or Site Reliability Engineer, but most of the engineers are doing the same things, trying to lay the framework for a continous tool / tools that can rapidly deploy changes, and scale to millions of nodes eventually making the entire business more agile.

Some of my top resources

Kirk Byers

David Bombal

Kevin Wallace

Page 1 / 1

blogroll

social