1. Home
  2. Training Library
  3. DevOps
  4. DevOps Courses
  5. Red Hat Virtualization and Infrastructure Migration Technical Overview

Infrastructure Migration

Developed with
Red Hat
Start course
1h 10m

Virtualization is everywhere! Exactly what is it and how should you make use of it?

The "Virtualization and Infrastructure Migration Technical Overview" course will help you discover the benefits of open source virtualization, how to better manage your virtualization assets, and the best way to move traditional workloads from one virtualization provider to an open virtualization.

In this course, you will learn to:

  • Easily define infrastructure mappings.
  • Create migration plans to confidently balance your workloads.
  • Build migration plans to reduce your expenditure on virtualization.

Hello. Welcome back to the Technical Overview on Infrastructure Migration. This time we are going to do a demo on Infrastructure Migration. As we have seen, we have a vSphere environment with several VMs. In this case, there are four VMs. One is a load balancer with NGINX. We have two JBoss Enterprise Application Servers configured in domain mode. We have a database which is a Postgres database. This is a typical three-layer architecture for applications. There is a running application on top of this deployment, which is this one. It is TicketMonster. It is an application that is just a ticket shop for the internet, but it is a demo. The good thing about this is that it has a bot that can start requesting tickets as if people were just accessing the website and, well, requesting concerts or theater or whatever. 

So, once we have this running, we are going to check that we have Red Hat Virtualization. In here we have a couple of hosts ready to take their workloads and we have virtual machines, but we do not have any of the virtual machines that are in the vSphere. So, let us go to Red Hat CloudForms Management Engine. This is what we typically refer to as CloudForms. We get in here and we need to check that everything is properly configured.

First, we will go to the Infrastructure Providers and we will check that we have both infrastructure providers and they are okay. In case we need to recheck we could go to both of them and go to Authentication > Re-check Authentication Status. Once they are ready, we need to go to the Hosts and define our conversion host. Have two hosts here, one of them is this one kvm0. This host has two tags that define it as a transformation host or conversion host. One of them is the tag that says that it is a Transformation Host, and the second one, it is the tag that says which method it is going to use to convert the VMs. 

So, we have everything ready. Let us see the virtual machines. As we can see here we see the virtual machine. Let us go to vSphere. We see there are four virtual machines that we want to migrate. So, now we go to Compute > Migration > Overview. In this page, we will see how we can create an Infrastructure Mapping and a Migration Plan. First, we create Infrastructure Mapping. We give it a Name. We will call it ticket-monster-mapping. We can add a Description, Moving Ticket Monster VMs to RHV. Next. We see we have detected the clusters. We select a source cluster, the destination cluster, and we add it to the mapping.

Next, the datastores. The VMs are stored in the datastore called Datastore in vSphere and we will move them to the vmstore in Red Hat Virtualization. So, Add Mapping, we add the mapping. Next. We have a very plain network configuration which is simple. We have VM Network and ovirtmgmt and we add the mapping. In here we could have like admin networks, storage networks, service networks, whatever you may need. We could map them all together and then we create the infrastructure mapping. So, the mapping is ready to be used. We close this.

Now we need a Migration Plan. We create a migration plan and we associate it with an Infrastructure Mapping. We could have several mappings here ready to be able to be used. We will use the ticket-monster-mapping that we have just created. We will create now the ticket-monster-plan. There we go. Next. As we expect to use many VMs to be migrated, we will import a CSV file with the list of them. So, we have a CSV file with the four VMs that we want to migrate: the load balancer, the database and the two JBoss Enterprise Application Platform servers. And then we create the migration plan. 

This plan is scheduled to be running right now. So, we will connect to both platforms and it will start running immediately. We can see that the migration has started and the VMs are being converted from one platform to the other. So, we can check that the first step is to shut down the machines. The machines have powered off even if the icon does not reflect so. And they are being transformed. 

The good thing about using CloudForms and Red Hat Virtualization is that they are based on Red Hat Enterprise Linux so if you have Linux skills, you can keep an eye on what is going on by simply accessing log files. We see here how the orchestration is being performed behind the curtains, although I want to see it here with this nice interface that we have for VM migration. 

So, as we can see we go to Red Hat Virtualization, we see that the VMs have started appearing in the destination. We have the load balancer here. The image is locked and now it's finished importing. The rest of the VMs as you can see are arriving also. Great. They will be booted immediately once that they are imported. So, we have the four VMs here. Really like this feature that you can check the tasks to see how it is being imported each one of them.

Meanwhile the VMs in vSphere will be kept powered off. Just in case you want to have a rollback. The db has been imported. Now we are waiting for the enterprise application platform servers to finish importing. The application is now not running as we can imagine. Reload. Time out. So, a load balancer is running, but the application is not there yet.

So, we can imagine. So, now the four VMs have been fully imported in the cluster. And now they are being booted. Now all of them are booting. We can see CPU and Memory consumption here. Powering up. And finally, JBoss is up and running. Let us check the application. Now we can start it. So, as we can see it is pretty straightforward to migrate VMs from vSphere to Red Hat Virtualization using CloudForms and infrastructure migration plug-in. 

Thanks for watching and I will see you in the next video.


About the Author
Learning Paths

Jeremy is a Content Lead Architect and DevOps SME here at Cloud Academy where he specializes in developing DevOps technical training documentation.

He has a strong background in software engineering, and has been coding with various languages, frameworks, and systems for the past 25+ years. In recent times, Jeremy has been focused on DevOps, Cloud (AWS, Azure, GCP), Security, Kubernetes, and Machine Learning.

Jeremy holds professional certifications for AWS, Azure, GCP, Terraform, Kubernetes (CKA, CKAD, CKS).