In this demo, you will learn how to migrate multiple virtual machines from vmware's vsphere to Google Cloud platform leveraging migration waves. If you're planning a large migration, it is a good idea to divide the work into large chunks called Sprints. A Sprint should contain all of the virtual machines running one of your applications migrate for compute engine subdivides a migration Sprint into one or more waves, which group the virtual machines that run your applications in two batches for migration. The current environment which we will be migrating from is VMware vsphere and currently runs on premise. We will be migrating two Virtual Machines in two different waves. But when you're doing a large production migration, you will typically have multiple virtual machines in multiple waves. In this case, we will be migrating a Windows Virtual Machine win Wave 1 and a Linux virtual machine Linux demo VM to to begin. Let's go to the my great for compute engine manager. Once there, we are going to select migration weights. Next, we will generate a run book based off of the Virtual Machines that we are currently running in our vsphere environment. To do so, we will select the source which is vsphere, select the data center, which is a vsphere concept, select our Target Cloud extension, which is what is running in Google Cloud to handle the storage for our Virtual Machines as well as the streaming storage from on-premise to Google Cloud. And then we will select the populate with Cloud extensions default once done click Create. You will notice that a run book will be generated and downloaded to your local machine within your downloads folder. Next, you will want to open the Run book with your favorite CSV. Editor once open you will receive a list of the Virtual Machines running within your vcenter environment in our scenario. We only want to migrate to Virtual Machines. So we will delete the rows with the Virtual Machines, which we do not wish to migrate. As you can see the two that we've selected our win wave 1 and Linux demo VM to now in order to make this into a wave migration. We have to define which run group these Virtual Machines will be processed. Then you can have multiple run groups and multiple Virtual Machines can share the same run group in our scenario. We only have two Virtual Machines. So I will provide one group one for win wave one and run group to for Linux demo VM2. The second part of this file that we must complete deals with the size of the VM also known as the target instance type. Now, we can automatically enter the target instance type directly here. For example an N1 standard one or we can ask my great for compute engine to provide suggestions in this scenario. Let's have migrated for compute engine provide suggestions given that we will save the Run book and close it. Next let's go ahead and create a new wave. We will want to give the wave a name. We will call it test wave migration and then choose your runbook and click save. Our next step is to select the wave then click action and choose right-sizing. There are two options. You can choose for right-sizing. The first is for my great for compute engine to recommend a virtual machine size based on the instance type, which you are currently running on premise. The other option is to start monitoring and overtime. My great for compute engine will learn the right size value for that virtual machine. Whereas maybe you need more or less resources than you I currently have allocated in our scenario. We will get recommendations based on the current instance type and how that would map within Google Cloud once done click. OK you will notice that a new run book has been generated open this ROM book with your favorite CSV editor and let's take a look as you scroll through it. You will notice that several instant sizes are recommended. Custom 2, 4, 0, 9, 6, a custom 2, 5, 1, 2, 0 and accustomed 2, 6, 1, 4, 4. This is my great for compute engine suggesting Virtual Machines sizes based on our Virtual Machines that we currently are running on premise in this scenario. I will take the custom to 2, 4, 9, 0 6, you'll want to copy that into your clipboard and then paste that under the target instance type and I will do that for both Virtual Machines. Once done, you want to save our run book and close now that we've updated the Run book with new instance types for our Virtual Machines, which will be migrating into Google Cloud. You need to remember that we have to actually update the Run book for this specific wave. If you recall when we started we generated a run book created a wave added that run book, but when we decided to go and get recommendations, it created a second run book. This current wave is still pointing to the previous run book which does not have our new instance sizes in it. So to do this, we will click on action click on update run book select choose file and select your updated run book. We will then click save once done. We now need to validate that the format of the rum book is correct to do so select your migration wave click action and select validate and click. Yes, it is now in a validating State this can take up to one minute to reflect in the web user interface. But if you would like it to update sooner, you can click reload on the browser. And as you can see the Run book has passed the validation now that are run book has passed validation. Let's go ahead and create a migration job to do so select your wave and click action, then select new job. We will want to select a full migration once done click. Start you can then see under the last job status that the full migration is running to get further details. You can click on the monitor icon. If you look closely you will notice that there are two run groups. Just like we specified in our run book again in a production migration. You will have multiple run groups in multiple applications are virtual machines running within each run group, but for the sake of Simplicity, we are doing two virtual machines one per run group for this demo. As you can see under migration status, you'll notice that when wave one our Windows Virtual Machine is already moving to the Target cloud in is at 15% complete but our Linux demo VM has not moved at all. The reason for this is because our Windows machine is in run Group 1 and our Linux machine is in run group to try to find the analogy between what we're doing in this demo and your real-world environment. Imagine the Windows Virtual Machine. Xin is an active directory server and the Linux VM is a standard web server that may connect to active directory in this scenario. We would definitely want to make sure that our active directory infrastructure is fully migrated before we bring additional virtual machines into the environment that rely on that dependency. As you can see our win wave one Windows Virtual Machine is currently in a migration status of preparing to detach our second run Group, which is Linux demo VM 2 is currently in the process of migrating as you can see both Linux demo vm2. And when wave one are almost fully prepared to be detached you can now see that both virtual machines are in a ready to detach State our next step is to click on waves. Select our test wave migration click on action and select a new job. This new job will be the detached job select attach and click Start you will notice that detach is now running for further details. You can click the monitor icon. If you look under the migration status column, you will see that when wave one is already detaching which is in run Group 1 and Linux demo VM 2 which is in run group 2 is waiting to detach now, you can see that Linux demo VM 2 which is in run group 2 is starting to detach now the both virtual machines in each run book are in a detached State. Let's move forward with the cleanup process to do so. Click waves next select your migration wave and click action click new job and then select clean up and click Start. You will see the last job status as cleanup running. If you would like further details click on the monitor icon, as you can see the cleanup function worked perfectly and both virtual machines in both run groups are now showing as cleaned up to Find that the migration was successful. Let's go to our Google Cloud platform console. Next we will search for the virtual machine names Linux demo vm2. Or when wave one. And as you can see, when wave one are Windows Virtual Machine and Linux demo VM to our Linux virtual machine both which were running on our on-premises VMware vsphere environment are now fully and successfully migrated despite being in two different run groups. This demo should show you the power of my great for compute engine and the ability to do large Enterprise migration.
