Infrastructure Migration Architecture and Usage
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.
Right now we are going to check on Infrastructure Migration Architecture and Usage. So, our goal is to be able to move virtual machines from one virtualization provider, in this case, vSphere to another virtualization provider, which is Red Hat Virtualization. To do so we will use a cloud management platform which is called CloudForms that will connect to both virtualization providers, and we will get all the information in there with all the objects that virtualization platforms have such as clusters, hypervisors, VMs, datastores, and networks.
With this information, we will be able to perform the migration and orchestrate all the transformations that are required. So, remember in CloudForms we have a single point to manage all the virtualization objects that are involved in this migration, the clusters, datastores, networks, and hypervisors are the main ones that we need to care for.
To manage those objects, we will create an infrastructure mapping in which will map the networks in the point of departure to the networks in the point of destination so they are the same networks, their storage in the point of departure to the storage on the point of destination so they are equivalent in performance and quality and space, and of course, the clusters, which hold all these other objects together.
We will create this infrastructure mappings first, and then we will be able to create our migration plan. The migration plan is a set of VMs that will be migrated together and to do so we will use conversion hosts.
So first, how do we configure a conversion host? In this case, we are going to use one hypervisor in Red Hat Virtualization as a conversion host. But it will be possible to use any other VM or machine to be able to perform the migration. The good thing about using the hypervisor is that they will scale out properly with the size that will be required for the number of VMs to be migrated.
So, once we have chosen our hypervisor to act as conversion host we need to tag it within CloudForms. And first, add a tag saying that it will be a conversion host and second add a tag specifying which method will be used for the conversion. So, now we have our conversion hosts and we assign it to CloudForms. And CloudForms can manage these conversion hosts.
What next? Pretty simple. We create an infrastructure mapping. As we have described before, we need to map their resources in the point of departure to the resources in the point of arrival. And in here we do it by adding entries to the database in CloudForms. So, these entries will be managed as a one single entity called infrastructure mapping.
Once we have the mapping ready, we will have to define the migration plan, which is simple. A list of VMs that we need to migrate with a characteristics -- with the characteristics of one infrastructure mapping. So, we assign the infrastructure mapping to the migration plan, and then we move the VMs from one point of departure to the point of arrival. And this way we have all our VMs migrated, or some, to the destination.
That concludes this section and see you in the next one. Thanks for watching.
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, GCP, Azure), Security, Kubernetes, and Machine Learning.
Jeremy holds professional certifications for AWS, GCP, and Kubernetes.