WEBVTT

00:00.000 --> 00:07.000
We have an agenda.

00:07.000 --> 00:11.800
For this, we are, you know, discussing about cloud, about virtualization, and you have

00:11.800 --> 00:14.400
the first question for the audience.

00:14.400 --> 00:24.840
Maybe you are not representing working for some cloud service providers here, yes, telcos,

00:24.840 --> 00:30.440
cloud, and companies, well, you have your own company, okay.

00:30.440 --> 00:37.040
We can see that your C-Satmins or cloud admins, your managing cloud infrastructure, your daily

00:37.040 --> 00:46.640
basis, yes, cloud admins not, okay, perfect, let's see, what about all this stuff about

00:46.640 --> 00:47.640
the H?

00:47.640 --> 00:51.960
There's no H is a lot of, you're marketing, and there's some people, you know, they're working

00:51.960 --> 00:58.240
telcos that have to cover at the end to provide connectivity, you know, at the mile, you

00:58.240 --> 01:01.880
know, for IoT platforms.

01:01.880 --> 01:08.560
The contest model with the H is this, I want to introduce more or less, what is the situation

01:08.560 --> 01:09.560
now?

01:09.560 --> 01:14.920
The vision, you know, in this case for Europe, the idea for Europe, maybe something that you

01:14.920 --> 01:21.640
do, yes, real, that now in 2025, we have more than 80 percent, no, that this, this smart

01:21.640 --> 01:26.440
connected object is, we represent the computation, you know, that we are using, in this

01:26.440 --> 01:31.320
case distributed, maybe with AI is not in this way, but in this case, that at the end

01:31.320 --> 01:36.600
for this centralized computing facilities in hyper scholars, we are not scaling like

01:36.600 --> 01:42.560
planet, okay, with this and with the idea for the commission to have this 10,000 H nodes

01:42.560 --> 01:49.520
by 20,000, they will define about what is the kind of this H nodes, and at the end, we

01:49.520 --> 01:58.120
can, the, our enterprises will be reached 75% of cloud services, you know, by 20,000, this

01:58.120 --> 02:04.360
is more or less, you know, you have your ball and you have the feature here, and, and

02:04.360 --> 02:10.720
the end, we want to focus in 5G, my colleague, previously, explain how in this case open

02:10.720 --> 02:17.280
Ebola is trying to cover in this vertical tool, you know, that is clear that H, you know,

02:17.280 --> 02:23.120
is in, you know, dealing with the connected to 5G, you know, and distributed systems.

02:23.120 --> 02:28.240
For this, there is a specific, you know, you know, the H computing observatory, we know

02:28.240 --> 02:33.840
it more or less taxonomists to see that we are talking in the same, or we are, we are

02:33.840 --> 02:39.920
in the same page, not with this in mind, what about H, I don't know, you have any definition,

02:39.920 --> 02:46.160
one of the main drivers for the H is Latency, as you can imagine, yes, have you see another

02:46.160 --> 02:52.800
thing out of Latency to distribute these services more near the user to have, you know, more

02:52.800 --> 03:00.080
be the stream and 4K, 8K, I don't know, we have the security part, you know, at the end

03:00.080 --> 03:05.360
in the H, we are in a different conditions than in our country H, data centers, all our

03:05.520 --> 03:10.000
on-prem, you know, and more or less we can define with this, we have to do that we have

03:10.000 --> 03:17.840
we are below 20 milliseconds of Latency, we are near the H, this is, you know, the current, you

03:17.840 --> 03:24.720
know, definition, with this in mind, let's go, we also have to fulfill these kind of things,

03:24.720 --> 03:30.000
we have a specific program, it was presented in the last first and last year and we will present

03:30.080 --> 03:38.640
the first outcomes of this program, this program is out of 3 billion, 3 billion euros

03:38.640 --> 03:43.360
that they are different member states, you know, are providing to solve these kind of things,

03:43.360 --> 03:48.800
the first is to you know, to enable this multi provider, real multi provider cloud edge continuum,

03:48.800 --> 03:55.520
in this case open navela was born from years ago thinking about that we need private clouds,

