 Test, test. All right. Good morning, everyone. My name is Josh Chai from Infiniti Soft. We're the software company dedicated in hybrid cloud management. And our goal is to make hybrid cloud adoption easy and simple. Who is Infiniti Soft? We're actually specialized in a software field, and we came from Java background. We were doing the projects for most enterprises, so we understand most business needs for adopting cloud. The cloud today, what we see is not the same. All clouds are not created equal. So the cloud, including the pricing tag, characteristics, how you're using cloud, even the location are different. Also, clouds are complex. Which cloud you should be choosing? You should be choosing based on performance, or you should be choosing based on characteristics. But all the devices growing today from wearables, cell phones, even smart cars, all the smart devices make cloud even more complicated. Because most important thing is, you need to make a cloud close to the user as close as possible to make your service be more efficient to increase your quality of service with consumers. What we do with Infiniti Soft, we make hybrid cloud management centralized. Meaning, it doesn't matter if you're using one or two version of OpenStack, zone one or zone two, or you're using VMware and other hypervisor solutions. We make it centralized in a single interface. Also, we have a completed cloud ecosystem. We make resource management. We make analytics, as well as a deployment easy. And we allow your service to be able to deploy to any location in the world. This is how our solution looks like. The solution has three products included. First product is CloudFusion. And the other product is a log loop. Literally, it analyzed a log from different sources. And the last is Apple Loan. So let me first introduce CloudFusion. CloudFusion, so far, are connected more than 10 different cloud resources, including different hypervisors. Doesn't matter you use which public clouds or private clouds, we're already connected more than 10 most well-known cloud resource already connected. CloudFusion, also, is a one-step platform allows you to jump straight to three most important characteristics in cloud, including self-service, including measurement, as well as a organization resource reporting, and all the flows. How does CloudFusion relate to OpenStack? We're actually adding more features and benefits to the OpenStack community. We make OpenStack be more easy to manage, give more functions, including charge back and self-service. So you'll be able to connect, for example, adopt two versions of OpenStack, because you know OpenStack have a revision every six months. With CloudFusion, you'll be easily to manage a different revision of OpenStack, as well as a different branch from OpenStack. In my slide, it's actually for SUSE, OpenStack version. Very quick interface screenshot showing you the CloudFusion. However, I will take the next half, 10 minutes to go through the product demo. So just give you a quick snapshot about CloudFusion. On the left-hand side, you can see different features of business needs. Also three different hypervisors right here. The secret behind the CloudFusion is our open source project. We actually have Skyport public on the big bucket, as well as a Github. Skyport is an interface connecting to multiple clouds. It doesn't matter if you use multiple private from OpenStack version, different OpenStack versions, as well as a public cloud. Our open source project, Skyport, allows you to connect to multiple sources, make it easy to manage. And you can also add your own drivers, why not? A quick interface showing you the Skyport. The left-hand side showing you many virtual resources you may have from different public clouds, as well as private clouds. Another project from us is actually contributing to OpenStack community is called Keystone4j. Keystone is actually one of the elements of OpenStack, a managed authentication, because we all know OpenStack built on top of Python language. What we do is we came from Java background. We actually make this little program allowed user to adopt OpenStack Keystone module easily from Java. We use RESTful APIs to allow Java users to enjoy the functionality of authentication from Keystone. Second product I'm going to talk about is LogLoop. So literally, LogLoop collects log from different sources, including OpenStack, as well as a hardware resource, OS resource, system resource, as well. All the log is all the text form, so it's not easy to see why you can get from log. Log usually looks very complicated. What we do is we're first of all collecting log from different sources, do the indexing, so you get easy to do the query from us using Google language. We can use log to make a graphical interface so easily to use this information to do your revision, as well as to judge your virtual resource. Last but not least, Appalone. Appalone is a product. Actually, we all know automation. Automation use a lot of script. So we actually transform and convert script to the GUI interface so you can enjoy the automation by GUI easily to deploy your service. As well as Appalone gives more manageability for you to deploy applications to everywhere in the cloud. So I'm going to finish my presentation as a quick introduction. Next, I'm going to demonstrate our product. So this is our goal by simply a hyper cloud adoption. So what I'm going to do is let me just quickly log in the product to the live demo. So this is Cloud Fusion. So from the first dashboard, you're going to see easy to see two different open stack version. We give you a zone one and zone two, as well as you see our resource in Beijing from Aliyun, a different hyper cloud management functionality. We also manage VMware, as well as RGV from Red Hat and AWS. So most of the wanted feature for enterprise when they adopt open stack when it's a cloud is you need to set up organization. This is most of the wanted feature from when you adopt cloud. So in my case, I set up InfinitySoft as a company layer. Again, you can easily set up multiple companies if you're MSP. So in my case, I have Japan branch, China branch, and three branches, as well as one resource for partner. So under my branch office, I have a different BU functionality. I have three R&D group. I can limit them by the functionality and the rows they are actually working on. So in this case, RD1 actually for the front end. Going to the row, as a front end engineer, you can restrict them the resource they can use on the cloud. For example, a restrict front end resource of engineer can only use AWS as a testing purpose or for developing purpose. So this page actually demonstrate you can actually you see the cloud resource. Now you actually be able to allocate a resource to your specific department. This is very important for enterprise to adopt cloud. So now you already set up the organization. What you're going to see is you need to set up a breakdown resource by companies. Again, we use AWS. You can limit it to different individual companies. Or we go down to another level as organization. Again, that's a sign, open stack zone 1 to another specific organization you may have. So for example, I have maximum 23 CPU. I can give Japan branch for five. I can give memory as a 43 gig. I give four for Japan branch. So now they will be able to use a specific resource that you allocate to them. Again, we go down to another level. You can even assign resource to a specific user group. So this is a maximum resource you have as a cloud maximum capacity. When you do all this arrangement and allocation from resource management as well as you set up your organization, most important thing is you can see the instance. This is a multiple instance you see from zone 1, zone 2, from open stack, as well as from different regions. In my case, let's try open stack zone 1. From this reds and greens, what we already been done is we connect VNC to your virtual resource to different open stack version. We can also go inside to click to see the detail of instance. In this case, we can see the life or see the duration of instance status. Here's has another module here called payment. It's very easy to understand as all the resource should be measured. So one of the important things as infinity solve is we actually give a customer a measurement so they can do the charge back to different departments. Not only for virtual resource, you'll be able to see the status. If you go inside the hardware, this is a host of your cloud hardware, which is what we call host right here. Different IP address represent your hardware so that say we try the first hardware. Again, you'll be able to see the life status of your hardware. It's your hardware environment. It's time to upgrade or it's your hardware capable supporting all your virtualization platforms. Template is also very important because Cloud Fusion actually pulls back life from different cloud platform you may have. So let's go to do a charge back function. It'd be easy to understand what's charge back. We have pre-set up charge back programs here. So let me create another new charge back. We give a name, a name of new charge back module. And we actually can assign different CPU. In this case, template is very important because we choose currency that shows a template from pullback from the OpenStack group. So we pull back from OpenStack, easily pull back a template. So you apply the template to your charge back module. So now you're easily to apply different charge back function. For example, running for Ubuntu, I give a price of $4,000 yen. Why not? Also, I give a price of applications. So I can say we run Office. So those are the costs of IT people. Admin people should be able to manage your organization more efficiently. So in this case, you're done. You set up one price plan as a charge back. You can also list, sorry, you can also list all your software functions and a currency right here. Workflow, workflow easily to understand is we can manage day and line, manage different servers. Sometimes you need some of the job to be done at night so you can shut down some of the server at date, start up some servers at night. Again, we all manage the virtual resources. Reporting is the same. You can report by different duration of time to get back your management to see the real cloud utilization. Scheduler, again, managed all the VM. Scheduler work together with workflow because workflow allows you, once you set up a hierarchical infrastructure organization, we allow you to authorize and resource allocation. Management easily to deploy the management functionality. So we're glad to be here of OpenStack Tokyo. If you have any questions, please visit us at booth T57. It was our website and we're infinity soft. We make a hybrid cloud adoption easy and we release the true power of a hybrid cloud utilization. Thank you very much.