Transcript
In this screencast, we are demonstrating federation across four different cloud service providers using OpenNebula. We will be demonstrating how OpenNebula provides a single pane of glass, a unified management interface for four federated cloud instances running on the different cloud service providers. For this specific setup, our four federated OpenNebula clouds are deployed across OVH Cloud, IONOS, Scaleway, and ADI data center Uscadi. Our goal is to showcase the centralized orchestration across these distinct providers. Let's look at the architecture of this federation. We have designed the OpenNebula installation on OVH Cloud to act as the master node. The other three environments, Scaleway, IONOS, and ADI, are configured as slave zones. The OVH node is in Rabot, France. The IONOS node is in Berlin, Germany, while Scaleway node is in Paris, France. And finally, ADI is in Bilbao, Spain. The OpenNebula front-end's control traffic integration uses a hybrid connectivity model. We have public internet connection to Scaleway and IONOS, while our connection to ADI is secured through a private networking via the VPN. In the following demo, we will manage the lifecycle of our virtual machine workloads directly from the master OpenNebula web interface located on OVH Cloud. First we will perform an infrastructure inspection, reviewing the available federation zones and listing the hypervisor hosts available on each. Then controlling everything from the master zone, we will deploy a virtual machine into each specific zone to prove orchestration capabilities. Finally, we will access the root console of the deployed virtual machine to confirm the connectivity and status. Let's inspect the federation infrastructure. As mentioned, we have four OpenNebula instances, Scaleway, Atlantic Data Infrastructure, also known as ADI, OVH Cloud, and IONOS. In this federation, OVH Cloud is acting as the master node, while the other three are configured as slaves. We are currently logged into the front-end of OVH Cloud. From here we can inspect the infrastructure and see which hosts we have available for each deployment. Right now looking at OVH Cloud zone, we can see that two instances are available as hypervisors. Now we change the view to the IONOS zone. You can see two different instances acting as the IONOS deployment. Next we will look at ADI. Here we can see a private IP address listed. This is because we are connecting to the Atlantic Data Infrastructure via the VPN. Finally we check Scaleway, where we also have a single hypervisor host available. Now we are going to demonstrate the deployment capabilities. Starting with Scaleway, we will instantiate a virtual machine on each of the federated cloud deployments. We will select the Scaleway zone and name the instance VM on Scaleway. We won't change any configuration parameters, we will simply create this virtual machine. We'll wait a moment for the virtual machine to deploy and verify it comes up and running. As you can see, the virtual machine is now running on Scaleway. Next we change the infrastructure zone to ADI. You can see a different set of virtual machines already running in this installation. We verify that these hosts belong to ADI infrastructure and then instantiate a new virtual machine here, naming it VM on ADI. As before, we are going to leverage the default configuration. We are going to wait for a while until the scheduler is going to place the VM into the ADI infrastructure. Continuing to IONOS, currently there are no virtual machines running. We will choose a name and instantiate a new virtual machine called VM on IONOS. As usual, we are going to wait just a little bit until virtual machine becomes available. Finally, we will also instantiate a new virtual machine on our master node, OVH. We'll name this one as VM on OVH and wait for the infrastructure to make it available. Now, we are going to access one of the virtual machines through the VNC console interface. We are able to log in as the root user. You can see here that we are able to run a few commands and we have full root access to the console. That concludes our demonstration of the federated deployment across four cloud providers using Open Nebula. This work has been made possible in the scope of IPSCIS project. Thank you for watching and see you in the next screencast.