03:55.920 --> 04:02.640
2025 we are in the same way, we need private clouds, only that this private clouds can be consumed

04:02.640 --> 04:08.800
or built in a different ways, it's going to pure this H, what is our idea in our own project

04:08.800 --> 04:13.040
in the EPCI, said the end we have all these technologies stuff that has to be distributed in

04:13.040 --> 04:18.640
the continuum, until you know, the platforms that can be some thousand of kilometers, you know,

04:18.640 --> 04:25.840
of your offices, or of your user maybe, or that is near the devices that need this time of

04:25.840 --> 04:31.440
common activity, with this private of latency we can see at the end that we need some

04:31.440 --> 04:36.480
technological stuff to cover this and this is where we are working for, in this case the vision of

04:36.480 --> 04:42.720
open navela as you know is that we are working now in like and silos and to distribute all this

04:42.720 --> 04:48.640
computing is only you know based in verticals, you have use in a provider if you are for

04:48.640 --> 04:54.000
using your CSV and your business model is to have more data centers well connected you know

04:54.000 --> 05:02.000
to distribute services but under your own you know technological stack, okay with open navela we

05:02.000 --> 05:08.720
are working you know to reduce this and to unlock the market because every company can you know

05:08.800 --> 05:15.680
distribute and have a real multi-cloud private you know infrastructure this is something that we

05:15.680 --> 05:21.280
are working and for today you will see I am excited today is something that I want to explain to you

05:22.560 --> 05:27.200
because when we are talking about life migration like the last thoughts you are really focused

05:27.200 --> 05:33.440
to the same data center today you will see another thing that is very different and maybe you can

05:34.400 --> 05:41.200
but okay this war effect I don't know we will try with this in mind we are building a stack another

05:41.200 --> 05:50.800
stack yes for to cover this okay we want to we like yes for to cover this idea for this stack

05:50.800 --> 05:56.480
that we call built or a you know is the continuous reference architecture that we are working with

05:56.480 --> 06:05.360
120 companies in Europe in this large program is one to do this as here is some people it's

06:05.360 --> 06:12.320
represented that is participatory in built or a built or if you may but they all is the continues

06:13.040 --> 06:18.640
with this in mind all the links that you you have in you know in the first them website all these

06:18.640 --> 06:26.320
companies are in this cluster you can see and this is for my first questions you can be represented

06:26.400 --> 06:32.880
some CSPs like you know are sizless web some telcos and some you know companies that are

06:32.880 --> 06:39.760
producing technology can be open source or not in our thesis 100 10 open source you can install open

06:39.760 --> 06:47.600
nebula don't let them hit that and go with a quick start as you know okay with this in mind

06:47.600 --> 06:53.040
on all these companies this companies for this built or a cluster we are organizing this stack

06:53.120 --> 06:59.920
for integration for instance phenics is a company from Poland that I do in producing the phenics

06:59.920 --> 07:06.000
RTO I don't know you know for IoT open source RTO operating systems that can be integrated in

07:06.000 --> 07:11.760
this in this form from the application like this micro the operating system until you know

07:11.760 --> 07:17.520
the providers that will provide bar metal in this case is important we are in the game of bar

07:17.600 --> 07:25.520
metal consumption because with open nebula if we want to you know avoid looking we have to be more

07:25.520 --> 07:32.640
or less free your cloud your roles the infrastructure can be from another part okay with this in

07:32.640 --> 07:40.400
mind let's go with all the supply chain that only to understand the demo for this open nebula

07:40.400 --> 07:46.480
next generation you know and to cover all these continuous challenges has to be aligned you know

07:46.480 --> 07:53.760
to like to be very agnostic about this bar metal consumption but at the end organizing in some way

07:53.760 --> 08:00.560
how we consume this like with tools like to reform with open tofu and simple okay

08:02.560 --> 08:07.280
we you know we will provide all for all these distributed clusters some technological extensions

08:07.360 --> 08:16.800
for instance you have to you know deploy a specific application for AI federal learning for instance

