Yep, you read that correctly folks. I’m going to show you how to import VMs from vSphere into RHEV, right from RHEV-M. Why would you want to do that?? For starters, maybe you simply want to move virtualization platforms. You have some virtual machines that you happen to like, you just don’t feel like rebuilding them from scratch. That doesn’t make you lazy at all. It means you’re planning. Or maybe a little lazy, but mostly that you don’t want to do your work over if there wasn’t anything wrong with it in the first place.
Work smarter, not harder. Continue reading “Deploying RHEV pt6 (Importing vSphere VMs)”
We’re officially on a roll here and making headway. This is the last major deployment and/or configuration step within RHEV before we start pushing things around. Yes, there are lots of bells and whistles, but in terms of “compute”, “storage”, and “network” resources, this rounds it out. Let’s get to it. Continue reading “Deploying RHEV 3.6 pt5 (Networks)”
We’re moving right along in this series of deploying RHEV. Up until now, we’ve been busy getting our basic underpinnings in place: management platform (RHEV-M), hypervisors, and storage (data domain & ISO domain). Now that those underpinnings are in fact there, we can put things together and actually get some basic work done. Continue reading “Deploying RHEV 3.6 pt4 (Provision VMs)”
This is a very quick follow up to my last post as I want to keep you moving along in your endeavors. We’ve deployed RHEV-M, we’ve added a RHEL hypervisor, but before we can provision any VM’s, we need to attach storage. In this case, we’re going to attach NFS.
Let’s get started. Continue reading “Deploying RHEV 3.6 pt3 (Storage)”
In my last post, we deployed RHEV-M, the Web UI & brains for Red Hat Enterprise Virtualization (RHEV). This week, I’m pushing on to the next logical and required step in the process – deploying a hypervisor. Continue reading “Deploying RHEV 3.6 pt2 (Hypervisors)”
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”. Continue reading “Deploying RHEV 3.6 pt1”