How-to – Simple network automation with Ansible – Part 1

Worth the effort?

Every now and then you may run into networks that run different brands of devices or same brands but with huge OS version discrepancies. That’s were implementation in any form of network automation becomes complicated. So while you think about using a tool like Ansible you also know you may be limited by time or by complication to get the job done: KISS beeing a reasonable thought in every aspect of IT nobody will blame you for going the custom script way. After all, why build a full automation setup to execute a single task, if there are no other planned configs to deploy in any other use case? Well, let me explain why it might be worth it after all.

It’s here

If you are running a network of a certain size, there is a big chance that you have a certain need for automation. There might be just a single use case for now or even none at all (or so you might think) but chances are high you will need it to keep up with all the automation going on all the services running on top of it, if it’s not already the case.