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

The Role of Cloud Management Platform in 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 course on Infrastructure Migration. We’re going to talk about the role of the cloud management platform in the infrastructure migration right now. So what is a cloud management platform? Cloud management platform is a piece of software that connects different infrastructure providers, cloud providers, automation providers, any provider of resources that IT could use for their own needs and tasks. So, in this case, we have CloudForms.

CloudForms is, Red Hat CloudForms, is a product from Red Hat that connects to both Red Hat Virtualization as well as to vSphere. It also can connect to Amazon Web Services, Google Cloud Engine, Azure, Ansible Tower - many other providers that can be managed from this management platform. So what is, in essence, a cloud management platform? It is a manager of managers. It connects to other managers like, in this case, vCenter or Red Hat Virtualization Manager, to be able to perform tasks in a similar way in both of them from a single pane of glass. It is great because it provides a good point to be able to orchestrate tasks in any of the platforms, virtualization platforms as well as cloud platforms, that we may have. So we can execute tasks in all the hosts, in all the VMs, around all the VMs that are running on our platform. We can do also some automation with Ansible, which comes inside of CloudForms, whenever we need to perform a lower-level task than orchestration. 

So one of the good things about having a cloud management platform is that you have visibility on all the objects of your infrastructure. In this case, we can see that connecting CloudForms to your vSphere deployment or to your RHV deployment provides you visibility on all the clusters that are running, all the hypervisors that you have, all the storage that is being used, the VMs that are running. You could even get into the VMs and check if they have been updated or not and send a message to whoever is not updating those VMs saying, "Hey, this VM needs updating because it has security problem." And if not, you can shut it down or even delete it.

So we have a single point of management to manage all the virtualization objects in the virtualization platform, which in this case, the most important ones are the clusters, the hosts, the datastores, the networks, and of course, the VMs. As we were saying, the cloud management platform, CloudForms, will do the orchestration on moving VMs from one place to another because it has visibility on all the resources on our virtualization platform. And to do so, we need the conversion hosts, which by default will use the RHV hypervisors, to do the VM conversion. The good thing about this is that they scale horizontally.

So first thing, we need to be able to do the mapping, as we said in the previous video, to know what clusters are corresponding with other clusters in our virtualization platforms. What VMs are going to be moved? What hypervisors are we going to use for conversions? What does datastores are equivalent in origin destination? And what networks need to be mapped? Once we have done that we can identify the VMs to be migrated and we can do the large batches. And then we need to also identify the conversion hosts.

All of this identification, all this information is, whether in tags in CloudForms or in the database in CloudForms, so all these points of being able to identify what is going to do what and when and where is done by the cloud management platform. As we are saying, CloudForms will use tags and database objects to be able to do that, to be able to create infrastructure mappings and to be able to create migration plans, and also to assign the conversion hosts for those. So the cloud management platform will perform the orchestration by setting up the migration groups, by preparing the VM transformations, by doing all the checks that are needed, and by doing pre- and post-migration automations. So let’s see it.

So this is Red Hat CloudForms Management Engine, CloudForms. Latest version, better version. Once we get in CloudForms, we see this dashboard. We can do many dashboard reports, and say, Chargeback and check Timelines, to be able to know when we are going to run out of space in our disk. But let’s check just this default dashboard that shows the number of VMs in each platform. And we see here the hypervisors in each of the platforms that we have. We have a Red Hat Virtualization with two hypervisors and we have VMware, vSphere with two hypervisors. They are the same size. 

We have here the discovered hypervisors or, as we call it in CloudForm, hosts. Have the Guest’s information. This is the operating system in the VMs that we are running. And well, many other things that we connect here. We can go to Compute and we see that we can manage some clouds here. We can manage containers. And we are right now focusing on managing infrastructure. 

This is virtualization providers. We go to Compute>Infrastructure>Providers. We will see that we have two providers: vSphere and Red Hat Virtualization. Let’s go down Red Hat Virtualization to see all the information that is here. You will see the clusters, the hosts, the datastores, the VMs and the templates. We will go to the hosts. We have two hosts configured for Red Hat Virtualization. These hosts can be configured in two ways. One way is using Red Hat Virtualization hypervisor which is a minimized set of Red Hat Enterprise Linux just for virtual machine hypervisor. So this is very straightforward to deploy. You just use an ISO image and you just deploy it and use menus to deploy and it’s very straightforward.

However, if you are very comfortable with Linux or you need to add any kind of variant to your hypervisor, you can use Red Hat Enterprise Linux as a hypervisor. Which is what we are doing here. So let’s get into the hypervisor kvm0 and check all the information that we see available. We see the IP, we see the amount of cores per socket, the CPUs, the memory, the datastore that it’s accessing, everything. And here we can see that we have these tags. We can go to Policy, Edit Tags, and we will see we have two tags to identify this hypervisor as a conversion host or transformation host. One of the tags is that we’re assigning the value true to conversion host and the second one is the method that we are going to use for this transformation. 

What else do we have? We have the VMs that we’re going to migrate. We can see them here. As we can see here, we see all the VMs that are running in all the platforms. We have four VMs running in vSphere, which are this load balancer, which are two JBoss Enterprise Application Platform servers, and one database with PostgreSQL, and one application running on these servers. We will see more about this later.

We can just go to the vSphere objects and see the two templates that we have on rhel7 and rhel6 with VMware tools included and the VMs running here. We can go to RHV and see that we have all these VMs running on all these templates; rhel-7.4 here, running windows, and windowsXP. Windows has also support of Red Hat Virtualization. We see that we have these compute resources and also these resource pools, datastores, all the objects in both virtualization platforms, can be seen from Red Hat CloudForms Management Engine. And therefore, this is why we are using it as our orchestration point for the infrastructure migration. Thank you very much. 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).