Okay, hi everyone, thank you so much for being here.
In today's session, we are going to discuss open source approach to the hybrid cloud.
First, let me introduce myself.
My name is Victor Palma, Cloud Engineer at Open Nebula.
It will be a pleasure to be with you here in this session.
First, I would like to do a quick overview of the current state of the hybrid cloud scenario.
First of all, I would like to introduce a question of what is the hybrid cloud.
Surely most of you already know what is the hybrid cloud,
but for those who don't, the hybrid cloud is the union of the public cloud and the private cloud.
So you can have your own premise cloud in front.
And in certain circumstances, maybe you need to expand your cloud in order to cover on demand resources.
So when you did that using public cloud resources,
we can say that you are using an hybrid cloud scenario.
So the hybrid cloud has a lot of benefits like flexibility, disaster recovery,
cost optimization.
But I think the relevant ones are the two related to security and the edge computing.
Security and compliance is I think that is a topic that is very, very important to know where it is.
For example, Europe, we have a lot of regulations related to the privacy of the user.
So we need to find a way to complete and to meet that regulations.
Thanks to the hybrid cloud, we can deploy in our public cloud provider in the Europe,
cluster in order to have all the information of the user in Europe and meet that regulation.
And the other relevant point is that you are computing.
So in order to offer all that application that works in real time like I or 5G connectivity or even video games,
video game streaming, we need to use this kind of service in the India,
India to the user in order to reduce the latency.
So we have some challenges here, most of them related to the complexity and the integration of this kind of architecture in our clouds.
So it's very difficult to handle all the different providers that we can find in the market.
Like for example, AWS or equine source, Calway or even others, new cloud providers, like I think that we have a lot of them.
So each of them has different nomenclatures, different names, different workflows, and you need to adapt your cloud to them.
It's a very big challenge that the hybrid cloud needs to cover.
And the other one is related to the cost and resource management of the hybrid clouds.
Of course, we can use the hybrid cloud to optimize the cost of our cloud.
But uncontrollable resources can in certain situations lead to unexpected costs that we are.
We're going to find on the end of the mode, a very big, a very big build to pay for example to the public,
I'll provide that with we are using.
So in order to face all these challenges, we are going to see a technology stack,
a technology stack, of course, an open source, a technology stack for cover all these hybrid cloud scenarios.
So first of all, of course, we are going to use a kvm and hypervisor.
So we are going to use the, the very foundation that we have an any Linux system in order to create and define all the build on machines that we are going to create.
We can of course use another hypervisor if you need it, but I think that kvm is the more general use case hypervisor that we can find currently in the Linux ecosystem.
So in top of that, we are going to use OpenNevola as a cloud orchestrator. OpenNevola has a lot of capabilities like the orchestration of virtual machines,
based in kvm and in others hypervisor as well.
You can manage application containers and even Kubernetes clusters.
So you can do that in your own on premise data center in the public cloud or even in the edge.
And also since it's a main philosophy of mine of OpenNevola, openNevola tries to avoid vendor locking.
So we want to create a solution that is at no sticks to the providers.
My, as my college journey speak in the, in the previous session.
So we are going to use OpenNevola as a multi cloud orchestrator orchestrator.
So we can with OpenNevola deploy any application like VMs, multi VMs, Kubernetes clusters, everything in a shared environment.
Then we have the feature to handle all of all these resources in a uniform management layer.
So we can use an homogeneous layer to handle all the resources that we have in AWS, in econics or even in our own clouds of course.
So that gives us the opportunity to use any infrastructure, not only our own premise infrastructure.
So we can migrate move from even life, migrate applications.
And we all time with no, don't time as you are as we are going to see later.
If you want to get more information about all the information that I'm talking about right now, you can go to OpenNevola.io, multi cloud where we have more information and some use cases related to these features.
So there we are going to introduce the technology that we are going to use to achieve all the, to face all the challenges that we have to, to fit during the, to be the deployment of our hybrid cloud that is one form.
One form is a tool that we are currently developing here at an openNevola, some open source tool as well.
And it's the foundation of the automatic provisioning in the public in the public cloud and even in the it edge cloud.
So one form is an extension of openNevola that use terraform for provisioning resources and uncivil to configuring all the stuff in the notes.
So, thanks to one form, we are able to deploy a cluster, sorry, a multi cloud infrastructure in just 50 minutes and in some cases under 50 minutes.
So it's a very quick deployment, a very quick provisioning that we can do thanks to this platform.
So we are going to take a look in depth to one form as a key tool for the hybrid cloud management.
So first of all, you can see here a dictionary definition of what is one form as I already said one for is a new tool that allows you to automatically deploy and configure new clusters in the public cloud into your openNevola cloud.
So it is just a definition of a formal definition, but thanks to one forms, you can deploy and provision in not only clusters, but host, of course, and networks, that are stories, virtual routers, VMs and multi VMs applications.
And all of these resources are supported by the openNevola multi-tenancy capabilities from a single portal.
So you can handle them with the same management lawyer using the same workflow for the different kinds of resources.
So here are two concepts I want to clarify first, we have first the provider.
The provider is where we are going to deploy, we are going to create the resources like the public cloud provider that we are going to use, and then we have the provision that is what we want to deploy, we want to provision in the public cloud.
So the provider for one form is just a bunch of credential in order to connect to the public cloud provider and request all the resources that we want to create later.
And a provision is the template and document that define all the resources that we want to create in or a public cloud provider.
I would like to say that we can use the same provision with different providers. So the provision, the document that define a provision, is at no state to the provider.
So we can reuse the same infra that we can define in a provision file to different providers.
Some of the features while is the template system that I already mentioned, the multi provider support, of course you can create different providers in the same platform.
And of course the ultimate cluster deployment is the core of all of these features.
But we also have some interesting features like the lifecycle management. So you cannot, you can deploy the provision for example in AWS.
And you can of course stop and delete all these resources, but you can also update this provision in real time.
A scale disk provision based on your needs on rules, predefined by the cloud administrator and you can even hold the provision and power of the provision in order to save resources.
One forms, one forms also develop it with the main idea in mind of the extensible and customishable is an open source tool.
So we want to anyone can add the own cloud provider to the platform.
So it's very easy to expand it with more configuration files.
We are adding a lot of guides to your documentation in order to be user-friendly, the integration of new cloud providers to one form.
Of course it also provides an API. So you can use it to create your own tool or to integrate these tool with all your third party tools in order to create automations and other workflows.
So as I really said, one form is based in the integration with OpenNLLA with Terraform and Ansible.
So starting from the Terraform site, here you can see a comparison between the info that one form provisioning using Terraform in AWS, this is an example for AWS.
And the configuration that one form creates in OpenNLLA.
In from the provider point of view, Terraform creates in this case a BPC subnet to connect for instances in this case, a public gateway and all the IP routes in cooperation that need in order to enable the confusion to the internet.
From the OpenNLLA point of view, one forms, one form creates, of course, the same number of hosts.
The BX lang in order to connect to provide intermediate communication between the virtual machines and all the configuration related to the data stories where we are going to restore all the images of our virtual machines.
So this is completely up and up to the provider. So it's one form who is going to decide what resources I'm going to create depending on the provider and it's going to automatically configure that configuration in OpenNLLA in order to handle all the resources seamlessly.
And from the Ansible part, one form relies on one deploy. One deploy is another OpenNLLA tool. That's of course open source as well.
That use a lot of Ansible Playbooks in order to configure OpenNLLA notes and frontends. The OpenNLLA frontends, the machine, the server where you install the OpenNLLA demo that is in charge of handling all the OpenNLLA services and the notice David Polication note.
So in this case, we use in one form, one deploy in order to configure these notes. This tool is very powerful. So in case you are thinking about try OpenNLLA, if you recommend it because if you know how to launch an Ansible Playbook, you are going to know how to use the one deploy tool. It seems it's based on an Ansible as well.
So we have some use cases for one form. Of course, the first one is the automatic H++. It's cluster provisioning. So you can deploy a cluster and less than 50 minutes. It's very awesome that you can do that fully automated. Then we have the option. The use case to use a multi cloud distributed applications in or OpenNLLA cloud. So you can deploy multi BMS.
Sorry, a multi cloud application for example, half a cluster distributed in different locations.
An application deployed at the same time and connected in the different cluster of different providers and different locations.
I'm finally, of course, provides the hybrid cloud expansion to your cloud. You can expand your cloud to the public cloud. Any time you need automatically based on demand of the resources of your current cloud.
So now it's the showtime. I don't know today the network connection is a mess. It's pretty unstable. So I'm going to share some screenshots about the process.
I'm going to show you how the process is. But in case you want a lift demo of all these process, we have our screencast that we recently upload to your YouTube channel.
So I really recommend it to take a look at this screencast. But I'm just going to comment how this works.
Here in this license, what I don't know, the Wi-Fi today is terrible. So here you can see a definition of from the info point of view of what we can deploy using one for.
We can deploy from the Open Nebula system portal using the one for website that it has another interface separate from Open Nebula. You can define the providers and you can define index example three different providers.
So you can create different clusters in the different providers. In this case, we have one classroom in Germany another one in Amsterdam and the last two in Paris and Poland.
So you can deploy that from the info point of view and from the application point of view, you can create a multi-bying application that is going to be automatically deployed at the same time in these four clusters.
So we have in this case an example you see Minayo, that is a very, very powerful tool for monitoring and all the things. So from here you can, for example, create a cluster with three VMs, we H.A. configuration, automatically and distributed in the in the cloud.
So you are going to use this for, for that for a store objects and get this distributed ecosystem.
Here you can see an screenshot of the one form providers tables. So from here we can add any provider that we want and it and that was supported in the platform.
For example, we can use this scale way AWS or Econys, but we can add any credentials of any any cloud provider that we want in order to use it and as I said, play before.
And if we try to deploy a provision is in the provider, we are going to get this. For example, this is the the Frankfurt cluster that is located in AWS.
It is, it will, AWS is the provider for this cluster and we define a couple of hosts in this case with the own IP, the own resources and all of them provisioned automatically integrated automatically in open NAWLA.
For an cloud open NAWLA cluster administrator, this host are going to be the workflow with this course are going to be the same as the host that you can have in your own premise infrastructure.
So then once we have the infrastructure deployed, we can go to the NAWLA public marketplace in order to download the my own multi-known service appliance.
So it's automatically configured in order to create the meaning and service selecting the nodes where we want to deploy it.
If we go to well to the service template, if you want to learn more about how open NAWLA works, we have a lot of tutorial in our YouTube channel.
But if we go to the template section and try to instantiate this service, we are going to get in a few minutes, this dashboard is my dashboard that is deployed distributed along a multi cloud setup.
So as closing folks and next Steve that we are working on in this tool, I would like to say that one for is currently in development.
So we will launch this tool along open NAWLA setting O. Open NAWLA setting O is the start of that we call the one next cloud generation.
So it's going to have a lot of new feature related to provisioning, hybrid cloud AI that we are working on as part of the IPCI project.
This tool is going to replace one provision. If some one of you knows about open NAWLA, maybe you heard this name in the past, is that touch preview that we had before, but we are redefining one form based on what we learn about one provision.
So the focus that we have with this tool are mainly two. First, we want to integrate as many providers as we come.
We are listening to the community in order to see what providers they are using and what providers are the game changers of these hybrid cloud scenario.
And then we are also trying to optimize the provisioning time even more. So within that we can improve more the time that we dedicate to the provisioning, making more optimization for the Ansible part, and maybe for the Terraform as well.
So I also would like to say as I said before that this project is funded by the EPCI-CIS project, the Net Generation Erupeet platform for the Data Center cloud edge continuum.
So if you want to learn more about this project, you can go to the URL that you can see there in the bottom.
And I also encourage you to participate in our forum, as I said before, we are developing the Net Generation for the cloud open source platform.
We are listening to the community. We are seeing what the community needs and what the user demands. So please participate in the forum and let us know what did you expect from the next open NAWLA cloud generation.
So thank you so much. So see you have any question. It's now the moment.
Thank you. Questions? Can you speak more louder please?
Can you repeat the question? Can you repeat the question?
So I'm sorry. He asked about this. It's a defensive to deploy, of course, a bare metal industry in WBS.
You say for what reason we want to do that? What? It's depending on the use case as always, but it's more oriented to the scenario where you have your own premise infrastructure and you want to be able to attend peaks of demands of resources.
In that case, you don't have the time to go to your data center and put more service. For that kind of a scenario or even for the cloud edge, it will be interesting. But of course, as I said during the first slides, one of the challenges that we face with the high recloud is just the cost that the environmental instance it has.
So that's right. Any other questions?
Thank you so much.