May 18, 2020 update: Some of the information in this blog is no longer up-to-date. For the most recent update to CitC, please see the “A new era for Cumulus in Cloud” blog.
First of all, we’re thrilled to announce that today we launched OpenStack with Cumulus in the Cloud. That means that you can now test out Cumulus Networks technology with an OpenStack environment easily and at zero cost to you.
I’ve written previously about Cumulus In The Cloud (CitC) when we first released it a month ago with Mesos as the initial release flavor. Since then, JR Rivers and his team have been diligently working on adding additional flavors to the CitC offering. I could not have been happier to hear the good news that they had integrated an OpenStack solution with the cloud testing framework. (We’ve also replaced the Mesos with Kubernetes, but that’s for a different post!)
I immediately launched my own free instance of Cumulus in the Cloud using the standard steps. I was greeted with a new option where I could pick the flavor of CitC I wanted to initiate:
Since I had already experimented with Kubernetes, I was eager to tinker with OpenStack to better learn this technology.
To be upfront, I am not an OpenStack expert. I have been diligently learning it over the past six months ever since a majority of my customer engagements have involved private cloud deployments leading with OpenStack. As a network engineer first, one of the uncharted territories of my knowledge is the container and application networking. As I outlined in my previous post, I was able to leverage the Mesos deployment (now Kubernetes) on CitC to learn more about container networking. I was hoping to do the same in this OpenStack deployment.
Once my instance was launched I was greeted with a similar homepage:
I could have selected the Horizon console to launch the VM instance from a GUI, but this time I wanted to play around with the OpenStack CLI so I could feel more like a hacker. Plus, I had previously done everything in the Mesos deployment with the Marathon GUI, so I felt like trying something different.
In this environment, server01 is set up as the OpenStack controller with server02, server03 and server04 as the compute nodes. Before I could issue any OpenStack commands, I needed to source the authentication parameters which were in the home directory of server01.
I started off by checking the components of OpenStack with which I was familiar. The most basic of things to check was the current images available, flavors of deployments and networks created.
This output started to align with the OpenStack experience that I had previously. With that information validated, I wanted to launch a virtual machine using the Cirros image, with a nano side flavor and associated with the provider network.
And there it was, the VM was launched, but I wanted to validate that my VM was actually launched successfully.
Now that the VM was launched, I logged into it to test connectivity:
Wow! I was starting to get a hold of this OpenStack business. It was really nice to have a safe environment in which I could play around and learn various different OpenStack commands. That’s all I had time for in this initial test, but I’ll be sure to update you all in future posts about the interesting things you can do with Cumulus in the Cloud.
If you would like to try the technology out for yourself, simply make an account here.