 Oh, welcome to our session, the future of the next collaboration on development of adaptation from Japan. I have actually the script, but I try to speak English by myself. I'm Yohei Suzuki from the Cybertross Corporation, and I'm joined by many basket from the Alliance Always Foundation. Well, to start and briefly, I discuss about, you know, collaboration between the Cybertross and the Always Foundation, and I've been some mainly talk more, you know, about Almaniacs and the Foundation things. I think it's, we will show the, what do you say, we affect the focus on and how we are shaping our future. Oh, again, my name is Yohei Suzuki. I'm from the Cybertross. I'm, you know, I actually over 20 years, actually the experience in the, you know, persuading and monetizing and struggling based on the OSS business. It's a kind of, you know, exciting, but it really hard. And I'm, you know, I'm proudly and deeply involved with Almaniacs and the Miracle Innex Fusion. And Miracle Innex is a Red Hat Compatible OS in Japan since 2000. It's a significant part of this history, this part. I think it's Miracle Innex is kind of, you know, sounds a little bit, a little bit unique for the English people, I think. Sometimes ask me why the Miracle Innex is. This is because I just want to explain that the Miracle Innex is at the 2000. We're working in Japan. I founded the Miracle Innex Corporation. And they release Miracle Innex distribution. So name after Oracle, Oracle Miracle and Miracle Innex. That's it. So now let me introduce Benny-san a little bit for you to introduce yourself. So I'm Benny. I know that most of you are not here to hear my story. So I'm going to be brief. I have been an assistant for a number of years. I've been involved in open source. I moved from tech into community building. So that's where you'll see me mostly now. I love Star Wars. If you have noticed, my earrings are Millennium Falcons today. You can find me, if you have questions, you can either talk to us here. Obviously, you can find me on the internet. I realize we're not supposed to call it Twitter anymore, but that's fine. I'll just leave it there. Thank you, Benny-san. Okay, again, let's dive into our collaboration with Star Wars Foundation. As a collaboration with Cybertrust, we take a big step by combining our Miracle Innex with Armour Innex. It's really kind of a big decision for us. Back in May, we are proud to announce that Cybertrust has become a platinum member of the Armour Innex OS Foundation. Since then, I've been deploying our engineer to this Armour Innex community, like Madsen and the other people. We are totally fully committed to the Armour Innex Foundation as well as this community. Our goal is to create Red Hat Compatible OS to meet global standards of the Japanese quality. It's my goal. Okay, let's talk about refuelling, reflecting our Miracle Innex achievement. Actually, the Miracle Innex has been supported critical systems, especially for the industry system. For over 20 years, I think that is the experience and track record. Well, it definitely strengthened to the community continuity, I think. Miracle Innex is, as you already know, business-oriented OS. Like Red Hat Enterprise Linux, we worked hard to maintain with independent software vendors and independent hardware vendors to get their certification. It's really hard. It's the same for the Armour Innex. We decided to establish the Certification Siege to develop and strengthen the relationship with these vendors. Actually, the server trust is specialized in long-term support and OS' compriances. I think this OS' summit, some server trust engineer already presentation, we are focused on OS' comprising also. I think Armour Innex also focus on achieving FIPS 143 compliance and also providing software boom also. I believe that we aim to fully use cyber trust expertise like Linux things and compliance things in Armour Linux. That's what I want to talk about. Thank you. We want to cover it over to the Benison. You can start in a minute. Okay, so we're going to talk about our history, how we came to be. We're going to talk about, we'll just dive in, right? Anybody who has been around the Red Hat ecosystem for a while knows that this is kind of what we had for many, many years. It would start in Fedora, the playground, the testing, the proving grounds. They would get pulled down into Red Hat with a regular release and then CentOS would rebuild Red Hat, right? For many, many years. In 2019, CentOS introduced this thing called CentOS Stream. CentOS Stream sits between Fedora and Red Hat. It allows earlier adoption of the operating system. It allows deeper testing than has historically happened, but it's not the downstream version of CentOS, right? And then in December of 2020, Red Hat announces that they are shifting all of the resources that have historically been part of CentOS to CentOS Stream, effectively killing CentOS Linux. As a community, we all felt that change very strongly at its peak. CentOS had, I saw a number somewhere in the neighborhood of 7 million servers online. That is a huge community to just be left adrift. So our founder, the person behind our Genesis Igor, who was the CEO of Cloud Linux announced he would be backing CentOS replacement. That announcement happened in January of 2021. And by March, we had a board, we had a foundation, we had released our first version, and we were ready to go. Our initial board is made up of appointees, obviously, because without a foundation, you have to appoint people. But the group of people that Igor pulled together were technologists, were people that had been in the Red Hat ecosystem for a while, were people that were experts on open source because those people together made sure that what we set up was going to be stable and what we needed for long-term growth. We pulled our sub-initial sponsors, those were the ones we launched with, and very shortly we added ARM and High Velocity and Equinix. They together gave us the hardware or the funds, the people that we needed to get an operating system off the ground. Since then, we have added another 25 sponsors, this is what it looks like today. And all of the people up here, all of the companies up here, are invested in the future of AMA Linux for one reason or another. This is what our adoption rate looks like. This is current as of three days ago, I think. We were just talking about how in July of this year, I had made a slide that looks similar to this that had 600 or 500,000 as the number of servers that we're calling home to our mirror system every night. And since July, we've added 200,000 more. So obviously, we are filling in need. This data is pulled from our mirror system. So in early 2022, or late 2021 technically, we added count me data. Essentially, when a server calls home once a week to update its DNF database, it says, hi, I'm online. That is an optional flag, so it doesn't happen every time. It is a, or it doesn't happen with every server. And if a company or organization has their own mirror, we don't see those. So these are just the servers that we know of that are online. Obviously massive growth. There's been some exciting moments in there. In the last two and a half years, we have done a lot. This is a very brief look at what we've covered. The most interesting thing about this slide to me is that as we look at this list, everything here is done because someone in our community needed it. This isn't, we're not corporate driven because we're a community operating system. So this isn't a feature request from a customer that comes in and says, we need this thing. This is all somebody in our community wanted to add or wanted to see support for this thing. Number two, we'll get to you in a second. But before eight, nine and nine, three, we had gotten so good that our releases were within a day or two of Red Hat. As you look at this list, you will see that primarily what we're doing is solving the pain points that we had as users with CentOS. Release times, support, like architecture support, that kind of stuff. Make sure there's nothing I want to point out specifically. No, I think we're good. Lots of extremely cool stuff up there. So we took up the charge. We were offering an operating system as soon as we could from March of 2021 to June of 2023. We were a choice for people that were looking for a CentOS replacement all over the world. I'm going to go back here. No, not going to go back. We're just going to go forward. In June of 2021, I am certain most of you have seen this update. This was Mike McGrath from Red Hat announcing that they would no longer be releasing Red Hat sources, Red Hat Enterprise Linux sources to get.centos.org like they always had. This broke our build pipeline without question. We had been doing no longer worked, but that was true for everyone who was trying to rebuild Red Hat, right? The thing about this, when we saw this come out, what we knew immediately was that we had to take our time to make a stable, long-term, forward-looking decision. We took a couple of weeks to talk to all of the people in our community, all of the people that would be impacted by our decision to understand exactly what they needed from us. What they ultimately needed wasn't exactly Red Hat. What they needed was Red Hat compatible. So that gave us a bunch of freedom. Red Hat compatible, from our perspective, means that we are using CentOS Stream repositories as our upstream in 99% of the cases. I'll fudge the numbers a bit. Our lead architect is in the back. He's going to correct me. But nearly all cases, we're using CentOS Stream as our upstream. We are pulling in any patches that we can't get from CentOS Stream, from other sources that we consider legal or acceptable. We are 100% laser focused on making sure that there are no breaking changes from Red Hat to Omelonix, because what we heard time and again is if I have an application that works on Red Hat, I need it to work on Omelonix. That's the line. Obviously, maintaining, continuing to maintain the things that people have also countered on us for, which are stability, speed, and security. Everything that we've been able to do, we pull 99% of the code, like I said, from CentOS Stream, and that means that nearly all of the code is exactly what Red Hat has anyway. Less than 1% of the code differs, and nearly all of that is in the kernel. So you're not going to see drastic differences between us and what you get with Red Hat, and that's the point, right? We need enterprise Linux that's stable long-term for our users. We've also had the ability to add new stuff since June. We added another repository that has packages that are unique to Omelonix. We can get in a little bit into what they will be. The goal with the Synergy repo is not to duplicate anything that exists in Apple. If you are using the extra packages for enterprise Linux repo, you won't have any conflicts. We've committed to that. This is just additional packages that our users might want. We also added a testing repo, so as we can now release additional things ahead of time, we get them tested. I only listed three here. I think there are five or six different times that we have added patches ahead of Red Hat, and added and been able to release. Security patches, those first two especially, are critical for the users that are picking up Omelonix, and those two we released almost a week ahead of Red Hat. The reasons are very practical on the Red Hat side, why they move slower than we do, but we were able to build and test and get them out the door ahead of time. Even just Monday, there was a kernel patch that we put out that was requested by somebody in our community that it currently sounds like that patch won't land until 8.10, but it causes instability. It is a bug that causes instability for people who are using large amounts of memory, and we wanted to be able to release that ahead of time, so we did. That's the kind of stuff that we get to do. I think, yeah, I'm going to hand it back to Suzuki-san. You're so quick. Thank you very much. Thank you very much for the insight, for the overview of the Omelonix, history and ongoing achievement. Let's look at commitment to stability and security in the post-SATO SL. This is a big topic in Japan, actually. We will show how Omelonix keeps the next strengths, as well as, you know, these stability and the security, this part. Omelonix breaching stability and security in business. Well, I believe that Omelonix is all about integrity. This is a point, I think. We aim to be generous and easy to understand OS, which is compatible with our Red Hat, actually. We know some are concerned about switching from the center OS. Our objective is to give Japanese businesses a Linux option to trust us, to use easily. We follow a Red Hat policy and some rules closely. Focusing on, of course, corporate needs. That's the point. Crowdlinux and Cybertrust has over 10 years' experience, as, how do you say, commercial Linux distribution. Well, our approach might be different, but we shared commitment. You know, we shared, again, we shared the commitment to long-term supply and sticking to the regulation. That's different to the other distribution. We focus on this. We are really, you know, important to the integrity wise, actually. Again, nowadays OSS is part of nearly every business system. The big questions for the future, you know, how to use OSS software in safety. I think every audience thinks about this. The big question for the future, yeah. And, you know, this is the answer. We are here to provide a clear and secure choice for our Linux. Please believe us. And this is the final part. I will announce that we have the first official event. Our Linux Tokyo Day Tokyo 2023. It's happening on the December 9th at its close. Actually this weekend, Saturday. Well, you can register from the official our Linux blog site. Please register from that. Okay. We can focus on the future. Venison, she is, of course, you know, already, she's the chairman of our Linux OS Foundation. And also, Egosound, Ego Zelensky. You're not here. She is, how do you say, the Cloud Linux CEO, as well as founder of the Linux. They will share insight into the latest Linux trend and also shared some idea how to survive post-Android error. This is the point. So, please join us. And I'm looking forward to seeing you there. And then talk with you and drink some with you. I am really waiting for you, ladies and gentlemen. Oh, thank you very much. And we have still have 10 minutes. All right. Q&A. Do you have any questions, please? We have, yeah, every question. And I'm going to stay Tokyo. Oh, the boost. Oh, if you have a question, please hang up. Let the hand over. Please. So Project Elevate. Did it just turn off again? No. Okay. Okay. So Project Elevate allows you to upgrade from CentOS 7 to Almalinix 8 in place. So if you have, again, we're solving the pain points that we as CentOS users had, right? So you can upgrade in place between major versions. And I know that that application, that upgrade project, has been used a ton. So my favorite example is an Internet provider in the U.S. that used it to upgrade 50,000 servers. So I know for sure it works. There are certainly caveats and there are hurdles. But we have an amazing community that will provide support for it, too. Okay. You mean U.S. have experience is from CentOS 7 upgrade to Almalinix is 1500,000? 50. 50. Oh, okay. Yeah. Yeah. And it's more than that. If you get to 8 and you need to upgrade again, you can upgrade in place from 8 to 9. And because we are so community focused, if you want to go from 7 to 8, we support going from CentOS 7 to Almalinix 8 or Rocky 8 or Oracle 8 or wherever you want to go. Because we care about keeping things open and collaborative. Yeah. Okay. Thank you. Yeah. We have the kind of expression seminar in the Almalinix Day Tokyo this December, this weekend. So maybe if you are interested in that, you can please join Almalinix Day Tokyo. It's free. It's not commercial, but our partner has a solution to migrate from CentOS 7 to whatever, that's 8 or 9 things. There is some solution. So they explain the solution about this. If you are interested in that, please join us. Thank you. Matt? No? Ah, Kurosawa-san? Do you have any questions? Of course. Sure. So our relationship with Red Hat is good. We are, if you think about it, we don't exist without them, right? So we continue to work with them as we can and as they allow. We are doing as they've asked with the change to using CentOS Stream as our upstream and pulling sources from places that they allow. Made the difficult but important choice to not violate their user agreements in how we get our code. And that, I mean, that goes a long way to building a better relationship, right? Yeah. And on a personal level, we know these people and have for years. So we're still friends. Yeah, including Egor. It's difficult, isn't it? Personally, we have a relationship with Red Hat people. You know, with Benji-san and Egor-san. And I already explained that. We don't, you know, we just want to, you know, I want to Red Hat policy and their rule. I want to protect their rule and the policy. You know, this is a regulation thing. So we don't, you know, fight each other. We want to do each other. It's at that point. This is a difference for them. You know, I don't see the other distribution things, but it's a point. Oh, okay. Mr. Takadori-san. I have to add the comment about that. As far as, I'm Saibatras Ospo, a leading person. And as far as I read the comment on Reddit, as MacGrath, the guy, Red Hat person, wrote the blog, the Red Hat blog. He wrote about the Armory Lacks is doing the, using the center stream as the upstream, as the Red Hat said. So, at least as far as I read the comment on Reddit, the MacGrath wrote, he looks, it's good. Because the Armory Lacks is following what Red Hat said. So, as far as at that point, Armory Lacks is following what Red Hat said and keeping the good relation with Red Hat. So, because of that, as a position, I said, this is good relation to join to this project. So, I think because of that, our company joined to the Armory Lacks. Thank you. The big point is, center stream is, center is the 80s, and next May, right? This is a point, I think. I don't know, computers, right? Even if you're just a user, I want you to be there because you care, you don't have to be committing code in order to provide value to the Armory Lacks community. Does that answer your question? Yes, thanks a lot. Yes, no problem. Thank you for asking. We have three more minutes. No, I will cut it off and we'll say, if you have more questions, you can't talk to us here. You have to come on Saturday. I think we're good. Yeah, thank you all for coming. Thank you.