 OK, good afternoon. Thanks for coming. Xiaohao. My name is Eric Chen. I'm the CEO of Profit Store. They are services. And this session, we are talking about Profit Store Federator, which is a software defined storage platform for OpenStack. Exactly who is Falcon Store, we are actually a group of storage and service veterans that have been working together. The core team has been working together for more than 10 years. We have been working in mission critical storage systems. So we are very proud of that. We can bring in that type of enterprise-grade services to OpenStack. We are here to challenge the status quo of storage management in so a defined data center. And we are headquartered in Milpitas, California. And we have teams across Asia-Pacific regions. We actually emerged from a two-year stealth mode yesterday. So although we are brand new from our look, but we have been working on the product for more than two years. What is Profit Store Federator, the product that I'm going to introduce now? It is actually the first software defined storage for OpenStack. And it is a sophisticated storage management solution with a single panel gas for promoting the wider sectors of OpenStack. We understand storage is a very complicated issue in the data center, as well as in a public or private crowd. We are here to provide a simple solution for that. So before we came in, this is OpenStack, as you can see. And if you walk into a data center or into a crowd center, you can see many different kinds of storage, be it EMC, NetApp, Hitachi, Dell, or many other storage systems. They are all very good. Except you have very different storage systems, very different storage management. So each and every one of the vendor, they come up with a volume driver, trying to connect into OpenStack, and that results in a tangled wire. Not just the wiring, but also the management. You manage so many different kinds of storages. And I don't believe there's enough talent or other people to really effectively manage all of them. So this is chaos situations. OK, what we are trying to do is to provide a flexible, intelligent, and standardized faderator for managing all the storage systems for OpenStack. OK, so this is after. Still down here, you can see many different kinds of storage systems. Well, just name a few up here. But with our faderator, what we are trying to do is trying to come up with a single entrance into OpenStack. And through the faderator, we will be able to embrace all the storage systems here. In addition to that, we do have a way of making commodity hardware, which is x86 based, and putting our storage server software into that commodity hardware. We can turn that into a very intelligent storage. That will work negatively with our faderator. So with this in mind, then this become a well-defined storage systems for OpenStack. OK, this is where our logo came from. And the functions that provide those characteristics to faderator would include the following. Let's discover, pour, classify, offer, and provision. We first discover all the storage connected through network. We will be able to pour all of them together and even import the pours inside each individual storage systems. Then in addition to that, we provide a classification mechanism that classify those storage systems into different classes of services. And then we offer that. We create offering that match the need from the application. So it becomes kind of application aware. And then we provision that to OpenStack. And then to a compute that requires storages. So with this in mind, all of these functions will actually enable a very easy management of the OpenStack storage issues. So we create a single pane of glass for management. All right, so with Parfait Store Faderator, we actually would like to take back the control and that you to define the storage the way you want it. Then we provide no vendor login, no functionalities locked down, no system locked out, and provide equality and freedom, meaning that we manage these storages equally. And freedom from the vendor login by providing additional storage systems based on commodity hours. So we are well connected with each and every one of the components within OpenStack. So as you can see here from this picture, the Faderator has a volume driver into center. It actually utilize keystone for the security. We even provide a way of moving the image from to volume and volume back to image. So all of these are well connected and we are designed for OpenStack. Next, I want to talk about the demo. This is a demo environment we are providing today. On the upper left-hand side, that's OpenStack. That's running on one machine. On the upper right-hand side here, that shows two screens. One is for OpenStack. The other one is the console for managing the storages. That's our Faderator. I will be switching in between OpenStack console and the Faderator console. On the lower left-hand side, you can see the Faderator itself. It's running either as a VM or it's in store and under the Apprises. Underneath here, you can see one network apprises and the other one is a profit store storage server running our own software to showcase that we actually can manage diversified storages. So in terms of steps, we would like you to see the management following these flows. We will show you the OpenStack console first and then come back to manage the storage using the Faderator. And from there, we can see all those storage services. Then, coming back to OpenStack to show you that actually we can provide the storage services using the Faderator. By the way, the Faderator is the control path. It doesn't encompass the data path. So we have a separation of that. Okay, so there's a demo and Prisha can't take us at the info at profit store. All on the sound. I need the sound. Can you, there's no sound. Okay, good. So first, we wanna do the discover. As you can see here, we are using protocols for auto discovery. And three storage are discovered. And we look into each and every one of them. Okay, and then pull them together by pulling. So if we import the pools, that's already in that storage systems. And you can tag, label the pool that you just discover, put in all kinds of information you want, okay? And then we classify that. Depending on the characteristics of the storage we discover, for example, on the first one here, we can even provide a testing to us, okay? From the test, the result will show the IO per seconds and other informations about our storages. Okay, so this is IO per second. That's all of the second ones. Then we abstract, provide the information for the, provide offerings, meaning that what type of classes of storages we have here. We define those classes of storages. We have the specification for that and specify the IO per seconds. And the offerings can be created on demand. You can have predefined offerings or on demand creation of that. Then we provide that. Coming back to OpenStack, you can see that those three storages have been discovered. And then start to provide that to VMs. You can start allocate storages, okay? For example, now we wanna create a volume. This is all on OpenStack. In here, you can see that we wanna create a volume of all the type that has IO per second or 10K. And you also could see other specification of that. And one gigabyte of that has been created. Okay, yet another one. So you have two gigabytes of that type of storage. Now, coming back to Federator, we can check to see actually those two are created. We can double check that on the Federator site. Okay, so we now have two volumes. Next, we wanna allocate those storages and attach that to an instance. And device them, we can specify the device them there. So with this, those two drives, I mean, two volumes have been attached to one instance. And we can double check that through the instance console here. And of course, we can detach that. And then after the detachment, that's according to OpenStack, we can do snapshots. Okay, here, snapshot has been created and we can create volume from that snapshot. Okay, so all these are integrated. And in addition to that, we do provide add-on functions to OpenStack. For example, on this case here, we can even roll back the volumes. This is a very critical for data protections, especially for database. Once you make some mistakes, you wanna roll back your database to the previous state and then we can do that. So overall, this is what we can provide. And hold on, not done yet. Okay, in the USB that we have distributed, we have an introduction video and we do have one click installations software. So you can try that out. So now I wanna speed up the introduction. The storage is defined by hardware, but isn't it? Data keeps growing, requirements keep changing. And traditional storage design keeps it from the performance systems. There are more data silos, not as existing storage. They span with a defined storage on demand. Today, we believe we can. The ProfitStore theory, software defined storage, defined storage, just the way in which a single solution that offers quality, talent is hot damn, no system market, ProfitStore. Okay, and that's us and we are at both C18. So you're welcome to come by to talk with us to see a live demo. And if you have any questions, we are here to answer them. Thank you very much.