Networklore is my home online, the main focus of the site is network automation.
Networklore started it's life as a blog. Most of the content here is in the form of blog articles.
Some of the content here is in a longer form than you would usually see in blog posts. One example is the Zero-touch provisioning tutorial.
I like sharing what I do and aim to continue releasing open source tools which can help other people in the networking industry. There's a small list below of example projects and a longer one on the contact page.
If you like Networklore make sure you subscribe and I'll let you know as soon as I publish anything new.
Each email you receive will have an unsubscribe link included, so as soon as you don't want any more mails you're just an easy click away.
Here you can find a few of the open source projects I have created.
A toolkit for aimed to help network engineers written with everyday tasks
A collection of network plugins for Nagios and compatible products.
Proof of concept for managing Cisco IOS devices with Ansible using SNMP.
Ansible modules to query network devices with SNMP from Ansible.
Here's the latest of my writings from the blog
Nornir is a new automation framework written in Python and intended to be consumed directly from Python. You could describe it as the automation framework for Pythonistas. This might strike you as something wonderful, or it could trigger your spider-sense. Writing code? Isn’t that just for programmers?
It started out as a question. If you are using several networking modules in a playbook, do you really have to repeat the same credentials on every task? Just like the last few articles about Ansible this one came to life after answering questions in a chat room. The short answer is; No you don’t have to include all of the required parameters for every task, you can use an action plugin to work around that. Great! So what’s an action plugin?
At the outset, a 1200 word article about saving configuration sounds strange. It would perhaps be perfectly normal if the topic was Vi and not Ansible, however there’s a reason for this and its simply speed and itempotency. Saving the configuration in the “wrong” way can take quite a lot of time and one reason for network automation is to accomplish tasks faster and constantly search for ways to improve your processes. This article assumes that you are running Ansible 2.4, but it should work in a similar way regardless.