08:16.800 --> 08:24.800
something that we will explain another another talk after this you know need you know GPU

08:25.360 --> 08:30.560
support you have you know more or less some confidential capabilities maybe in ARM

08:31.200 --> 08:35.280
this kind of things we will recover or is being covered by technology extensions and this next

08:35.360 --> 08:41.360
generation open nebula and at the end for what for the world all these applications and services

08:41.360 --> 08:47.360
at the end has to be you know in some way easily distributed you know in the continuum

08:48.160 --> 08:53.600
for help for at the end to fulfill the users that can be you know some different use cases

08:53.600 --> 08:59.360
from railway operations critical infrastructure uh cloud service providers and so on okay

08:59.360 --> 09:05.040
and this is the complete sub chain with this in mind there is another thing that appears here

09:05.120 --> 09:11.520
the data act you know you know what this something that is now we have to follow and all around the

09:11.520 --> 09:19.600
egress no will be free no in this case I don't know if we receive from hyper scholars and

09:19.600 --> 09:27.600
CSPs some you know some increase enough of the of the price but it will be real with this in mind

09:27.680 --> 09:36.240
and this idea we are following something okay we are following that we have to work with state

09:36.240 --> 09:42.960
this kind of infrastructure as you can see here this is real this is the first test bit of you know

09:42.960 --> 09:48.160
the EPCI around build position and orchestration and you can give here represented some different

09:48.160 --> 09:55.760
companies you can see hyper scholars you can see some companies that are offering barimetal like

09:56.640 --> 10:02.400
they are reserve centers computing centers uh some CSPs that are providing you know

10:02.400 --> 10:08.880
nested virtualization you know throw bms and at the end we will dis first test to fulfill

10:08.880 --> 10:18.400
the first test that with this idea if you see the architecture uh you know open nebula not more or less

10:19.120 --> 10:26.960
we have a specific front end um that is now here in in bit in the Netherlands

10:26.960 --> 10:34.640
uh bit is a CSP offering you know some ears and managed services and with this front end you know

10:34.640 --> 10:39.440
we have an initial marketplace you think in one key is our cluster distribution

10:40.320 --> 10:47.200
Minayo you know for to have your own S3 storage services you know that can be distributed

10:47.200 --> 10:54.080
and the typical WordPress you know that always is in the demos okay with this in mind we will demonstrate

10:54.080 --> 11:01.120
today that we have capable to have three things we will demonstrate a scalability portability you

11:01.120 --> 11:10.800
know I think that is the best one and um interoperability okay with in this case open nebula

11:10.800 --> 11:16.880
you can do these kind of things now 2025 with different providers you know that are you know

11:17.920 --> 11:25.760
exposing different IPIs are different ways to do things but at the end the way here is we are

11:25.840 --> 11:33.920
consuming barimetal okay with this test that as we explain uh for next step we will go with real

11:33.920 --> 11:42.960
world use cases um around Europe is something that is open uh please if you are working for a CSP

11:42.960 --> 11:48.240
and you are interested to be involved in this there is an now an open call that will is funded by

11:48.320 --> 11:55.360
Europe you know to go with open nebula in this case on all these stacked technology and start

11:55.360 --> 12:05.680
or being the game okay let's go about the overall of the architecture you don't know open nebula

12:06.320 --> 12:13.200
this front end at the end that can be you know on premises at the end we have different ways you know

12:13.200 --> 12:20.480
to deploy a dissolution you know is orchestrating all these clasters that are distributed in all

12:20.480 --> 12:26.000
these member states okay you can see from amazon web services from bionos, equinex or a

12:26.000 --> 12:34.240
university super computing in dansk in Poland okay let's go with the first and check in my

12:34.400 --> 12:44.000
blog let's go about the scalability in this can all these orchestrated we can do this kind of things

12:45.680 --> 12:52.720
and the first that we can do here why not is to distribute in this case a WordPress

12:53.520 --> 13:00.800
2000 machines all all these infrastructure as you can see from our front end and at the end

13:01.600 --> 13:09.120
um okay see how is our orchestrator is distributing you know in all these clusters you can see the

