All right.
Perfect.
So, let's hope that we don't get this.
Perfect.
So.
All right.
We're going away from CERN, but we stay in Taitlan, so let's welcome Victor and give him some applause.
Hello, everyone. Thank you so much for being here.
In today's session, we are going to see how to deploy a hyperconverting infrastructure with F across the cloud edge continuum.
But first, let me introduce myself.
My name is Victor Palma, cloud engineer at Open Nebula.
I come from Madrid, Spain, and I've been working for Open Nebula for more than two years.
Developing an innovative new feature for the cloud edge world.
So, first, we are going to start with some theory and then my idea is to show you a demo of all the things that we are going to see here.
Well, first, we need to do the question of what is the cloud edge continuum?
The cloud edge continuum is just an environment of nodes on the edge,
distributed in multiple locations and everything interconnected using the same management layer.
So, some advantages of the cloud edge continuum are the deployment of low latency applications.
Since we are deploying our application near and closely to the final user,
we can also reduce the energy consumption that our application does since we are deploying the application in a small data center, not in a big one.
We can also reduce the vendor dependency since we are not deploying our application in a standard data center like cloud or AWS.
We are deploying our application in multiple locations and managed by any provider that we want at any time.
Then we can improve the user experience using the cloud edge continuum for our applications.
Since it's related to the first point, since we are deploying our application near to the user,
the experience and the latency is going to be low.
We can also expand the service ability. It's very easy to duplicate and replicate our applications in different locations, different servers.
We can deploy our application, for example, one cloud edge in Paris, another one in Madrid.
If we want to replicate that, it's very easy to replicate the same infrastructure in Lisbon or London and so on.
Finally, we can reduce data transfers and reduce security rigs since we are running all of this in a local location near to the user.
The data transfer we need to transfer from our application to the user is more closely.
How can we manage all of this? How can we manage the applications in the cloud edge continuum?
First, we need to have a set of clusters of bare metal servers.
Ideally, running KVNC is the mostly popular hypervisor.
Then we need a uniform management layer for handling and managing all these locations, the private cloud associated with that.
Then we need to interconnect all these clusters.
Finally, we need to provide a multi-tenancy environment in order to create several users and groups and isolate each environment in the cloud edge.
We are going to see now an example of how a cloud edge is inside.
This example is a scenario for a 5G radio.
We have this cloud edge node connected to the 5G radio using an edge land and two servers.
The idea of the cloud edge is only to have a small number of servers.
In this case, we have two, running the KVNC hypervisor.
We can run in this hypervisor any application that we want.
For example, a Kubernetes cluster for handling all the 5G code and workloads.
We can also use the virtual GPUs of the server if it is available for data processing.
All the servers inside this node are connected to the Internet through this public network using a single VLAN.
The idea of the cloud edge node is to be autonomous as possible.
If the single management ledger that we are going to use is not accessible, this site can work alone and without any problem.
It can still provide service to the user.
Now we are going to bring these ideas to life and see how all these concepts match together in order to create our cluster.
How can we deploy the cloud edge in the node?
We are going to use three main technologies.
The first one is OpenNevola.
It is a platform for orchestrating virtual workloads.
Then we are going to use Terraform to automate the resources deployment.
Then we are going to use Ansible for the configuration site for installing the packages that we are going to need.
We don't need to use Ansible and Terraform directly.
We are going to use these technologies through the OneProvision portal.
That is our OpenNevola tool that allows us to automate all the configuration of the nodes and deploy the cloud edge nodes in an instant with a few steps.
OneProvision supports several providers in order to create our own cloud node on the edge like GCloud, AWS, or GAYJax.
Some of them are currently in development so not all are available.
We are going to use AWS for the example of the today's issue.
I would like to see more closely what is OpenNevola in order to understand the environment that we are going to see in the today's demo.
OpenNevola, as I already said, is a platform that allows you to orchestrate and manage all your virtual machines, application containers, or Kubernetes clusters,
all of them in the same way, in a very easy daily operation.
You can deploy all these applications or all these workloads using your own private cloud or expand your cloud to the public cloud or on the edge.
OpenNevola has integrations with several third-party tools like Terraform, Kubernetes, Ansible, and Docker.
It also has its own built-in tools like a Sunstone UI, the graphical user interface, the web portal that we are going to use to interact with OpenNevola.
We can create workloads in different hypervisors like BingWare, KBM, LXD, or file crackers.
You can handle in the same way a micro-BM or a virtual machine. It doesn't matter for OpenNevola.
Then, we have the possibility in OpenNevola to expand our cloud to the multi-cloud or to the hybrid cloud.
In the case we have, for example, our own data center and we need more resources, we can deploy any infrastructure with automatic provision using, for example, providers like GCloud, AWS, or Equinix.
Then, we have a uniform management for that resources with a homogeneous layer for users on workload management.
Then, deploy the infrastructure, any application that we want. For example, as I already said, we can create Kubernetes clusters or Docker or virtual machines and so on.
Well, we are going to use for the deployment of our cluster, thev as a storage solution.
But why thev? We are going to see thev basically because it's an easy way to distribute the storage of our cloud, of the file, of our virtual machines,
and share all the storage between the cloud etching nodes in a very, very easy way.
So, thev at OpenNevola has implemented the storage basis on thev that with simple configuration, you can add multiple clusters or pools to OpenNevola.
This storage implements replication and consistency and some important features for thev data storage in OpenNevola are snapshots, clone operations, encryption, et cetera.
Regarding thev at the edge, as I already said, we need first a small number of nodes in our cloud etch node.
Thev storage is going to be dedicated to store VMs in the scheme image.
It's not necessary to have high storage requirements because we can use a multiple option for the storage.
It has lowest storage requirements.
And this is ideal for run in a HCI configuration because we can create nodes everywhere with a reduced cost.
So, thev storage in OpenNevola consists of three different types of servers.
We have the full nodes that run the Thev OSD and the monitor daemons as well, the KVN hyperbysos as well.
We have the OSD nodes to run the Thev OSD daemons and the hypervisor only nodes that, as the name said, only runs the hypervisor.
Here we have a sample of a comparison side by side from the point of view of the Thev storage from the AWS and from OpenNevola.
For AWS we need to configure first a VPC, defining the metal bar servers, all the reaching tables, all the configuration that we need for our infrastructure.
And from the OpenNevola point of view we just only need to create our host and automatically associate it with the Thev storage and we can start to create workloads on that servers.
So, we are going to do a little demo on how we can do this using OpenNevola.
So, let me...
I don't know.
Displays, sorry.
Okay, that's better.
So, this is the OneProvision portal that we are going to use to create the cloud HNO.
Here we can see a general overview of the clusters, hosts and data storage that we have already in our infrastructure.
So, we are going to take a look to each section.
For example, here we can see the providers that we have already configured.
I have configured here the AWS provider for Frankfurt.
It's the example that we are going to see here, but we can create any provider that we want.
For example, AWS or Reqinys or on-prem.
Here you can select the location for the provider and when you finish this process, a provider is just a set of credentials that it's going to...
OneProvision, the thing that OneProvision do is use the API endpoint of each provider in order to create the host on the servers, on the provider.
So, it's just a set of credentials in order to connect to that endpoint.
Using Terraform.
Then we have the provision that are the provision providers.
Here I have already a provision created.
I'm going to show you this provision as an example, but we are going to see how the process is.
I've already one created because deploying a note on the edge can take around 30 minutes.
So, in order to avoid that, we can see here, for example, this class already created and running.
For creating a new edge note, it's very easy.
We just need to click on the add button.
We can see here a description or the different options that we have, the support of virtualization technologies, etc.
And we can set here if we want to create a edge cluster or if we want to create a HCI cluster using the app, that's the option that we are going to use.
Next, we can select the provider that we want to use.
In this case, it's going to be AWS Frankfurt.
General attributes like the name, the description.
And here we can tune in our note, setting the number of instances.
The number of instances for only hypervisors or for only the OECD, etc., the DINIAS servers.
The image that we want to use in the host.
All of this configuration is also accessible through Jamel files.
And we can set, for example, here if we want to use virtual machines or micro-VNs using LXC, etc.
I'm going to back scenes.
This takes some time, but the result is this.
A cluster created in the edge in a very, very easy way.
So what is the result of this?
We are going to see here this is the main OpenEvula dashboard.
The OpenEvula system is the user interface, the web user interface.
So here we can see all the virtual machines that we already have.
We have some VMs already running here.
If we go to the exception, we can see here three nodes deployed on the edge inside this cluster.
That is the cluster that we have created using OneProvision.
We can create and deploy VMs in a very easy way, downloading an appliance for the OpenEvula marketplace.
So for the Docker marketplace, if we want to deploy containers in our cloud, we are going to deploy a VM as an example.
So for example, we can, this one, one of the Pine Linux.
We can set here, for example, for example, we can even set the host that we want to use inside the cluster.
For example, we are going to use this one, but we can change any configuration of that VM.
We are going to instantiate the VM.
And here we can see that the VM is starting to be created.
So we are going to take a few seconds since it's an edge location, but it's booting and it's running.
It's totally running.
We can see here the host where the VM is running, the start time.
A lot of configuration regarding the VM, like capacity or other storage and so on.
And we can even connect to that VM.
Oops, sorry.
Maybe it's not so totally ready.
And this one?
Okay, I think that is the, I don't know if the Wi-Fi or maybe something is blocking the connection to the VM, but believe me, it's working.
It's working on my machine.
But that's all regarding the demo.
As you can see, it's very easy to create filter machines in Open Nebula on the, using a Cloud Edge node.
So returning to the slide.
Okay.
Well, that's the demo environment that we show you.
As final conclusion, the necessity of this project and this integration with the Open Nebula are support for them in spaces, support for incremental backup in theft, adopt theft image, live migration.
We want also to improve HCI configurations and integrate the one provision tool with the one deploy project that we already have.
It's another public project that you can visit on GitHub that automates all the configuration and install of Open Nebula.
And you are more than welcome to contribute to the repository on GitHub.
And I also encourage you to contribute to our community.
Join to the forum and share your experience using Open Nebula and help other users in order to create our Cloud open source community.
So this project is funded by the European Union.
So it's very interesting, the project.
It's Cognite, so you can visit here the URL.
And it's Cognite tries to provide a cognitive serverless experience to the European Union.
So we can, the idea of this project is to using Open Nebula and one provision create a lot of Cloud Edge nodes in Europe in order to deploy application and gains independence.
So that's all. Thank you very much for your attention.
Questions?
How do you deal with network outage, especially in the Edge?
Sorry, can you repeat the question?
How do you deal with network outage, especially in the Edge where the connection might not be stable?
How can we handle the network connection when it's not stable?
The idea of the Edge nodes are that in this kind of a scenario, the node is totally independent.
So it's still working even if you don't have a connection to the Internet, at least to the region.
I don't know if that answered your question.
Yeah?
Just to understand the configuration of the nodes in this form.
So from the diagram I see that you can deploy, as I said, the storage subsystem on the same nodes we are running as the virtual machine.
Is that correct?
But you need dedicated nodes for the storage side and the VMs.
He's asking about if we can deploy in the same node the storage and the virtual machines and the other workloads.
Yeah, you can deploy in the same node.
From OpenEvola point of view, it's only one node.
But behind it's handled in the splitting between the nodes and the hypervisual nodes.
But for the user that uses OpenNegulites, the host where he can deploy VMs and use their storage.
So yeah.
Any more?
Thank you.