Responding to my Infrastructure as Code Sounds Scary blog post, Deepak Arora posted an interesting (and unfortunately way too accurate) list of challenges you might encounter when trying to introduce network automation in an enterprise environment.
He graciously allowed me to repost his thoughts on my blog.
Why don’t we agree on that :
Automation never really took off well despite all efforts from vendors and communities side. My best guess is even today close to 80% of network infrastructure is deployed and managed in a manual fashion. The ratios might be bit here and there and I can imagine North America as region would be ahead of everyone else.
Most automation engineers I have interviewed in the past couple of years had absolutely no idea about how to sell it to management for seeking investment. At best they will often be found throwing another set of marketing slides at them.
Let’s admit that when we ask people what network automation really means and can do, 90% of people will just spell out “Python, DevOps, Ansible and Terraform”.
How many engineers in the network automation community treat is as an architecture in itself rather than as a very tactical thingy?
Automation is a great tool like many others available to the network engineering community, but most of them are still looking at it as if it is a silver bullet, and being very tactical in their approach.