 I'm sorry, okay. Many thanks for joining our cloud migration presentations. And I'm DJ, I'm founder and managing director of Gconvoter. My background is, I founded my company as 11 years ago. I'll be first to founded my company. I was working for IBM and LG as a subject matter expert and principle of virtualization and high performance cluster. And our vision is to help the enterprise of the cloud service providers to make the cloud migration as simple and easy. And our Gconvoter cloud migration has OpenStack compatible software. And our company is one of the OpenStack corporate sponsors. Is there anybody who is first time to hear about the IaaS OpenStack? Yeah, perfect. Okay, everybody know well this OpenStack and the IaaS. And the physical to virtual migration has automated physical server to virtual migration without the reinstalling the application and operating system. And this for is P2C is today's topic. P2C or V2C or cloud to cloud migration has also the automated cloud migration technology without reinstalling the applications and operating system. Okay, let's look at this simple demo the physical to virtual migration. Actually this is very simple process to move your physical server to a virtual machine like VM here, the Hyper-V KVM. First tab is the copying, sorry. Copy, actually this process is like a copy and paste process. Second tab is paste and run the converting. You can up and running your new virtual machines because of their technology as a VM wear is one of the fastest growing company. Before the P2V migration technology, VM wear is growth radius much slower than the market expectations. Actually these guys are supporting the P2V migration technology they are providing actually they're company are helping the enterprise to a re-installation problem, they solve the re-installation problem when enterprise go to the virtualization. And the funny thing is that most of the enterprise or cloud service providers are focusing on the cloud services. And the funny thing is that a similar issue is still, there's a manual re-installation problem is still existing in the cloud migration. Do you know why? Because many people, some people thinking we still using the physical to virtual migration technology in order to move on-premises to the cloud, open stack cloud but that is not true. Actually the P2V vendors cannot support cloud migration, do you know why? Let's think about why cannot they support the physical to cloud migration. Actually this is the open stack architecture and open stack is cloud platform and where the open stack is cloud operating system even though there is no kernel, everything is runs like cloud operating system. It means that this high provides level is they are also one of the operating system they have the own the kernel. P2V migration technology support is high for vital level. However, when you look at this open stack cloud operating system, high for vital like VMware, the KVM, and Zen is one of the open stack component. It means the high for vital doesn't have any the operating system position. It means in order to open running the migrated to the new cloud instance to the open stack you have to meet the two conditions. First thing is you have to meet this high for vital migrated condition. Second thing is you have to follow the open stack cloud migrations registration process or a controlled process. Actually P2V migration tool I mean this process. The cloud migration cloud operating systems registration process because of that when you try to migrate your on-premises to the KVM is belong to the open stack you're migrating the cloud instances without working properly. Actually we solved this problem. We are now providing the on-premises to open stack cloud migration by a few clicks. Now you don't have to reinstall the operating system and application. Also you can move your virtual machines like VMware, the high for V to open stack. And or if you want to move your Azure public cloud instances to the open stack cloud you can do by a few clicks. You don't have to reinstall the application. And soon or later we are going to support open stack to public cloud Azure or AWS because most of the enterprise companies and government forecast is this by 2017 more than 50% enterprise is going to use the hybrid cloud. They may use, they may running the open stack as a private cloud and also they are running they are using the public cloud like this Azure, AWS, Google cloud platform. Because of that the cloud cloud technology should be supported. Yeah, this is the most supported leads actually we are companies supporting open stack and also Azure is going to support it November next month. And AWS, AWS also be supported and also KVM and VMA giant hypervisor to support it and also we are supporting the disk format like this. During the cloud migrations if your virtual machine is VMware the disk format is VMDK. If we want to converting this VMDK to QCOW 2 we are supporting the converting the disk format from the VHD to QCOW 2, the VMDK to QCOW 2. And also we are supporting the windows or Linux operating system. This is the conceptual automated cloud migration process. Very simple. First step is creating a new cloud instances to your open stack cloud. And the second thing is an imaging process. And third thing is replicating this women to the target open stack cloud. Final step is converting that's it. You don't have to re-install the application as the operating system in order to move your own primary stage to the cloud. And the better thing is during your running your source machine you can do this cloud migration. We are supporting live migrations like this woman. And this is use case. We are helping the public cloud migration for the Korea Telecom. Korea Telecom is the largest public cloud vendor in South Korea. And they announced the cloud migration services in February this year. And also one of the big company is going to move the 500 servers to the private open stack cloud. And actually this shows the starting project. If they succeeded this 500 server cloud migrations next year, they are going to move a few thousand server to the open stack private cloud. And another opportunity, the 700 servers is going to be migrated to the private open stack cloud. And also we are talking about the cloud migration technology with Google cloud platform team in Mountain View. Perhaps our cloud migration technology is going to be integrated with Google cloud platform. Perhaps only next year. Now this is the cloud migration software as a services model, very simple. If you wanted to migrate to your own premises to the open stack cloud, please access this www.gcloud.net. And first tab is login. And the second tab is the registry source machine. It's a very simple process just to download your agent file to your source machine. Then our cloud migration website will identify your source machine. And third tab, in our automatic lines and demo, first tab was creating the cloud instances. Actually you can create your new cloud instances from our website. You don't have to go to the open stack cloud. Adjust login from our website. You can start to creating your new cloud instances. Now first tab is the starting cloud migration. Now when you click this next button, you can start to imaging and replicating and converting process at the same time, but automatically. Now fifth tab is complete. This is the demo video, same process. This is the cloud migration demo. Left side is the source machine. We are going to move the source machine to the target open stack cloud. And the first tab is to register the source machine, the downloaded agent, and this is the information in your source machine. Identify our website and choose the driver you want to move to the open stack cloud and choose the repository and click next. Now this is the login process to your open stack cloud. After this login process, you can create your cloud instances from our website. The third step is creating the cloud instances. You can type the instance name, you can choose the flavor like one CPU, four gigabyte memory, blah, blah, blah. And to choose the operating system, you should have to choose the same operating system with the source machines. If you're running the Linux, you have to choose the Linux operating system. This is processing the creating the cloud instances. Our first step is registering the cloud instance and target created instances in order to move your source machine to the new cloud instances. Now we are starting the migration. Our first step is imaging. Our second step is replicating from the source machine's image to the target cloud instances. This converting step, this is the final step. When you're finishing this converting step, you can open running your new cloud instances. And actually if you want to move your virtual machine to the open stack cloud or physical machines to the open stack cloud, or the Azure, AWS cloud instances, the cloud open stack cloud, the process will be the same, no differences. Because we are using our own MEGN technology, we don't use the open source technology. Because our company has two original technology. First one is image technology, second one is migration technology. This is final step. This is the migrating the target server. We can compare the source machine and the target machine is same. Finishing? Okay. Okay. Any questions? Actually very simple. Our migration is copy and paste. You don't have to re-install the applications like a P2V migration. A network layer, that's a good question. Have you ever experienced it to do the physical to virtual migration? Actually, like network layers, before starting the cloud migrations, you have to consider in the network layer. When you're creating your target cloud instances. Actually, if the target server is providing the HTTP, you don't have to customize any network configurations. However, if you have the different IP structures, blah, blah, blah, in the case you have to design about this network before migrating. That's a good question. Okay, that's a good question. For the database, for the database, we are supporting the block-level replication. First time you're sending the full imaging file to the target. The second step is replicating the changes data. Actually changes block data from source machine to the target. You can dramatically reduce the services downtime. This process will be done when you're running your server. Very, yeah, last time, very last time. Very short, okay? During the replication, during migration, you don't have to shutting down your server, okay? Yeah, that is possible. Actually, your private cloud, if you download our agent, and if you allow the access from our migration software to your private network, you can migrate your private cloud instances to the Azure public cloud. You have to allow to access. If you are providing VPN, that will be much better, okay? Also, if you want to migrate in a private cloud environment, we are providing the migration software appliances. Okay, you don't have to access the public network, okay? You can do it in your private network, everything, okay? Yeah, that's right, that's right. Software appliances, okay? Okay, thank you. Now, if you have more questions or details, please visit our TS61. Our, what is located over there, okay? Yeah, thank you. Have a good lunch.