So far this little InfraAsCode series was all about declarative Ansible playbooks and Git version control. In this last post we go full circle and discover how CI/CD pipelines helps with automation workflows, taking full advantage of good software development practices.Continue reading “Network InfrastructureAsCode with Ansible & Git – Part 3”
In part one we learned how to use Ansible and a data model to represent infrastructure as code. Now it’s time to introduce Git as the central network automation tool to use the advantages that result from working with text files.
I cannot emphasize enough how important this step is to long-term success with an automation initiative. Unversioned files with funny names in a random directory are not the solution.Continue reading “Network Infrastructure As Code With Ansible & Git – Part 2”
Infrastructure as code is all the rage, but sounds hypercomplex. How should it be possible to represent a router or even a whole network as code? We definitely need deep software development skills and an extensive version control plus CI/CD pipeline, right? Well, no! Actually, it’s pretty darn simple and by the end of this blog post you might wonder what took you so long to get started.Continue reading “Network Infrastructure As Code With Ansible – Part 1”
It seems that the TIG-Stack not only excels in the data center, but as a home automation UI as well – thanks to the versatile Telegraf input agent. Stock OEM display solutions often cost an arm and a leg, so I decided to build my own over a year ago. This post is about the hard- and software in use, as well as the necessary configuration to realize a useful dashboard system for your precious home.Continue reading “Telegraf/InfluxDB/Grafana Dashboard @home”
Whether you are looking for a little test bed or an always-on home dashbording system, the RaspberryPi is a great, affordable platform for the TIG-Stack. So let’s ride through all the necessary steps ‘From Zero to Awesome’ in less than one hour.Continue reading “Telegraf / InfluxDB / Grafana on RaspberryPi – From Scratch”
This topic came up via Twitter recently and I heard this use case before but wasn’t aware how easy it could be solved with Ansible, until I started thinking about it. The little playbook in this blogpost fetches all discovered neighbors per device and sets the interface description according to the remote host and port. It supports the two platforms Cisco IOS XE and NX-OS to demonstrate the path to a multivendor solution for the common brownfield networks out there.Continue reading “Fix Your Interface Description with Ansible and CDP/LLDP”
Most Network Automation publications tend to focus on the technology, how to code, build useful pipelines, and this week’s tool of fashion. But isn’t that a very one-sided view of the topic? I mean after all, people are what make automation happen and drive those projects forward. Thankfully Skynet is too far away to autonomously build automation frameworks and the ‘Self-driving Network’ never made it from marketing to the real world.Continue reading “The Human Factor in Network Automation”
I know, even Cisco NX-OS has a REST-API and Streaming Telemetry these days.
But you, or established processes in your organisation, might find it helpful to handle all switch ‘Telemetry’ in the same way using good old per device SNMP polling. A quick poll* on the Twitters seems to validate that ~80% of production network metrics are still SNMP anyway.
*See what I did there?Continue reading “Monitor Cisco NX-OS/ACI via SNMP and the TIG-Stack”
This blog post from the folks at NetworkToCode about the DRY principle (Don’t Repeat Yourself) reminded me of our early network automation days. There were playbooks involved, external variable definition files as a first step to source of truth and, well, lot’s of redundant data …Continue reading “Working with ipaddr in Ansible”