Cloud details. It's going to be AWS migration. The way we want to filter our source tags is it's a name value. We want to take every value. Our cloud extension will be X1 and we want to populate with cloud extension defaults. I'm going to click and create. And we're going to say yes to this. So, what's going to happen, is our run book when we created it will generate a CSV file for us that will outline the specifications of what exists inside AWS. So, let's open up that CXV file. Okay, so I'm in google sheets and what I'm going to do is I'm going to import that file, import, upload the file. And I am going to use comma as my separator. And I'm going to go import data. And what this creates is a spreadsheet that highlights all of the machines running inside our AWS and we can see the operating system, we can see a number of CPUs memory. So, it's a pretty good assessment of what we have within our other cloud providers. So, I need to edit this spreadsheet to allow me to tell migrate for compute engine what machines I want to migrate into google cloud. So, as we mentioned previously, we're going to migrate in our web machine and our file server. So, web machine here, I wrote him before. So, the first thing I want to do is I want to change this to one which will indicate this is one of the machines I want to bring in. And then for my file server, I will do the same thing. That's our first change that we want to do there. The second change we want to do is we want to highlight that the type of machine that will be needing within google cloud. If you remember from our AWS interaction we had machines that had different ways of specifying different naming for the type of machines we have in the cloud so we need to put in something appropriate. Okay, so, the machine I want is, we're going to go over to we're looking for specifically the column that says target instance type. And I've gone straight past it. >> You see your target instance type? So, let's go back it is. Call him zero. So, for row four I'm going to put in my machine type here which I'm going to use as a E two standard for and for my file server, do the same thing. Okay, so, there are the two machine types that I want to use. The one element that I need to remove from this is one of the tags we have. So, I need to scroll across to the tag columns and I need to remove. Yeah, AWS Cloud formation stack name. That's what they wanted to remove. I need to remove AWS Cloud formation stack ID. So, I can remove this column completely. Okay, so, we have updated our CSV file to represent the machines that we want to migrate in and we've specified what machine type there to be when they're being created inside google cloud. So, what I want to do now is I want to re download that file, download as a CSV file and you can see that's been done over here. I'm going to return to my migrate for compute engine interface and I'm going to know create a new wave using that CSV file. So, I'm going to be very imaginative with my title here and I'm going to call it wave one and I'm going to choose my file and I'm going to save. Now we can see that we have a wave one set up here, that run book data set up for our current time. We can look at the run book if you wish. We can look at the monitor, we can see it's AWS. But what's very important here is we need to validate it before we start going through the effort of actually trying to do the migration. It's far more sensible to take a short amount of time to validate what we want to do to make sure that it's going to be possible. So here, I'm going to click on our wave one action. Are we going to go to validate and yes, we are going to run the validation. And you can see here that it's running and validation and will return back once it is it has passed already. Okay, so now, we are at the process where we were able to begin our migration, we have our infrastructure set up in AWS, we have our landing zone created in google cloud. We have enabled all the APIs we need on google cloud plus our firewall rules to allow the communication between two platforms. We have configured our cloud extension, we have configured our source cloud in migrate for compute engine, we have configured our target cloud, we have created a run book from our source provider. We have edited that run book to represent what we want to bring into our target location. We have created a wave because we're migrating multiple machines at once and we have validated that the way we want to bring in will work. So, the next step to do here is to run a new job and our new job will be a full migration. I'm going to click start here and this will begin to actually bring the content into google cloud. If I click on my monitor icon, I can see the job that's beginning and as this process runs true, you will add details there. This process is going to take some length of time, about 60 minutes. So, we will use some editing and we will come back once the migration has completed. Okay, and we're back and we can see that both VMs now are ready to detach, what has happened between when we started this process and now, is that they ran to a series of options on the migration. So, the migration started to run, it prepared to migrate and that took a process of gathering the information and making sure that the, both the source and the target, we're ready to do the process. The actual migration itself, where it streamed the information from one provider to another provider occurred, and then it ran through preparing to detach, where it tidied up any of the connections that were made. At this point, both our machines are ready to attach, which means that our migration has completed successfully.