13:09.120 --> 13:18.160
pitches you know to have in the same way you know the world done okay and here I'm sure

13:18.160 --> 13:24.720
I will appear on what about networking no for instance and at the end each you know cluster

13:24.720 --> 13:30.080
has his own networking capabilities and offering public floating IPs to the world

13:31.120 --> 13:38.720
directly all that we saw at the end we will have these 2000 machines not in two seconds it's clear

13:39.280 --> 13:44.960
in these cases WordPress is a service that is with almalinus and all these stuff but you can do

13:44.960 --> 13:51.840
from the same you know front end at for people from the pops the psychops it will be can be

13:51.840 --> 14:00.320
automated you know with our terra from driver you know with our specific API you know Java

14:00.960 --> 14:08.720
Ruby etcetera okay with this in mind well for the second experiment interoperability

14:08.720 --> 14:16.720
it is more more complete in this way we will go you know and we reduce the complexity for this

14:16.720 --> 14:21.360
and the idea is from access from space into the in the logo you know we will you know

14:22.800 --> 14:30.560
deploy mean value you know in this case we have we have to the and one key for us only we have

14:30.640 --> 14:39.200
with some configuration with these appliance we are minayos in our marketplace you can see you know

14:39.200 --> 14:44.080
that we will you know in resistile as open and 80 only to avoid the SSL

14:44.080 --> 14:52.080
it's certificate but we can you know deploy in this case in dance why not this appliance

14:52.080 --> 14:59.120
digitally you know and we want to do the same in the rest of the sites that are you know here in

14:59.200 --> 15:05.200
this test but represented okay you can see here we can use the credentials that people you

15:05.200 --> 15:13.440
know in the context for this template and go to this okay next portability and this something

15:13.440 --> 15:18.960
that we have I think that we have we can have some extra discussion because it's important to

15:19.040 --> 15:29.520
see how we did this experiment in this case the chant chant what we will do okay with this in mind

15:31.520 --> 15:39.120
the idea you know is to have to do a live migration of a bien that now is in equinex in this

15:39.120 --> 15:47.680
bar metal to another location live migration okay between different data centers that are

15:47.760 --> 15:53.680
managed you know in the same way open nebula is to in this you have the same

15:53.680 --> 16:04.480
management layer from equinex you know to you know in this case will be dance you know and

16:04.480 --> 16:11.760
whether you know the process here this in our front end you will see the process that is in

16:11.760 --> 16:16.720
this way and this more or less about the networking thing we will you know go with a specific

16:16.720 --> 16:24.240
of our market place a specific war press in this case that we will deploy in equinex

16:24.240 --> 16:33.120
directly with this in mind the typical the information credentials okay about the network we will you

16:33.120 --> 16:39.040
know we will see in equinex public and private network and with this in mind we will proceed you know

16:39.120 --> 16:46.000
you will see here we will be the project is in you know in Amsterdam so equinex provider

16:46.640 --> 16:54.160
and now we will go you know to do this operation you know it will depend you know about you know

16:54.160 --> 17:00.240
the network this kind of things but from different than you can do this live migration you know

17:00.240 --> 17:06.960
and when we are you know in Poland we can you know attach another Nick with a new IP that you

17:07.040 --> 17:14.640
know have the front end in this case we were you know in Amsterdam two seconds we are

17:15.520 --> 17:38.400
impolent okay okay perfect I only want to maintain there this one okay this one okay

17:38.720 --> 17:51.200
is the first time that you see this live migration among two different sites different providers yes

17:52.800 --> 17:58.000
yes yes it is only that they can be important you know in first and twenty twenty five the first

17:58.000 --> 18:04.080
time that we saw this more or less you know in like a with public networks you know and

18:04.160 --> 18:17.840
agnostic to the provider you know it's that is really okay and yes the question we can go to the

18:17.840 --> 18:23.440
question and then we are at the end yes this is a manual action that can be automated you know

18:23.440 --> 18:29.360
so the NES change of the okay you can do all this it's only to you know to illustrate the the

