Preview of Red Hat Virtualization Manager

Hi folks, when we last parted, I left you in the hands of the Next Generation Node. I gave you a preview of what’s coming from Red Hat in the form of the Red Hat Virtualization Host. What better to follow that up with than a preview of the Red Hat Virtualization Manager? Seriously, there have been so many updates and improvements, I can’t wait to dig in..

Let’s go!Installing things is very similar in version 4 as compared to the later versions of 3.x (3.5, 3.6). Several software repo’s that cover RHEL and JBoss EAP need to be subscribed to, and that’s highlighted in the demo below. There is the option of running the virtualization manager as a standalone application (bare-metal), a virtual machine, or in “hosted-engine” configuration.

“Hosted-engine” is a special configuration for Red Hat Virtualization Engine where it deployed as a VM on a node that it also manages. This provides High Availability for the virtualization manager and also reduces the overall number of servers required. In the case of the demo below, I’ve deployed it as a VM. (I plan to have a separate demo just for hosted-engine.)

Once the repo’s are subscribed to, the system needs to be updated and then virtualization manager can be installed. One command will pull down all of the required packages. After that, the “engine-deploy” command is used to launch the configuration wizard. In many cases the defaults will be just fine, but pay attention to what the wizard is asking for. In the demo I’ve highlighted some things to look out for or things that are new as compared to version 3.x.

My recommendation is to always choose to deploy Data Warehousing. That’s where all of your good stats get pulled from. You can always choose to not use them, but traditionally it’s been easier to “not use them” as compared to try and install “DWH” after the fact.

Also, if you’re paying attention to my demo, you’ll see that I’ve selected a local NFS share for my ISO images. This is perfectly acceptable for home labs, such as mine. I would never recommend that for production use or work labs.

Once the configuration is complete, it will list out your URLs (http and https) to choose from and then we’re off! The login screen is really no different as compared to RHEV 3.x. We select the administrator portal.

However, the first thing that we’re presented with upon login is NOT the Virtual Machines tab, but the “Dashboard” tab. BOOM! It doesn’t look like much when we don’t have hypervisor nodes, VMs, or other resources yet, but trust me. Once we’ve populated our environment the Dashboard tab might just become your favorite tab. It presents important information in an easy to consume fashion and still easy on the eyes.

Let’s look at the video (best viewed in full screen):

As suggested in the video, I fully plan to follow this up once I add in hypervisor nodes, VMs, etc. I’m not going to do a full blown series like I did for 3.6. Adding hypervisors, storage, etc, hasn’t changed. However, I will show you the new things, or things that I didn’t show you before.. Hosted-engine configuration, migration policies (new!), etc.

As always, comments and questions are welcome.

hope this helps,

Captain KVM

 

Agree? Disagree? Something to add to the conversation?