 So now time to start. So hello everyone. I'm Yoshihiko Kobayashi from CIP and I'm working for Toshiba also and Today I direct the meta presentations about our project which called Chibi Infrastructure platform The title is how to make smart cities based mark with open source project. So First of all things change a lot around yourself. Now many systems connected to the internet. Not just all connected cars but also industries and smart cities. Which means everything around yourself will be connected together to optimize the world. So do you know what the civil infrastructure is? Anyone? Alright. There are many kinds of hidden industrial IoT systems around the world. For example, transportation. Yeah. Every time, every day maybe some of you are using trains which controlled by operating systems. And now we are using Venus to control train systems and energy. Can you imagine? The turbine, big turbine controlled by Venus. So it means electricity comes from energy power plant runs on Linux. And other stuff also runs on Linux. For example, building automations and broadcasting. And also almost yourself using smart phone and smart phone relying on telephone network. So that kind of network also runs by Linux and industry stocks. So these kind of things are difficult to see but all runs for your life. So which means civil infrastructure systems. And if we focus on smart cities we consider the quality of the services. To provide smart cars, each car able to run by themselves. And the controlling systems also provides their services by the best way for the basis. But for industrial IoT systems, something like a power plant, we should consider about the quality of services. Because if power distribution stops, which makes huge issues for our life. So industrial IoT systems need to run 24 hours every day and cannot stop. And also ensure the quality of services. So this is a kind of smart city. This is very old power distribution systems. But inside this kind of systems, also we are using software based on Linux. But there are many issues to ensure the quality for a long time. Once we created power plant and created some software for power plant. We have to consider how many years to run this kind of systems. And for example power plant runs for more than 30 years. This is just normal. This is a quite difference between smart phone and power plant. And now we have to consider about security. Usually the power plant doesn't connect to the internet directly. But to optimize our life, we should consider to run these kind of systems with network. For example, if the power plant able to optimize by power consumption every home or every town and every everyone. So that means everyone able to provide the data to optimize the power plant. So in that case, we have to consider about security for million devices. So there are three main key challenges to ensure the civil infrastructure systems are stable enough. The first one is industrial grade. To ensure the industrial grade, we have to enhance the reliability for open source software. And the next one is sustainability. Once we created the product, we should use this kind of system more than 10 years or sometimes 30 years. So we have to consider about the long term stability. And the last one is of course security. We should consider about fix the security issues over time during the product lifetime. But to solve this kind of key challenges, we also consider about the complexity of the software. About 20 years ago, when we created the products, small products for infrastructure, we just created everything by ourselves. But now seems change to use open source software to create this kind of product. And now we also consider about the connectivity to connect the internet or to optimize our life. Which makes quite complicated software systems underneath of our applications. So to create our civil infrastructure systems products, we are using Linux. But many companies also using Linux. But they also have same issues. So as you can see here, there are many kind of penguins. So if we create the different penguins every time, this makes quite difficult to maintain all penguins at the same time. In software world, there are no common solutions for base systems. So this is why we created civil infrastructure system platform project. And CIP aims to establish the open source base layer for industrial systems. So this is the first time to say open source base layer. But I'd like to explain what the open source base layer is. Open source base layer is located under the Linux distributions. This is kind of very, very fundamental systems for every product. So that includes Linux kernel, of course, and the set of important packages. For example, C language library. I think many are everywhere using this kind of libraries. So we should consider what kind of libraries or what kind of utilities are commonly used for industrial systems. That is categorized to CIP core packages. And both CIP kernel and CIP core packages, we called base layer. And on top of the base layer, there are many packages able to use with CIP base layer to create our applications. So this is how we use our open source base layer inside the company. So CIP will provide the CIP base layer. And on top of that, we can use many kinds of open source software packages based on your requirement. So this is a kind of middle line, this part. And on top of that, this is very, very important for business units. This is the value for the product. So this shape is how we use open source base layer with other open source projects. And based on our experience, we can reduce about 70% of our effort to create our product based on our CIP base layer. Because CIP focus to maintain this base layer. And this is a very fundamental part. And many, many people join to maintain this effort that's able to reduce the cost for development. So CIP is open source project. There are member companies there. And now we have eight member companies to create our open source base layer. And as you can see, Xemence and Toshiba, these kind of companies are creating many kinds of CIP infrastructure systems. And SOC vendor is Ronessus. So they're providing industrial grade SOCs. So these kind of companies are currently joining the CIP as a member. And we have some budget because we paid some membership fee. And that's budget we usually use to hire some developers and also to fund our important projects. So this is a technical map. So we have to do many kind of stuff, not just a maintenance. Because we still consider how current open source is not enough to directly use for our product. So there are many enhancements will be done by CIP. For example, real-time support is good example. Real-time support is we are using real-time patch. But Linux kernel real-time patch set is not upstream yet. Which means when we use Linux kernel with real-time patch set, we have to maintain both kernel trees, which makes twice as cost or more. So we contribute to real-time Linux project. So this is the kind of how we are working with that. And as you can, as you see, we currently have only eight members. So we have to prioritize our technical issues. And our first target was super long-term support kernel. Then increase our focus to build our open source base layer. And this right shows CIP's governance. So we have a normal open source project, which have a governing board. The governing board decides the project direction. But under the governing board, we have technical steering committee. The technical steering committee is very important committee. Because inside the TSC, we discuss a lot how we focus and what kind of topic will be focused in CIP project. And currently, we have six projects inside the CIP. And the first one is super long-term support kernel. And then increase the project. And the latest one is software update working. So I'd like to explain how we work together with open source project. To ensure the CIP base layer. So this right shows how we work with open source project. Because CIP is open source project, but we don't reinvent or avoid from scratch. There are many open source projects doing similar stuff or doing important stuff for CIP. If we find that kind of project, we work together. So we have strict rule. The rule is upstream first. This is quite opposite considerations in between maintain and upstream first. But upstream first is very, very important policy for CIP. If we want to maintain something, we have to include the fix to upstream. This is the upstream first policy for CIP doing. And once our fix or our important device drivers or our important key features are included in upstream, then we start to backport to CIP kernel. So if we fragmented with open source upstream project and CIP, it also causes serious issues to maintain the CIP kernel or other layers. And other than the kernel layer, we are also using many kinds of open source projects. And the most important one is Debian because Debian is a kind of CIP difference distribution. And for testing, we contribute to the Lava and kernel CEI and the other open source project as well. So to ensure our project, this circle is very important. And this is what CIP is doing now. So this is actually a development structure for the CIP SELTS kernel. So first we upstream our required features and also bug fix to mainline and also stable queries. So we are just doing as normal. For example, if you try to find CIP project inside the Linux stable mailing list, you cannot find it. But our maintainer actually helping their reviews for Linux stable queries. And once the LTS kernel is available, we merge the fixes to our CIP kernel. And CIP kernel have some device driver enhancement and also some future enhancement. Because during our support period, sometimes we would like to have some security enhancement to make our systems more secure. So this kind of very small and very important features only able to backport to our CIP kernel. And currently we have two CIP kernels and the first one was released I think around three years ago. That was a 4.4 base kernel. And currently we maintain CIP kernel and the latest one is 4.19. So both kernel is maintained by CIP with stable kernel team. So the latest one just released yesterday and the version is that one. So this is a bit different because in real-time Linux patch is not upstream yet. So we first funded to real-time Linux project as a Gold member. And not just funding, we also joined their activities. For example, 4.4 is maintained by CIP members and based on that we created CIP-based RT kernel. So this is a kind of funding and development. And the next one is CIP testing. So at the beginning we consider we would like to test by ourselves. That means we created our own environment based on open source software using Lava and kernel CI. But after that we reconsider our testing effort to individual persons to distributed environments. And now we also using Lava and kernel CI but our testing environment is now located on AWS. And every day we test our CIP kernel. And the testing result is available on internet as well. So all testing effort is open. And fourth one is CIP Core. So CIP Core aims to provide the implementations which means the kind of difference distributions for CIP core users based on Debian. So we are using Debian source code and Debian binaries to create CIP open source base layer. The reason why we choose Debian is Debian is very friendly for embedded systems. And also there are some long term support project which is called Debian LTS. So if you are going to Debian LTS project you can find CIP logo on their website. Because we work together with Debian LTS project persons. And currently we have two profiles. One is a tiny profile which makes very very small footprint root file system for IoT sensors or something like small product. And the other one is generic profile which able to use IoT gateways. Now IoT gateways have more than 32 megabyte or 32 gigabyte something like that. That kind of storage and also memory on the machine. So which is able to use a generic profile. And the latest status of the CIP core is you can test CIP core based on... Now you can download from GitLab. And also we are using CIP core to test CIP kernel every day. So this is a status for that. So from now on things are a little bit changed. So we launch the security working group. As I said we are fixing security fixes. But the other point of view to create the secure product is also important. Which requires development process and also development document or something like that. Now there are quite important standards is available which called IEC 62443. Which is a generic cybersecurity standard. And that was published at February. So this is very new security standard. But many product developer want to apply this standard for our product. In that case every developer need to ensure to meet this standard. Which requires many testing effort and also many documentations. So we decide to create many test cases and also reference implementations to fit this standard. That means once we publish our result you can use directly to your product. Which makes more than 50% of cost reduction for development for this security standard. So the latest status is we just started the feasibility study. Because this is only published in last February. So now it's about 6 months now. But we already created some test cases around 40 test cases with document. So this kind of a document will be present open source in Japan in next month. And the last one is a software updating work group. So software updating is important because now many devices connected. Which means we have to manage that kind of devices. And also need to update to fix the critical issues for IoT. And currently we are focusing to use open source software in that effort. And we are using SW update for the updating systems. And we are using a hook bit to manage all devices. So this is also just started recently. But will be demonstrated in next month. So we currently are actively development for the demonstrations. So let me summarize my presentations. So a kernel maintenance is important of course. But to maintain the kernel we have to consider about upstream. So we currently are using upstream fast policy to maintain the Linux kernel more than 10 years. So 10 years is our minimum commitment. And we just should say 10 years or more. And we are doing the other activities to ensure the open source base layer for civil infrastructure systems. And this open source base layer will be able to use many kind of products. Not just a power plant, not just a train. I think this base layer will be used everything. So if you are interested in our products, please feel free contact me and please join us. And there are many information available here. And thank you very much to attend my presentations. Are there any questions? No? There are five minutes to go. All right. Okay, that's a good question. The question was, are there any membership free to join this project? So there are two membership level is available. And first one is platinum, which is 200,000 USD for a year. And silver membership is a bit different. The maximum is 20,000 USD, but depending on company size. For example, if your company is quite small, less than 50 members, which reduced to around 5,000 USD per year. So this is a membership free to join the CIT project. But yeah, please consider to join Linux Foundation. Because Linux Foundation membership fee is also required to join this project. Thank you. And any other questions? Anything welcome? All right. Thank you very much.