18:29.440 --> 18:38.400
case and yes only for we saw this it's clear you have the presentation all the YouTube

18:39.520 --> 18:49.040
video with this and this is to the end and what we are doing for next and maybe you know we can

18:49.040 --> 18:55.920
be presenting in the next for them some results we will go with another applications and the

18:56.000 --> 19:01.360
importance here is the benchmark in results but for this kind of operations you are using

19:02.960 --> 19:08.800
public networks you know you are American condition with this and with this in in mind is something

19:08.800 --> 19:14.400
that we are working now now is there is an overline network from a big Islam that is distributed

19:14.400 --> 19:23.360
for a little disproviders if you want to see some details with this two main things this open call

19:23.360 --> 19:30.720
for CSPs please you can check our web and if you're interested in the in this kind of projects

19:30.720 --> 19:37.760
you are welcome you know to be part of open-nebula systems and change you know the European and the

19:38.640 --> 19:43.040
market perfect thanks for your attention and

19:43.040 --> 20:03.840
questions please out of the first question yes hello yes sorry I didn't

20:14.000 --> 20:20.960
so what's the point of the immigration to disrupt your disropting you know in this yes the question

20:20.960 --> 20:27.760
is that for this life migration that we are doing in this innovation you know project is the first

20:27.760 --> 20:35.040
face to go with no disruption if you automate this you can you know lose some things like you are

20:35.040 --> 20:41.040
doing in your data center here only to illustrate that we can do this but if you automate everything

20:41.120 --> 20:47.920
you can go like a near life migration we can so a warm migration call migration but we will be near

20:47.920 --> 20:53.680
the life migration the second question here is about we are what we are changing now the IT because

20:53.680 --> 21:03.360
it's the current conditions that we have with the network is some people is what we introduce the

21:04.320 --> 21:12.080
you can say that maybe you can use cloud flare not or another balancer to have you know the

21:12.080 --> 21:17.040
service you know and you can you know do this operation but for some use cases in the edge

21:18.000 --> 21:24.480
then that there the driver is latency you cannot go with this kind of approach is more or less

21:24.480 --> 21:30.800
the I don't know if this question can appear but it's the answer but we can discuss you okay

21:31.760 --> 21:32.800
yes for there

21:45.280 --> 21:47.280
about features

21:47.280 --> 22:05.920
yes the question is that we have some comparison you know with some of another solutions not

22:05.920 --> 22:11.840
like proxmox yes we have a specific some studies that you can check in our you know in our

22:11.840 --> 22:17.360
block that there is a specific composition from being aware with open nebula open stack with open

22:17.360 --> 22:23.280
nebula and proxmox with open nebula some of the highlights for this that you mentioned perfectly

22:23.280 --> 22:30.240
is multi-terrency and this cloud you know multi-cloud consumption you know this is out of the

22:30.240 --> 22:34.800
prices that can be another you know way to compare but this is our the two main things

22:41.840 --> 23:04.560
okay you have in separate way yeah you can see but this one by one not you know that this

23:05.520 --> 23:09.520
okay

23:16.480 --> 23:23.520
yeah yes the news for this is that the question is that about in confidential computing what is the

23:23.520 --> 23:29.840
plan no for us they are the first is that in the next quarter the A or M packages

23:30.800 --> 23:36.720
for all that your Raspberry is no will be available you know in two months you know for testing

23:38.080 --> 23:43.600
this is the first the second about confidential we have some feature with the data you know

23:43.600 --> 23:50.880
in rest but in use we are working to have in this case a constraint device through RM and confidential

23:50.880 --> 23:54.640
you know there are some projects that working with this you know linear I don't know if you were in the

23:54.720 --> 24:04.720
confidential Devroom no about attestation no very fires we are working with with this in mind and

24:04.720 --> 24:08.000
will be you know I think in the fall quarter in our run up

24:17.600 --> 24:22.480
yes that one of the T at the end will be consumed you know by the manual factors Intel or

24:22.480 --> 24:30.160
I think that the times that but we will be here some people from Open Nebula thanks for your time