Now that we have our 3-node OpenStack lab up and running we can start exploring how virtual networks are implemented under the hood.

In the previous post I’ve demonstrated how to get a working instance of a single-node OpenStack inside UNetLab. In this post we’ll continue building on that by adding two new compute nodes and redesigning our network to resemble something you might actually see in a real life.

In this post I’m going to show how to get a running instance of Openstack inside a UNetLab virtual machine.

The final post in a series demonstrates how to use the network-ci tools to safely replace a core routing protocol inside a small Active/Standby Data Centre.

In this post I’ll demonstrate how to use the network-ci tools to automate the build, test and upgrade of a small 4-node network topology.

Traditionally, the first post in the series describes how to setup a development environment. This time I’ll do it DevOps-style. I’ll show how to use Packer to automatically create and configure a VM with UNetLab and Jenkins pre-installed.

In this series of posts I’ll introduce the tools I’ve been using for continuous network development and how they can be used with automation servers like Jenkins for network continuous integration and delivery.

In this post we’ll look at how to create arbitrary topologies and push configuration to Nodes in UNetlab via REST SDK. We’ll conclude by extending our sample application to create and configure a 3-node topology and enable full connectivity between all nodes.

In this post I’ll show how to build REST SDK to authenticate, create labs and nodes in UnetLab. I’ll briefly cover the difference between composition and inheritance design patterns and demonstrate how to use test-driven development.

In this post I’ll show how to setup environment for UnetLab REST SDK development on Windows. I’ll be running UNL inside a VM and using PyCharm as Python IDE on the host OS.