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

Red Hat Virtualization and vSphere

Developed with
Red Hat
play-arrow
Start course
Overview
DifficultyBeginner
Duration1h 10m
Students64
Ratings
5/5
starstarstarstarstar

Description

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.

Transcript

Hello. Welcome back to the technical overview on the Infrastructure Migration. We are going to do a walkthrough on Red Hat Virtualization and VMware vSphere. First, we will check on the components and main features that you can find on vSphere. Of course, you have a manager which is the vCenter and you have hypervisor which are ESXi which is a lightweight hypervisor and we used to have an ESX hypervisor which was a more beefy and customizable kind of hypervisor.

We have a feature called vMotion which is intended to be able to move VMs from one hypervisor to another without disrupting service. We have a software development kit vSphere SDK to be able to automate tasks in vCenter, and also, we have a high availability as we were talking about if we have a problem in one hypervisor, the VMs running on the hypervisor will get started in a different hypervisor. We have four networks in a distributed switch that will help us reach the right VLANs when accessing it from the virtual machines. And we have our resource scheduler which will help us distribute the VMs along the hypervisors in an efficient way.

So, in Red Hat Virtualization we have a Red Hat Virtualization Manager which is a manager for this virtualization platform that can be run as a virtual machine within the same hypervisors as the rest of the virtual machines. As hypervisors we can use Red Hat Virtualization hypervisor which is a stripped-down version of Red Hat Enterprise Linux which is intended to run only as a hypervisor and has everything that it requires in there. It can be updated from the Red Hat Virtualization manager without any issue so it is very, very focused and intended to people that are very into virtualization and that they are not into managing Red Hat Enterprise Linux. However, we can use Red Hat Enterprise Linux also as a hypervisor and then we could add agents or any kind of automated tasks in the operating system and use it as any other Linux operating system that we are using.

We have live migration which means that you could move one VM from one hypervisor to a different hypervisor without disruption of service. We have a storage live migration which means that we can reallocate the disks of the VMs in different storage arrays that are connected to our cluster. We have a software development kit to be able to automate tasks and also REST API to be able to access and automate tasks without having to need a development kit. There is a Linux bridge that is used to allocate logical networks. So, you have access to VLANs, whatever you are running your VM. 

We have scheduling policies that help you distribute the workloads along all the hypervisors in your virtualization platform. What else do we have in Red Hat Virtualization? We have a fresh new interface which is HTML5 based. We, we are using KVM as the engine for virtualization which is what most clouds are moving to because it is very, very efficient. We have a very easy to use API to manage any resource in the virtualization, and there is a complete feature set for everyday tasks for operations and to keep everything running. As a matter of fact, we have it in production, in heavy production, in many of our customers. 

So, let us take a look at how Red Hat Virtualization and vSphere are in real life. So, this is vSphere5.5. I am enabling Flash to access it. It is loading, and this vSphere is, it has a vCenter server and two ESXi servers. Let us access it. Have this flash interface, this is vSphere5.5. We can see VMs and templates here. We can use any template to instantiate any VM. Using VMWare tool, we will be able to configure it to have a, a different IP or different name or change any kind of characteristic within the VM. So, deploy VM from this template. Give it a name. And as you see this is pretty straightforward. We use a Cluster01. This datacenter which was a datastore which is NFS datastore. 

We can customize the operating system so we are saying by adding some specs to it and we are done. This is very lean and straightforward, we can, for example this VM we can migrate it. Move it to a different cluster, to, sorry, to a different host in the same cluster. So, as they are only two hosts, we cannot choose and we can just move it. So, as you can see this is like very straightforward being able to control. The datastores that we have available. This is the main one that we are using an NFS datastore, the hosts that we have available also, how they are running, ESXi hosts, so on. 

So, let us go to Red Hat Virtualization. This is Red Hat Virtualization 4.2 which is this HTML5 interface. It is super cool. And we can go here and see virtual machines that we have running in here, we have like four VMs running, one that is down. We just can create a new virtual machine. It is very straightforward. We have several templates available. Let's take rhel7. Okay. And we give it a name rhel7 machine and then data access options, initial run. I really like this. I mean in cloud we use Cloud-init to configure the VMs internally to change the IP, the name, or to add a user and this is what we are going to do. Let's have a username labuser and a password, okay, which is admin password for this. Not very nice but let's go for it. 

So, we can leverage all the cloud-init scripts that we have to configure VMs in clouds by using them in the Red Hat Virtualization. So, we are instantiating this VM. We have this VMs running. We can migrate one VM. Let us do it. Let us migrate this one. Migrate. We choose the destination host or we say to migrate automatically. So, right now, we are building one VM. We are migrating a different VM, jboss0, here. But in here we have our jboss cluster. You see it we have two jboss VMs. Well, even if I am migrating it I am not sure that I want both VMs on the same hypervisor as it is a cluster. So, we can go to the clusters. Choose the cluster that we are running on and say okay let us create an Affinity Group. New Affinity Group and we call it JBoss. We add these two VMs, jboss0 and jboss1 to the Affinity Group. And we say that we want negative affinity which means that we do not want these two VMs running on the same hypervisor. There we are. 

So, we have virtual machines. Oh, both of them are running the same hypervisor. Now the new scheduling policy will start and it will migrate the VMs so they are not running on the same hypervisor. It is very easy to create a scheduling policy here. Now let us run this VM, the one that we created right now. Just starting up. Meanwhile we can take a look at the storage domains. We have normally three storage domains. They are all managed the same which makes things very easy and straightforward. We have the vmstore for the VMs. We can add, add as many source domains as we want. 

We have the iso storage domain. It has, which can have all the images that we are going to use in the deployment machines. We have an export storage domain to be able to export the VMs and import them in different clusters or even in different platforms. So, let us go back to virtual machines. We have the virtual machines running. Starting Up. JBoss VM has been migrated. They are in different hypervisors. So, they are well distributed following our policies. And let us open a console.

The console in Red Hat Virtualization can be used in different ways. One of the ways is use in VNC which is straightforward and can be embedded in HTML. So, you do not need any kind of, of client to be able to access it. However, there is a Spice client which is a protocol that we use when we want to have a high-speed, high-performance console which is especially good if you, if you are watching videos. 

So, this is how our login page, labuser, and as you see, I just created a user within the VM using cloud-init. So, this is fresh and modern virtualization from Red Hat Virtualization. We have seen the current virtualization that you may be using in your data center. And as you can see we have a full feature set virtualization that is available for you to be able to run your workloads cost-effectively. Well, thank you very much for watching and see you in the next video.

 

About the Author

Students31462
Labs32
Courses93
Learning paths22

Jeremy is the DevOps Content Lead at Cloud Academy where he specializes in developing technical training documentation for DevOps.

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

Jeremy holds professional certifications for both the AWS and GCP cloud platforms.