WEBVTT 00:00.000 --> 00:13.840 Okay, the next talk is up and it's here in Karees and Luis Vineras on Lupos, the French 00:13.840 --> 00:15.680 government's sovereign cloud. 00:15.680 --> 00:17.880 Welcome, and the stage is yours. 00:17.880 --> 00:18.880 Thanks Felix. 00:18.880 --> 00:24.680 Thanks everyone for joining today, I know it's second day of first time, so it's more 00:24.680 --> 00:25.680 difficult. 00:25.680 --> 00:30.480 We'll talk about digital sovereignty and not just about the importance of doing it, but 00:30.480 --> 00:36.160 more practical example of people doing it today using open source solutions. 00:36.160 --> 00:42.040 So Luis is going to co-present with me, is a master student in European affairs at 00:42.040 --> 00:47.560 Cionspo Paris, also an apprentice at the Public Finance General Directorate at the French 00:47.560 --> 00:54.160 Finance Ministry, and the Labour IT Association co-founder and president, Labour IT is a group 00:54.160 --> 01:00.600 that's trying to increase the option of open source in student activities, I think. 01:00.600 --> 01:04.640 And my name is Tirek Karees, I'm the General Manager for the Open Infra Foundation, which is 01:04.640 --> 01:08.240 the Stuart behind the Open Stock Project. 01:08.240 --> 01:12.800 I'm also the Vice Chair of the Open Source Initiative, the body that defends the open source 01:12.800 --> 01:19.080 definition, and I've been a really manager for Open Stock for the last 15 years, so that's 01:19.080 --> 01:27.660 why I'm helping giving some extra context to this project, because Nubo is based on an 01:27.660 --> 01:34.200 open stack cloud, and so I wanted to give a quick history of why Open Stock plays a role 01:34.200 --> 01:36.240 in digital sovereignty. 01:36.240 --> 01:41.480 So Open Stock is an openly developed open source solution for cloud software, basically 01:41.480 --> 01:45.720 if you want to provide infrastructure, if you want to do what Amazon web service or Google 01:45.720 --> 01:50.400 compute cloud does, there is open source software that's available out there to help you 01:50.400 --> 01:51.400 do it. 01:51.400 --> 01:57.480 It's developed by a global community, actually more than 50% of our recent activity over 01:57.480 --> 02:03.320 the past two years is coming out of Europe and the Middle East Africa and for only 20% 02:03.320 --> 02:10.520 in North America and 30% in the Asia Pacific region, and you might have heard that Kubernetes 02:10.520 --> 02:15.400 killed Open Stock or made it to relevant, the reality is that it actually reinforced 02:15.400 --> 02:22.240 Open Stock because Kubernetes provides a really nice way to abstract the infrastructure 02:22.240 --> 02:28.120 and deploy containerized applications, and so if you want to do that on top of Amazon web 02:28.120 --> 02:32.320 services, you can do that with Kubernetes as well, and if you want to do that on top of 02:32.320 --> 02:36.720 Open Stock Trif and Resources, you can do that as well, so that actually put Open Stock 02:36.720 --> 02:40.000 more on the map than you just tried it. 02:40.000 --> 02:44.440 In terms of Open Stock today, we're actually celebrating the 15th birthday this year, it's 02:44.440 --> 02:49.560 really the edge of maturity, so it's bit like the Linux kernel, mostly new developments 02:49.560 --> 02:55.160 is driven by new advancement in hardware capabilities or new type of workloads that need 02:55.160 --> 03:01.120 to be enabled through technologies accessible to all. 03:01.120 --> 03:05.320 For the past year, we've seen three key trends that drive a lot of new adoption for 03:05.320 --> 03:06.720 Open Infrastructure. 03:06.720 --> 03:12.680 The first one is clearly AI, like everyone has been hearing about it by now, it requires 03:12.680 --> 03:18.280 a lot of new capacity, new accelerated capacity, and so people that are deploying that 03:18.280 --> 03:24.080 capacity today are using software that's only available to do that. 03:24.080 --> 03:29.800 There's also a lot of people that are escaping the VMware new aggressive licensing since 03:30.000 --> 03:35.320 Vortcom both VMware, people have been receiving invoices that could be tenfold what 03:35.320 --> 03:41.200 they used to pay, and so clearly those people are climbing up to find solutions, and for 03:41.200 --> 03:45.800 the most adventurous that also wanted to drive a cloud transformation more of a programmable 03:45.800 --> 03:50.840 approach to infrastructure, Open Stock is there as an option, and the third driver, which 03:50.840 --> 03:55.520 is why we're here today, is digital sovereignty. 03:56.520 --> 04:02.000 Well, there is a clear need today more than ever for local infrastructure. 04:02.000 --> 04:09.680 It's clear that we need programmable computing infrastructure to sustain our software 04:09.680 --> 04:17.080 driven economy, and that means we need access to resources that you can access programmatically 04:17.080 --> 04:18.920 with cloud APIs. 04:19.000 --> 04:26.480 At the same time, this is only offered, or mostly offered by US or China-based providers. 04:26.480 --> 04:34.320 So how do we get that access without being vulnerable to weaponizing access? 04:34.320 --> 04:41.160 Like tomorrow, the new US president could just say, well, it's illegal for Amazon 04:41.160 --> 04:47.880 web service to continue delivering services in your what then, like how much of our economy 04:47.880 --> 04:48.880 is going to crumble. 04:48.880 --> 04:53.240 We need to build that local capacity today, because even if it doesn't do it, it will 04:53.240 --> 04:59.960 use it in threats to drive some, or as a way to negotiate something else, and we'll have 04:59.960 --> 05:04.240 to give in on something else, because it doesn't push the button. 05:04.240 --> 05:10.160 We also need, even without taking like this step, which used to be crazy now, not that 05:10.160 --> 05:11.160 crazy. 05:11.160 --> 05:14.880 You also need to resiliency against State Actual Espionage. 05:14.880 --> 05:20.080 There is low in the US that allows the government to actually force any US-based company 05:20.080 --> 05:24.480 to disclose information that's about foreign industry. 05:24.480 --> 05:29.920 So there is ends that has been used for State Actual Espionage by the US by China, and 05:29.920 --> 05:32.640 for anything that's localized there. 05:32.640 --> 05:36.800 So even for our industry, it's very important that we have this local capacity. 05:36.800 --> 05:43.200 And finally, even without the current geopolitical trouble, we have very progressive privacy 05:43.200 --> 05:48.200 laws in the EU, it's very important that our data is protected by our laws, and that 05:48.200 --> 05:55.200 needs our data needs to be stored in the jurisdictions where that law applies, otherwise 05:55.200 --> 06:00.640 we just lose this benefit of living in the EU. 06:00.640 --> 06:01.640 So why open source? 06:01.640 --> 06:05.320 Why open source helps with this goal of building local infrastructure? 06:05.320 --> 06:10.440 Well, it has several properties that are very interesting, availability, it's the fact 06:10.440 --> 06:16.680 that using open source software, you actually have permission as access to that technology. 06:16.680 --> 06:18.320 You don't need to ask anyone for permission. 06:18.320 --> 06:24.120 You don't need to have the permission of the US government before using open source. 06:24.120 --> 06:25.400 So you can just take it. 06:25.400 --> 06:33.640 There is independence, the fact that it's provided by a collection of participants, open 06:33.680 --> 06:38.120 level by your wide community of organizations. 06:38.120 --> 06:42.040 That gives you, you don't have a dependency on a specific actor. 06:42.040 --> 06:48.600 You don't buy it from one company, which could be influenced in doing something else. 06:48.600 --> 06:52.400 So you have this independence, you have this transparency, the governance is very open, 06:52.400 --> 06:55.400 every discussion is happening in the. 06:55.400 --> 07:01.360 So it was in the 2008 economic crisis, the governments proposed the symbols package called 07:01.400 --> 07:05.920 investment plan for the future and within that plan had many different objectives. 07:05.920 --> 07:11.600 Couple of them were to modernize and industrialize the state-friendly hosting infrastructures 07:11.600 --> 07:17.680 of the state and industrialize also computing environments for the state IT teams. 07:17.680 --> 07:23.760 All of that obviously needed to meet the needs of security and resilience, be interministerial 07:23.760 --> 07:29.480 by default and enhance state sovereignty. 07:29.480 --> 07:34.600 With these objectives in mind, a team, which was then we taken by Rune Shaya, who is now 07:34.600 --> 07:39.640 the current director and founder of the new project, they proposed the two projects. 07:39.640 --> 07:46.360 So the first part is a set of tooling to create an open source cloud, meaning management 07:46.360 --> 07:51.360 industrial scale, cloud infrastructure, so provisions to VM, buildings, as well as upgrades 07:51.360 --> 07:53.080 without downtime. 07:53.080 --> 07:57.480 And they insisted that those tooling needed to be based on free software and specifically 07:57.480 --> 08:00.840 community divisions of the free software and welcome back to that a bit later. 08:00.840 --> 08:05.240 The second part of the project was an interministerial hosting offer, obviously based on the 08:05.240 --> 08:12.200 open source cloud tools so that other public administration can consume pay as you go resources 08:12.200 --> 08:19.160 and benefit from the industrial scale security and customer support that we have at Kibo. 08:19.160 --> 08:22.520 That's a quick rundown on the milestones, I won't get into the details, I just want you to 08:23.160 --> 08:30.680 remember two key dates, the first production set up of the first platform in July 2018, 08:30.680 --> 08:35.800 and then the customer portal and sender of excellence in November 2019. 08:35.800 --> 08:41.640 Also notable is the four major open-secret rates thanks to Kula Ansible 08:41.640 --> 08:44.680 through the span of several years. 08:46.920 --> 08:50.760 The offer assistance today, we have two independent and autonomous sites. 08:50.840 --> 08:56.920 Within each site, we have two platforms, one is exposed to the internet, the other is exposed 08:56.920 --> 09:02.760 to the internal network of the state area and within the two platforms, you have two 09:02.760 --> 09:04.120 availability zones. 09:05.960 --> 09:08.680 We deploy all those open-secret components. 09:09.560 --> 09:16.040 We also do observability through open source components and last but not least, we have the 09:16.040 --> 09:20.520 customer portal for onboarding and support, which is quite important. 09:21.720 --> 09:28.040 When it comes to the numbers, we have about 450 projects, about 2,000 tenants and lot more 09:28.680 --> 09:34.520 VMs and VZPs, all that is serving daily 15 different public administrations. 09:35.320 --> 09:40.840 And it keeps growing so much so that now we have a new offer named Kibo, which is a 09:40.840 --> 09:46.200 named space as a service software, so it's based on Kubernetes and Pluster API. 09:46.200 --> 09:50.040 And as Terry said, Kibo can be inside open-sec and that's what we're doing. 09:50.760 --> 09:57.720 It's a Kibo, the offer is a whole tenants inside open-sec and using the the new 09:57.720 --> 09:58.760 ball APIs. 09:59.960 --> 10:05.960 Now let's talk about the Terry talk about free software and the sovereignty behind it. 10:06.360 --> 10:11.720 Let's see how free software can really be the chosen path for sovereignty. 10:12.280 --> 10:16.760 Before that, I just want you to make a distinction between product and project. 10:16.760 --> 10:21.560 I made this distinction, thanks to Bestangiri, maybe you know him. 10:21.560 --> 10:25.000 I urge you to read this blog post about it, it's in French, but it's great. 10:25.560 --> 10:26.680 So basically, we have two things. 10:28.440 --> 10:29.320 We have two things. 10:29.320 --> 10:34.040 We have the products, the products is just the source code and the license and the license dictates 10:34.040 --> 10:35.720 how you can use the source code. 10:35.720 --> 10:39.400 In some cases, the documentation is also part of the product. 10:39.400 --> 10:43.000 For example, the Apache license, the documentation is part of it. 10:43.000 --> 10:44.440 And the product is everything else. 10:44.440 --> 10:50.760 So it's maintenance, it's support, it's built pipelines, it's PR's emergency issues and so on. 10:50.760 --> 10:51.480 It's everything else. 10:52.440 --> 10:57.080 And that's very important to make the distinction, I believe, because then we can make a 10:57.080 --> 10:59.480 difference between formal freedoms and real freedoms. 11:00.040 --> 11:04.840 And using free software for the state cloud, the sovereignty, 11:04.840 --> 11:06.520 using it as a product. 11:06.520 --> 11:10.040 So meaning we only care about the code and the license behind it. 11:10.040 --> 11:12.840 It enables us to have the four essential freedoms, 11:12.840 --> 11:16.440 which enables us transparency over the code that we use, 11:16.440 --> 11:17.400 taken over the product. 11:18.040 --> 11:21.640 So one answer would be, well, maintain your own fortune, 11:21.640 --> 11:24.360 but we use way too many products. 11:24.360 --> 11:27.800 And so that's not feasible and it's not desirable. 11:27.880 --> 11:30.680 We want to pull resources with free software, not separate them. 11:31.800 --> 11:34.280 And that's where the community versions of free software really 11:34.280 --> 11:36.280 shines for digital sovereignty. 11:36.280 --> 11:41.000 Because they allow us the possibility to take part of the contribution, 11:41.000 --> 11:43.320 the collaboration, and the governance process. 11:43.320 --> 11:50.120 And that's how we can better control how the project is handles 11:50.120 --> 11:51.320 when we participate in it. 11:52.600 --> 11:55.960 If we do that, though, then we need to internalize competencies, obviously. 11:56.920 --> 12:00.600 But that's, at the French Finance Ministry, 12:00.600 --> 12:03.960 we're quite lucky because they have been doing so for quite a long time. 12:03.960 --> 12:07.000 And it's one of the largest information system of Europe. 12:07.880 --> 12:09.640 So that's a great thing. 12:09.640 --> 12:12.680 And obviously, digital professor internalized competencies 12:12.680 --> 12:13.880 rather than licenses. 12:13.880 --> 12:17.880 So from the 2000s, early 2000s, as you can see, 12:17.880 --> 12:21.800 they have developed skills mainly if not exclusively 12:21.800 --> 12:25.000 based on free software about virtualization and so on. 12:25.000 --> 12:28.360 And as you can see also, they chose a possible skill 12:28.360 --> 12:30.280 over Oracle for the databases. 12:32.040 --> 12:35.000 We haven't given a definition yet of sovereignty. 12:35.000 --> 12:37.640 It is one of the most controversial ideas in political science 12:37.640 --> 12:41.160 and international law, but I'll try to give it a shot 12:41.160 --> 12:44.200 in the context of a state platform. 12:44.200 --> 12:48.600 So if sovereignty refers to the ultimate authority in the decision-making process 12:49.640 --> 12:51.320 or the state and in the maintenance of order, 12:51.320 --> 12:53.800 then in the context of the state cloud, I define it 12:53.800 --> 12:57.160 as a computing environment that is owned, controlled, 12:57.160 --> 12:59.320 and operated by the state. 12:59.320 --> 13:01.880 That way, as Terry said, we can ensure that the data 13:01.880 --> 13:05.720 and services are satisfactory and regulated by 13:05.720 --> 13:08.200 or own laws and only all laws. 13:10.280 --> 13:13.000 At that's different, and contrary to just mere independence. 13:14.120 --> 13:17.640 Obviously, you can control the infrastructure of AWS cloud, 13:17.640 --> 13:20.360 but you do not own it and you do not operate it. 13:20.360 --> 13:22.200 And I'm not even mentioning the US cloud 13:22.200 --> 13:24.600 Ag material is talking about. 13:24.600 --> 13:25.720 Even OV is clouded. 13:25.720 --> 13:26.440 You don't own it. 13:26.440 --> 13:27.800 You don't operate it. 13:27.800 --> 13:29.320 The company can go out of business. 13:29.320 --> 13:29.960 You don't have it. 13:29.960 --> 13:33.640 That's what we need local free software to have full sovereignty. 13:35.000 --> 13:37.800 So where are we going from here? 13:37.800 --> 13:39.480 That's the conclusion. 13:39.480 --> 13:41.800 First of all, we want you to thank the new boat project 13:41.800 --> 13:45.640 wants to thank the grid community for the past 20 years. 13:45.640 --> 13:48.520 Free software has given a lot of benefits and independence. 13:49.320 --> 13:50.760 And that's great. 13:50.840 --> 13:53.640 We have contributed to renewable to open the Swiss Open 13:53.640 --> 13:55.160 Stackman HQ and so on. 13:55.160 --> 13:59.320 Luckily, though, it's a bit more difficult due to the migration 13:59.320 --> 14:00.600 of the central SDBN. 14:00.600 --> 14:04.760 So we're lagging a bit behind the OpenStacker latest updates. 14:04.760 --> 14:08.040 So contributing relevant patches is a bit more complex. 14:09.000 --> 14:13.480 Looking ahead, though, we have the Cuba offer that was talking about. 14:13.480 --> 14:16.280 That's a cluster API in Kubernetes distribution 14:16.280 --> 14:17.800 that we want to open source. 14:17.800 --> 14:19.160 So that's coming up. 14:19.160 --> 14:23.240 And we are committed to increasing or contribution both 14:23.240 --> 14:25.480 internally with the genome. 14:25.480 --> 14:28.760 I don't know if anyone here from the genome here is here. 14:28.760 --> 14:31.080 So that's what we're going to do. 14:31.080 --> 14:34.840 And also externally by sharing our expertise and contributing 14:34.840 --> 14:36.200 back to the projects. 14:37.720 --> 14:39.160 And that's about it. 14:39.160 --> 14:40.520 So thank you for your attention. 14:40.760 --> 14:45.480 APPLAUSE 14:45.480 --> 14:46.200 Questions? 14:46.200 --> 14:47.880 No? 14:47.880 --> 14:48.680 Questions? 14:48.680 --> 14:49.480 Questions? 14:49.480 --> 14:50.440 All right. 14:50.440 --> 14:51.400 Well, we have time for questions. 14:51.400 --> 14:51.880 So. 14:51.880 --> 14:52.680 Right timing. 14:52.680 --> 14:54.680 Yeah, thanks. 14:54.680 --> 14:59.480 Do you aim to provide a higher security 14:59.480 --> 15:01.480 application and good infrastructure? 15:01.480 --> 15:03.960 And do you, uh, like, what's, sorry? 15:04.040 --> 15:07.960 Uh, there is a, uh, no, hopefully, 15:07.960 --> 15:10.600 the qualification, which is called, uh, 15:10.600 --> 15:11.400 was not there. 15:11.400 --> 15:12.440 Ah, yeah, okay. 15:12.440 --> 15:15.400 Which is required for high, uh, the federal security. 15:15.400 --> 15:18.200 Uh, do you aim to provide it in a way? 15:18.200 --> 15:19.960 And the second question, uh, 15:19.960 --> 15:21.960 the world is allowed to do, 15:21.960 --> 15:23.960 which is, uh, for the, uh, 15:23.960 --> 15:25.960 you have to do something. 15:25.960 --> 15:27.960 Uh, no, no, I don't focus on that. 15:27.960 --> 15:29.000 Okay. 15:29.000 --> 15:29.800 Uh, okay. 15:29.800 --> 15:32.440 So, um, just if you need to, uh, 15:32.440 --> 15:33.560 she's my boss. 15:33.560 --> 15:34.840 Can you repeat the question? 15:34.840 --> 15:35.160 Okay. 15:35.160 --> 15:41.160 So the question is, um, um, 15:41.160 --> 15:43.240 do we plan on having, uh, 15:43.240 --> 15:44.760 division on this country, which is a high, 15:44.760 --> 15:46.280 it's a qualification for security. 15:46.280 --> 15:48.440 And also do we work with the club peer, right? 15:48.440 --> 15:50.040 So, as I was saying, saying, 15:50.040 --> 15:50.600 she's my boss. 15:50.600 --> 15:53.080 I'm, uh, I'm, uh, I've been here for just, uh, 15:53.080 --> 15:53.800 a few months. 15:53.800 --> 15:56.680 So maybe, uh, I don't want to say anything bad. 15:56.680 --> 15:59.960 Um, that's like, just this lemme, uh, 15:59.960 --> 16:01.880 we don't have the division on this country. 16:01.880 --> 16:04.680 Yes, not yet, but we're planning on having it. 16:04.680 --> 16:07.400 We have a set of qualification for security, uh, 16:07.400 --> 16:11.320 it's, um, which is mainly based on the second-plad, uh, 16:11.320 --> 16:12.120 qualification. 16:12.120 --> 16:13.080 It's not second-plad. 16:13.080 --> 16:14.680 We're also planning on having that. 16:14.680 --> 16:17.080 And, uh, we want to work with, 16:17.080 --> 16:20.440 with the, we work with the club peer, 16:20.440 --> 16:23.400 with club peer, uh, yeah, that's it. 16:23.400 --> 16:24.840 She's also another stack plan. 16:24.840 --> 16:27.160 Which is also, also an open stack plan. 16:29.560 --> 16:30.360 Any other question? 16:32.440 --> 16:33.480 Oh, way too many. 16:33.480 --> 16:34.200 He was first. 16:36.200 --> 16:38.760 Well, I was doing, but you had quite a lot of evidence 16:38.760 --> 16:40.680 in the heart situation, you know, more and more. 16:40.680 --> 16:42.600 How do you, how did you get the report, 16:42.600 --> 16:43.880 so you can divide what to, 16:43.880 --> 16:45.960 would I, uh, do you have the money? 16:45.960 --> 16:47.800 For the public and research, you mean? 16:48.600 --> 16:51.640 Um, I think it's also, uh, yeah, repeat the question. 16:51.640 --> 16:55.320 Um, how did we get so many tenants and projects in the cloud 16:55.320 --> 16:55.640 new book? 16:56.440 --> 16:59.720 Uh, I think one of the key things is 17:00.680 --> 17:03.400 the, uh, have you heard about the, 17:03.400 --> 17:04.440 the, the cloud doctrine? 17:05.240 --> 17:06.040 Maybe not. 17:06.040 --> 17:09.080 The cloud doctrine is, uh, the stake doctrine that now says, 17:09.080 --> 17:11.720 well, IT teams should use cloud infrastructures 17:11.720 --> 17:14.520 and on how their own local production 17:14.520 --> 17:15.400 things and everything. 17:15.400 --> 17:18.360 And because we're also very intermanuously and open, 17:18.360 --> 17:21.240 it's, it's, it's quite easy to get people to, to come in. 17:21.880 --> 17:22.280 Yep. 17:25.560 --> 17:29.560 What's the range of current different physicality 17:29.560 --> 17:32.360 projects, what do you have, what do you do structure, 17:32.360 --> 17:36.120 and how do you hide and in a situation like someone said, 17:36.120 --> 17:39.560 yeah, that's really interesting, but not project as two specials 17:39.560 --> 17:41.960 to get one to, uh, like five cities in his direction. 17:43.240 --> 17:44.440 Can you repeat the question? 17:44.440 --> 17:47.240 Yeah, no, you, uh, no, me, 17:47.240 --> 17:49.880 but, uh, simple version of the question. 17:49.880 --> 17:52.520 How do you come across situations where people have said, 17:52.520 --> 17:56.040 um, uh, our project is two specials 17:56.920 --> 17:57.560 two specials. 17:57.560 --> 17:58.600 Okay, here is two reason. 17:58.600 --> 17:59.720 Oh, yeah. 18:01.000 --> 18:02.280 How have you dealt with that? 18:04.280 --> 18:06.440 All right, uh, yeah, that happened. 18:06.440 --> 18:08.840 Uh, so the question is, uh, 18:08.840 --> 18:10.840 project that come into Nubo and say, 18:10.840 --> 18:13.240 is the, uh, our project is two specials, 18:13.240 --> 18:16.680 or requires too many security qualifications so on. 18:16.680 --> 18:18.040 Um, it happened. 18:18.040 --> 18:23.480 Um, basically what we did is they still tried, uh, 18:23.480 --> 18:27.480 the, opens the, the Nubo APIs for the project, 18:27.480 --> 18:29.160 by, because they're developing it, 18:29.160 --> 18:31.960 and also because we're working in parallel 18:31.960 --> 18:34.840 to get the security qualifications. 18:34.840 --> 18:37.960 So by the, by the time that their project is ready, 18:37.960 --> 18:39.160 we may have the qualification. 18:54.440 --> 18:59.640 Uh, how to tell the finance ministry to, 18:59.640 --> 19:02.760 to use an open-sac platform, basically. 19:04.120 --> 19:04.760 Yeah. 19:04.760 --> 19:06.120 Another finance ministry. 19:06.120 --> 19:07.480 Another finance ministry. 19:07.480 --> 19:14.120 Uh, uh, I don't have enough, uh, hindsight on the Nubo project, 19:14.120 --> 19:15.960 uh, right now, so I won't be able to tell it. 19:15.960 --> 19:17.480 Maybe you can say something about it. 19:19.480 --> 19:22.680 They're like open-sac clouds being used in other, uh, 19:22.760 --> 19:24.040 some other European countries. 19:24.040 --> 19:27.320 The problem is, like, I discovered the Nubo project by accident, 19:27.320 --> 19:28.680 by a LinkedIn post saying, 19:28.680 --> 19:30.280 oh, we did that with OpenStack. 19:30.280 --> 19:32.840 So some, and I live in France and I pay my taxes. 19:32.840 --> 19:38.360 Uh, and so I, like, it's sometimes super difficult to uncover. 19:38.360 --> 19:39.240 Government activity. 19:39.240 --> 19:41.640 There's a bit of a nickel chamber within the government. 19:41.640 --> 19:44.680 Might be well known, but outside, there is no, uh, 19:44.680 --> 19:49.320 it's not as actively public, or engaging as publicly as, 19:49.320 --> 19:53.880 and it's was great to see, uh, you all, uh, really, uh, 19:53.880 --> 19:57.080 starting talking about it, because that's really, uh, 19:57.080 --> 19:59.960 all of us to have that conversation and this presentation. 19:59.960 --> 20:01.960 And I feel like we know of other governments 20:01.960 --> 20:03.560 that are a deep learning of OpenStack clouds, 20:03.560 --> 20:06.600 but sometimes, um, they don't tell us. 20:06.600 --> 20:08.520 So it's, we're, I know, Estonia, I know, 20:08.520 --> 20:12.120 some of some in Italy, but it's super difficult to track where they are at, 20:12.120 --> 20:14.200 and because they don't communicate at all. 20:14.200 --> 20:15.720 And so it's super difficult. 20:15.720 --> 20:18.120 Maybe, maybe I can just add a few things. 20:18.280 --> 20:19.800 Um, those pose. 20:20.840 --> 20:21.880 Public, those pose. 20:21.880 --> 20:23.160 Open source program office. 20:23.160 --> 20:24.760 That's also a way to go. 20:24.760 --> 20:27.560 Uh, I don't know the, oh, yeah, yeah, I was, 20:34.040 --> 20:34.840 exactly. 20:34.840 --> 20:39.240 And also the, the, also the, the presentations just before us. 20:39.240 --> 20:40.680 I don't know if they're still here. 20:40.680 --> 20:41.480 That's about it. 20:41.480 --> 20:44.360 Like, trying to get the public and research, 20:44.360 --> 20:46.360 should be public about what they're doing. 20:46.440 --> 20:48.840 That's, uh, that's a, a huge work. 20:48.840 --> 20:51.320 And friends is part of a precursor on that, actually. 20:53.960 --> 20:57.800 Oh, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah. 20:57.800 --> 20:58.600 Come to Fausem as well. 21:05.160 --> 21:06.520 So can you speak louder, please? 21:09.480 --> 21:09.880 Yep. 21:10.520 --> 21:16.280 For the distribution of the open source, 21:16.280 --> 21:17.720 we don't have yet to line line. 21:17.720 --> 21:19.240 Yep, it's working on it. 21:19.960 --> 21:20.920 Ah, repeat the question. 21:21.800 --> 21:24.280 Is the, is the Cuba distribution? 21:24.280 --> 21:26.680 Do we have a timeline for the Cuba distribution? 21:26.680 --> 21:28.280 And now it, time's up. 21:28.280 --> 21:29.800 So thank you very much for your questions.