 All right, thank you very much for joining us today. My name is Yuji Yazawa from Toyota Motor Corporation, as well as Vice Chair of the Soda Governing Board and Chair of the Soda and User Advisory Committee. Today I will facilitate this session and talk to you about overview and mission of Soda Foundation. After that, Kei Kusunoki from Entity Communication will talk to you about the projects. Yuzou from China Unicorn will talk to you about YIG projects. Then Vivian Su from Intel will talk to you about outreach committee. Each person will speak for about 10 minutes for a total of 40 minutes, with five minutes left to QA. Okay. In 2016, Dell EMC, Fujitsu, Hitachi, Huawei, Intel, and Vodafone funded OpenSDS. We got increasing requests during discussing OpenSDS and many companies including Toyota joined to OpenSDS. With the majority support of OpenSDS members, we are transforming the project into Soda Foundation. Soda Foundation is a home for OpenSource dealer and storage projects. As you can see, many major companies joined to Soda Foundation. The Soda Foundation provides an open, collaborative and newer home for project stakeholders to coordinate the development and community investments in the Soda ecosystem. The mission of Soda is to foster an ecosystem of OpenSource dealer management and storage software for dealer autonomy. To offer a new forum for cross-projects collaboration and integration to provide and use as quality end-to-end solutions. Today, there are many challenges such as dealer silos, non-standard interfaces, support solutions, and something like that because our environment is being too more complexity. I actually used to work for Yahoo! Japan Corporation as a principal storage architect. There were hundreds of storage systems and several petabytes of storage devices there, managed mainly by me. In fact, we were operating with only three people, including me. As shown on this slide, we had no choice but to avoid increasing the number of storage types as mixing different models and necessarily makes management more complicated. That's why even if there was a product we were technically interested in, we couldn't easily introduce it. This is a very sad story of missed opportunities to gain experience as an engineer. Anyway, it can be said that the configuration described in the slide not only lead to complicated administration, increased operational costs, and locking, but it also take away the opportunity to even take new initiatives. Soda is a single-dealer framework connecting different solutions into seamless end-to-end solutions. This framework is open source, allowing any developer, vendor, or end user to build and expand upon it. If we had Soda when I was at Yahoo! Japan Corporation, even there were only three operational members, the operational load would not be too high and we would be able to take on new challenges. Soda is an open source, unified autonomous framework for dealer mobility from edge to core to cloud. The key highlights is open source, standardization, ecosystem, and certification. Soda Foundation is overseen by the governing board and supported by the Technical Stealing Committee and User Advisory Committee and Outreach Committee. Technical Stealing Committee lead two-link projects and oversees collaboration with AppStream. And User Advisory Committee is a forum for end-user companies to discuss and exchange information on use cases and requirements and to provide feedback on Soda testing. Outreach Committee oversees evangelizations, communications, outreach, events, and training. From now, Kei Kusunoki from NTD Communication will take over and talk about the projects. Kusunoki-san, please start your session. Can you hear me? Okay, so hi, this is Kei Kusunoki. So I'm chair of the Technical Stealing Committee, working on NTD Communication. And today I'd like to introduce the project to any Soda. So we were formally organized this. As we had changed to Soda, we organized all development activities. And we shared the project list. We made the three-project category. The first is core project that is mainly open-sidious development activities. Four-project deal with fundamental center part of data-alternate autonomy architecture, like we'll... Okay, sorry, the first is core project. And the core project deal with fundamental center part of data-alternate architecture, like most soundsbound API, programming, storage infrastructure management, et cetera. It is initiated by formally open-sidious community and now governed by Soda community. Of course, every Soda release will contain new core project features over improvement. Next is native project. This category is for donated projects that was developed by SADA party or Soda member. Soda welcome new storage project to open data autonomy ecosystem. We support this native project to work with corporate, but the original organization can govern the project independently. They can choose whether their software version is pushed to Soda release. For example, next, for example, G release. And we are now S release. So now let me talk about example. For example, G release has new future from native project, but the next HD release doesn't have anything. It is optional for Soda release. And the sub is eco project. As you know, there are so many open source projects that are deal with Soda stretch data directory in directory. So to achieve open data ecosystem, it is significantly important that these open source software can use Soda work with Soda. So we make eco project category for such open source project to show that we are trying to build Soda ecosystem together. Of course, eco project is managed, governed by other open source community, don't follow Soda release. But Soda community will support specific use case or integration or something like that. So this is a landscape of our project. Top line is eco project. Currently we are working on two projects, Open EPS and Kubeh edge. And the middle line is native project. YIG became Soda native project to donate in their code to Soda. It will be introduced later by Zouyu. Additionally, Lin Store and Zenco have discussed to the joint. Finally, bottom line is core project. We have API, controller, match crowd, probably dog, dashboard, it's a step forward. Let me explain core project, seeing Soda architecture overview. So this is a Soda architecture overview. In Soda architecture, core project is located at the center. It's a kind of hub from Northbound, Kubernetes, OpenStack, VMware platform or any other application can use Soda through API. The programming and to Southbound, Soda will orchestrate traditional storage LA and software defined storage. And in terms of East Westbound, Soda form data lifecycle management through match crowd, like AWS, Azure, Google, and so on. Next. So here is a list of essential core projects. And so yeah, of course, we have more dashboard of infrastructure management or something like that. So this is detailed diagram about architecture I wanted to explain it, but unfortunately I don't have enough time today. So advanced session about core project and architecture will be provided in Soda mini summit, right, second, I appreciate it if you could join it. Lastly, I'd like to talk more about native project. As I said, YIG is only native project and we are discussing with Denko and Linstor. While we have kept trying to make new friends, we are working to crystallize Soda Incubator program. So this program has governance policy for each project. It covers the proposal process, growing process, review process and the accept time for each test. Besides this program, we also considering complete benefit and the support from Soda Foundation. So by these program, we hope to continue expanding Soda ecosystem presentation. So final part is, yeah, actually it's kind of hand over to Yuzo. So this is YIG project. So detailed presentation is next talk. So yeah, thank you so much for the missing. So Yuzo, are you okay to the presentation? We will introduce our YIG project. And I will introduce YIG from two pounds. The first is, the first, I will introduce the architecture YIG on some basis. In the early stage, we use the staff of Riddles Gateway as our obligated story stories. But along with our business girls, we need some problems. For example, if there are too many cells in the bucket, it will take longer time to return to list objects in the bucket. This will slow down the request of the user. And also in a larger self-clutter, if we do some intention of the server, the recovery and the backfilling will introduce some proper cross-system performance and it will slow down the user request also. Because Riddles Gateway can't share the cache, it will be difficult to use the simple cache in the Riddles Gateway. So at that time, we tried to find some solutions to all these problems. But unfortunately, we didn't get a solution in the Riddles Gateway. So we decided to develop a project that is YIG. In YIG project, we make better pooling performance for metadata because all the metadata are saved in YIG and managed by YIG. And some other other library functions, such as log static capacity and user authentication are moved to other systems. And also many YIGs instantly can share the same simple cache and also this improved the cache performance. And this is the architecture of the YIG. YIG can manage multiple self-clutters. So the self-clutter in YIG the self-clutter in YIG just provides the basic IOS storage and all the metadata are used in YIG and management managed by YIG. In the bottom, they are self-clutters and they are managed by YIG cluster and all the metadata are saved in TIDB company. We use TIDB for our metadata management. But you can use your favorite data-based data more because YIG has abstracted the interfaces for the metadata management. And also for authentication, you can write your authentication, apply it in the YIG and it will serve your authentication purpose. And for YIG metadata, currently we save the metadata into TIDB and because TIDB is built in the database system and compared with the Metcicle, there is no low number limitation in a single table and it is very easy to perform with Pension. So the list object in YIG will take a short time than that in Riddles Gateway and by using this kind of method without the problem we meet in the Riddles Gateway and for file processing, YIG will classify two kinds of files according to their size. YIG will handle the small file and this kind of small file can be saved in whole in set cluster with replication enabled and another kind of file is the large file. The large file can be saved in set pool and it is easy enabled. Because it is easy, we can save the storage space and that's all from YIG project and welcome to use it and try it. Okay, I'll start. Here's Vivian, I'm based in Shanghai and this is early morning. Okay, so session and currently I'm working for the in-care storage domain. And today, there's some delay to switch the pages. Okay, so hope you can see it. Okay, so yeah, today I will talk about the solar global community including what is solar foundation and solar governance and also how the global outreach community. And so our major focus today for this session is more about the outreach committee. We will also look back key events happened organized by outreach committee and happening in the last one year. So as introduced at the beginning by Yuji that solar foundation is a solar foundation that aims to foster an ecosystem of open source data and the storage software for this autonomy. And you can see that there are many customers, many companies joined at the foundation of the solar and the including China Unicom, Fujisu, Toyota, Huawei, and many other companies here. I will not just go through them one by one. And so if you look at organization on the solar foundation, you can find that. So we have four, there are three major committees here, committees here to support it including the technical steering committee on the bottom left to block and use advisory committee other EU AC on the middle block and the outreach committee showed on the bottom right to block. So what's the major goal of the outreach committee? Outreach committee is responsible for the event they've been keeps as a continuous communication for the committee health events and provide training to stress the solar community. And in different chairs, we have according outreach committee and they're also, you know, they are the country we have five outreach committees located in North America, Japan, China, India, and the Europe. In the past 2019, solar committee hosted multiple events along with global open source events. So we have the last year, we have the Kubokon Barcelona in Europe. At that time, we have the mini summit of solar in early May. Kubokon China in Shanghai in November, cloud native days in Tokyo and open source event in India. All of the events, you can see the solar meetup or mini summit or according talks. So you can just replay their videos showed up in the, you know, in the video. And then in December, in Tokyo, we hosted the solar formation meetings at Sony, Tokyo headquarters, more than 25 organizations, participants in the solar formation meeting. In December, along with China, Unicorn World Cloud Summit, so the China committee was launched. There's a bit of delay truth just to change the presentation. Hope you, we are on the same page. Yeah, currently I just moved to the solar formation pages. Okay, so in Europe, since year 2017 for the first solar member meeting, every year we have according events or meetings to have a call speech or to do the demo or project Jeff to join the solar foundation. And just the updates by the, by you, so you can find that either projects is also donated and they're joined into the solar foundation. And so let's go back to the US. There's also so many technical forum and the events or a conference happened there, right? So that's why, you know, in each second though for a conference, we also have according speech there to promote the solar. And also, you know, such kind of communication and the events will continue to happen in this year. So, but unfortunately due to their outbreak or coronavirus for year 2019, all offline events has been canceled or be postponed or just the changes to the virtual events to us. So, but to move into the Q3, we are a Q3 and Q4 of this year. We have planned multiple events and the work on all your guys can participate. In Q3, SOTA mini summit in North America and we also plan the solar days at Microsoft in August in India. In September, global intensive, there's so many, you know, intensive events happens there, I include in the co-operative. They see in Tokyo, so their former forum are always Kubernetes. So the forum Japan and the SIGNA SCC in Senkara. So all of that kind of events will also have according in power sessions for solar. In Q4, you will see that SOTA forum in India open for infrastructure submit in Berlin, SIGNA SCC in India and OSS in Dublin. In November on Kubekaw Boston, you will see SOTA forum there. So moving to the December, then it's foundation member forum in Tokyo. You also can just see SOTA and also can have the conversation with the team members from the SOTA. So whatever we should say to you are located in, you can participate according SOTA events and also we wish we can see you there. So this is all for the update for the outreach committer in the past one year. And also, you know, moving to this year, we hope we can have more, you know, events and can talk with you offline or maybe just virtual and also working new join into the SOTA foundation. So that's all for update from me and thanks for your time. And then we will move to the Q&A session. And oh, by the way, thanks all our previous speakers from UJI, K-EASL, and now we hope co-develop the code that you present for both sessions. And this is topic for a new home for data and storage collaboration. I'm moving forward, let's go to the Q&A session. So welcome to raise up any questions and also, you know you can just raise up question to the specific speakers or just ask questions to ask all the guys, thanks. So is there any question about our session? All these, it seems to be nothing. All right. So thank you so much for attending our session. Thank you. Thank you.