Deploying RHEV 3.6 pt1

Hi folks,

A few weeks ago, I made a suggestion/push/case for what I casually refer to as “cloud light”. As a brief recap, it just means using a hybrid management platform (aka cloud management platform) to front a traditional virtualization platform like RHEV. In the end, you get automation, integration, self-service, API and everything else you would want from “private cloud”. See my previous article on Should I Migrate to the Cloud?  for the “why” or “why not”..

Before we get to our “cloud light”, we need to start by deploying our traditional virtualization. In this case, “RHEV”.I don’t want to go too heavy on the writing here, but I do want to provide you with a little background to the recorded demo that I’ve included. First off, understand that I’m not working with high end gear; it’s my home lab after all. Using enterprise gear in your data center will provide enterprise performance. Next, I did in fact cut out a lot of footage for the sake of time. Everything that I’m doing is well documented at Red Hat’s Virtualization documents page.  I just want to provide an overview.

So what do I cover in the video? I have a VM deployed with RHEL 6.7,  that I then update and install the RHEV-M (RHEV Manager) related packages. From there I configure and deploy RHEV. There really isn’t much more to it. Have fun.

(Best viewed in full screen.)

As you can see, it’s really straightforward. I didn’t hide anything difficult; it really is that easy. Future demos will build on this demo: adding hypervisors, adding storage, adding networks, and getting actual work done. Want to know more check out these links:

https://www.redhat.com/en/technologies/virtualization
https://access.redhat.com/products/red-hat-enterprise-virtualization/evaluation

Next up, we’ll add some hypervisors to the mix, so stay tuned..

Hope this helps,

Captain KVM

2 thoughts on “Deploying RHEV 3.6 pt1”

  1. Hi Captain,
    Does it really necessary to subscribe with RedHat as at some places we may not have direct internet connectivity to the RHEV-M ? Cant we just download the required packages and setup local repository to proceed ?

Agree? Disagree? Something to add to the conversation?