This week we’re going to cover how to configure our RHEV system for High Availability (HA). Specifically to handle VMs that need to be restarted automatically should something happen to the underlying hardware. Keep in mind, not every VM needs HA and not every VM with an HA configuration needs the same priority. We’re going to cover that as well as some optional features that may or may not be needed for your VMs, depending on the scenario.
Let’s get started Continue reading “Using RHEV 3.6 (Configure HA Virtual Machines)”
We’re now firmly rooted in getting work done and doing more fun things in Red Hat Enterprise Virtualization at this point. We’ve moved on from “deploying” in that we’ve deployed RHEV, we’ve deployed resources, and we’ve even imported some resources from a completely different hypervisor/environment. Today, we’ll talk about and demonstrate another cornerstone feature of any enterprise virtualization platform:
Live migration Continue reading “Using Red Hat Enterprise Virtualization 3.6 (Live Migration)”
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)”
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”