Ansible for Networking - Part 2: The Lab environment

This is the second part in my ongoing series on using Ansible for Networking, showing how to use Ansible to configure and manage equipment from multiple networking vendors. In the “Start of the series” post, I mentioned that the lab would consist of: - The KVM hypervisor running on Linux A virtual machine, running CentOS 8, that will run: - FRR - Acting as a route server Syslog Tacplus (for TACACS+ integration) Two routers/virtual machines of each vendor, one running as an “edge” router, one running as an “internal” router A control machine that Ansible will run from, over a management network to all machines This post goes through the Hypervisor, setting up the CentOS 8 virtual machine, and the control machine. [Read More]

Ansible for Networking - Part 1: The start of the series

For those who have been reading my posts for a while, they’ll know that while currently I’m a DevOps Engineer, I spent the previous decade managing and configuring service provider networks. For the majority of that time, the network was configured by hand. The closest most people in the industry had to an automation toolset was either using a spreadsheet with variables, their own scripts they had created, or delegating the task to multiple junior engineers. [Read More]

Configuration Seasoning: Getting started with Saltstack

Configuration management is the practice of deploying and managing your application and infrastructure configuration through automated tooling, rather than managing all of your infrastructure manually. This can cover everything from Linux servers, to network equipment, installing packages to updating existing services. The primary benefits are that you can manage more infrastructure without the operational burden increasing significantly, and that your configuration is consistent across your estate. There are already a number of tools which achieve this: - [Read More]