Okay, the next talk is up and it's here in Karees and Luis Vineras on Lupos, the French
government's sovereign cloud.
Welcome, and the stage is yours.
Thanks Felix.
Thanks everyone for joining today, I know it's second day of first time, so it's more
difficult.
We'll talk about digital sovereignty and not just about the importance of doing it, but
more practical example of people doing it today using open source solutions.
So Luis is going to co-present with me, is a master student in European affairs at
Cionspo Paris, also an apprentice at the Public Finance General Directorate at the French
Finance Ministry, and the Labour IT Association co-founder and president, Labour IT is a group
that's trying to increase the option of open source in student activities, I think.
And my name is Tirek Karees, I'm the General Manager for the Open Infra Foundation, which is
the Stuart behind the Open Stock Project.
I'm also the Vice Chair of the Open Source Initiative, the body that defends the open source
definition, and I've been a really manager for Open Stock for the last 15 years, so that's
why I'm helping giving some extra context to this project, because Nubo is based on an
open stack cloud, and so I wanted to give a quick history of why Open Stock plays a role
in digital sovereignty.
So Open Stock is an openly developed open source solution for cloud software, basically
if you want to provide infrastructure, if you want to do what Amazon web service or Google
compute cloud does, there is open source software that's available out there to help you
do it.
It's developed by a global community, actually more than 50% of our recent activity over
the past two years is coming out of Europe and the Middle East Africa and for only 20%
in North America and 30% in the Asia Pacific region, and you might have heard that Kubernetes
killed Open Stock or made it to relevant, the reality is that it actually reinforced
Open Stock because Kubernetes provides a really nice way to abstract the infrastructure
and deploy containerized applications, and so if you want to do that on top of Amazon web
services, you can do that with Kubernetes as well, and if you want to do that on top of
Open Stock Trif and Resources, you can do that as well, so that actually put Open Stock
more on the map than you just tried it.
In terms of Open Stock today, we're actually celebrating the 15th birthday this year, it's
really the edge of maturity, so it's bit like the Linux kernel, mostly new developments
is driven by new advancement in hardware capabilities or new type of workloads that need
to be enabled through technologies accessible to all.
For the past year, we've seen three key trends that drive a lot of new adoption for
Open Infrastructure.
The first one is clearly AI, like everyone has been hearing about it by now, it requires
a lot of new capacity, new accelerated capacity, and so people that are deploying that
capacity today are using software that's only available to do that.
There's also a lot of people that are escaping the VMware new aggressive licensing since
Vortcom both VMware, people have been receiving invoices that could be tenfold what
they used to pay, and so clearly those people are climbing up to find solutions, and for
the most adventurous that also wanted to drive a cloud transformation more of a programmable
approach to infrastructure, Open Stock is there as an option, and the third driver, which
is why we're here today, is digital sovereignty.
Well, there is a clear need today more than ever for local infrastructure.
It's clear that we need programmable computing infrastructure to sustain our software
driven economy, and that means we need access to resources that you can access programmatically
with cloud APIs.
At the same time, this is only offered, or mostly offered by US or China-based providers.
So how do we get that access without being vulnerable to weaponizing access?
Like tomorrow, the new US president could just say, well, it's illegal for Amazon
web service to continue delivering services in your what then, like how much of our economy
is going to crumble.
We need to build that local capacity today, because even if it doesn't do it, it will
use it in threats to drive some, or as a way to negotiate something else, and we'll have
to give in on something else, because it doesn't push the button.
We also need, even without taking like this step, which used to be crazy now, not that
crazy.
You also need to resiliency against State Actual Espionage.
There is low in the US that allows the government to actually force any US-based company
to disclose information that's about foreign industry.
So there is ends that has been used for State Actual Espionage by the US by China, and
for anything that's localized there.
So even for our industry, it's very important that we have this local capacity.
And finally, even without the current geopolitical trouble, we have very progressive privacy
laws in the EU, it's very important that our data is protected by our laws, and that
needs our data needs to be stored in the jurisdictions where that law applies, otherwise
we just lose this benefit of living in the EU.
So why open source?
Why open source helps with this goal of building local infrastructure?
Well, it has several properties that are very interesting, availability, it's the fact
that using open source software, you actually have permission as access to that technology.
You don't need to ask anyone for permission.
You don't need to have the permission of the US government before using open source.
So you can just take it.
There is independence, the fact that it's provided by a collection of participants, open
level by your wide community of organizations.
That gives you, you don't have a dependency on a specific actor.
You don't buy it from one company, which could be influenced in doing something else.
So you have this independence, you have this transparency, the governance is very open,
every discussion is happening in the.
So it was in the 2008 economic crisis, the governments proposed the symbols package called
investment plan for the future and within that plan had many different objectives.
Couple of them were to modernize and industrialize the state-friendly hosting infrastructures
of the state and industrialize also computing environments for the state IT teams.
All of that obviously needed to meet the needs of security and resilience, be interministerial
by default and enhance state sovereignty.
With these objectives in mind, a team, which was then we taken by Rune Shaya, who is now
the current director and founder of the new project, they proposed the two projects.
So the first part is a set of tooling to create an open source cloud, meaning management
industrial scale, cloud infrastructure, so provisions to VM, buildings, as well as upgrades
without downtime.
And they insisted that those tooling needed to be based on free software and specifically
community divisions of the free software and welcome back to that a bit later.
The second part of the project was an interministerial hosting offer, obviously based on the
open source cloud tools so that other public administration can consume pay as you go resources
and benefit from the industrial scale security and customer support that we have at Kibo.
That's a quick rundown on the milestones, I won't get into the details, I just want you to
remember two key dates, the first production set up of the first platform in July 2018,
and then the customer portal and sender of excellence in November 2019.
Also notable is the four major open-secret rates thanks to Kula Ansible
through the span of several years.
The offer assistance today, we have two independent and autonomous sites.
Within each site, we have two platforms, one is exposed to the internet, the other is exposed
to the internal network of the state area and within the two platforms, you have two
availability zones.
We deploy all those open-secret components.
We also do observability through open source components and last but not least, we have the
customer portal for onboarding and support, which is quite important.
When it comes to the numbers, we have about 450 projects, about 2,000 tenants and lot more
VMs and VZPs, all that is serving daily 15 different public administrations.
And it keeps growing so much so that now we have a new offer named Kibo, which is a
named space as a service software, so it's based on Kubernetes and Pluster API.
And as Terry said, Kibo can be inside open-sec and that's what we're doing.
It's a Kibo, the offer is a whole tenants inside open-sec and using the the new
ball APIs.
Now let's talk about the Terry talk about free software and the sovereignty behind it.
Let's see how free software can really be the chosen path for sovereignty.
Before that, I just want you to make a distinction between product and project.
I made this distinction, thanks to Bestangiri, maybe you know him.
I urge you to read this blog post about it, it's in French, but it's great.
So basically, we have two things.
We have two things.
We have the products, the products is just the source code and the license and the license dictates
how you can use the source code.
In some cases, the documentation is also part of the product.
For example, the Apache license, the documentation is part of it.
And the product is everything else.
So it's maintenance, it's support, it's built pipelines, it's PR's emergency issues and so on.
It's everything else.
And that's very important to make the distinction, I believe, because then we can make a
difference between formal freedoms and real freedoms.
And using free software for the state cloud, the sovereignty,
using it as a product.
So meaning we only care about the code and the license behind it.
It enables us to have the four essential freedoms,
which enables us transparency over the code that we use,
taken over the product.
So one answer would be, well, maintain your own fortune,
but we use way too many products.
And so that's not feasible and it's not desirable.
We want to pull resources with free software, not separate them.
And that's where the community versions of free software really
shines for digital sovereignty.
Because they allow us the possibility to take part of the contribution,
the collaboration, and the governance process.
And that's how we can better control how the project is handles
when we participate in it.
If we do that, though, then we need to internalize competencies, obviously.
But that's, at the French Finance Ministry,
we're quite lucky because they have been doing so for quite a long time.
And it's one of the largest information system of Europe.
So that's a great thing.
And obviously, digital professor internalized competencies
rather than licenses.
So from the 2000s, early 2000s, as you can see,
they have developed skills mainly if not exclusively
based on free software about virtualization and so on.
And as you can see also, they chose a possible skill
over Oracle for the databases.
We haven't given a definition yet of sovereignty.
It is one of the most controversial ideas in political science
and international law, but I'll try to give it a shot
in the context of a state platform.
So if sovereignty refers to the ultimate authority in the decision-making process
or the state and in the maintenance of order,
then in the context of the state cloud, I define it
as a computing environment that is owned, controlled,
and operated by the state.
That way, as Terry said, we can ensure that the data
and services are satisfactory and regulated by
or own laws and only all laws.
At that's different, and contrary to just mere independence.
Obviously, you can control the infrastructure of AWS cloud,
but you do not own it and you do not operate it.
And I'm not even mentioning the US cloud
Ag material is talking about.
Even OV is clouded.
You don't own it.
You don't operate it.
The company can go out of business.
You don't have it.
That's what we need local free software to have full sovereignty.
So where are we going from here?
That's the conclusion.
First of all, we want you to thank the new boat project
wants to thank the grid community for the past 20 years.
Free software has given a lot of benefits and independence.
And that's great.
We have contributed to renewable to open the Swiss Open
Stackman HQ and so on.
Luckily, though, it's a bit more difficult due to the migration
of the central SDBN.
So we're lagging a bit behind the OpenStacker latest updates.
So contributing relevant patches is a bit more complex.
Looking ahead, though, we have the Cuba offer that was talking about.
That's a cluster API in Kubernetes distribution
that we want to open source.
So that's coming up.
And we are committed to increasing or contribution both
internally with the genome.
I don't know if anyone here from the genome here is here.
So that's what we're going to do.
And also externally by sharing our expertise and contributing
back to the projects.
And that's about it.
So thank you for your attention.
APPLAUSE
Questions?
No?
Questions?
All right.
Well, we have time for questions.
So.
Right timing.
Yeah, thanks.
Do you aim to provide a higher security
application and good infrastructure?
And do you, uh, like, what's, sorry?
Uh, there is a, uh, no, hopefully,
the qualification, which is called, uh,
was not there.
Ah, yeah, okay.
Which is required for high, uh, the federal security.
Uh, do you aim to provide it in a way?
And the second question, uh,
the world is allowed to do,
which is, uh, for the, uh,
you have to do something.
Uh, no, no, I don't focus on that.
Okay.
Uh, okay.
So, um, just if you need to, uh,
she's my boss.
Can you repeat the question?
Okay.
So the question is, um, um,
do we plan on having, uh,
division on this country, which is a high,
it's a qualification for security.
And also do we work with the club peer, right?
So, as I was saying, saying,
she's my boss.
I'm, uh, I'm, uh, I've been here for just, uh,
a few months.
So maybe, uh, I don't want to say anything bad.
Um, that's like, just this lemme, uh,
we don't have the division on this country.
Yes, not yet, but we're planning on having it.
We have a set of qualification for security, uh,
it's, um, which is mainly based on the second-plad, uh,
qualification.
It's not second-plad.
We're also planning on having that.
And, uh, we want to work with,
with the, we work with the club peer,
with club peer, uh, yeah, that's it.
She's also another stack plan.
Which is also, also an open stack plan.
Any other question?
Oh, way too many.
He was first.
Well, I was doing, but you had quite a lot of evidence
in the heart situation, you know, more and more.
How do you, how did you get the report,
so you can divide what to,
would I, uh, do you have the money?
For the public and research, you mean?
Um, I think it's also, uh, yeah, repeat the question.
Um, how did we get so many tenants and projects in the cloud
new book?
Uh, I think one of the key things is
the, uh, have you heard about the,
the, the cloud doctrine?
Maybe not.
The cloud doctrine is, uh, the stake doctrine that now says,
well, IT teams should use cloud infrastructures
and on how their own local production
things and everything.
And because we're also very intermanuously and open,
it's, it's, it's quite easy to get people to, to come in.
Yep.
What's the range of current different physicality
projects, what do you have, what do you do structure,
and how do you hide and in a situation like someone said,
yeah, that's really interesting, but not project as two specials
to get one to, uh, like five cities in his direction.
Can you repeat the question?
Yeah, no, you, uh, no, me,
but, uh, simple version of the question.
How do you come across situations where people have said,
um, uh, our project is two specials
two specials.
Okay, here is two reason.
Oh, yeah.
How have you dealt with that?
All right, uh, yeah, that happened.
Uh, so the question is, uh,
project that come into Nubo and say,
is the, uh, our project is two specials,
or requires too many security qualifications so on.
Um, it happened.
Um, basically what we did is they still tried, uh,
the, opens the, the Nubo APIs for the project,
by, because they're developing it,
and also because we're working in parallel
to get the security qualifications.
So by the, by the time that their project is ready,
we may have the qualification.
Uh, how to tell the finance ministry to,
to use an open-sac platform, basically.
Yeah.
Another finance ministry.
Uh, uh, I don't have enough, uh, hindsight on the Nubo project,
uh, right now, so I won't be able to tell it.
Maybe you can say something about it.
They're like open-sac clouds being used in other, uh,
some other European countries.
The problem is, like, I discovered the Nubo project by accident,
by a LinkedIn post saying,
oh, we did that with OpenStack.
So some, and I live in France and I pay my taxes.
Uh, and so I, like, it's sometimes super difficult to uncover.
Government activity.
There's a bit of a nickel chamber within the government.
Might be well known, but outside, there is no, uh,
it's not as actively public, or engaging as publicly as,
and it's was great to see, uh, you all, uh, really, uh,
starting talking about it, because that's really, uh,
all of us to have that conversation and this presentation.
And I feel like we know of other governments
that are a deep learning of OpenStack clouds,
but sometimes, um, they don't tell us.
So it's, we're, I know, Estonia, I know,
some of some in Italy, but it's super difficult to track where they are at,
and because they don't communicate at all.
And so it's super difficult.
Maybe, maybe I can just add a few things.
Um, those pose.
Public, those pose.
Open source program office.
That's also a way to go.
Uh, I don't know the, oh, yeah, yeah, I was,
exactly.
And also the, the, also the, the presentations just before us.
I don't know if they're still here.
That's about it.
Like, trying to get the public and research,
should be public about what they're doing.
That's, uh, that's a, a huge work.
And friends is part of a precursor on that, actually.
Oh, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah.
Come to Fausem as well.
So can you speak louder, please?
Yep.
For the distribution of the open source,
we don't have yet to line line.
Yep, it's working on it.
Ah, repeat the question.
Is the, is the Cuba distribution?
Do we have a timeline for the Cuba distribution?
And now it, time's up.
So thank you very much for your questions.