OpenQRM and XEN LVM based HVM VM.

How to run multiple Virtual Machines (VM) in one Physical Server, and be able to manage them with a WebUI. The Virtaulized environement will be accomplished with Open Source Xen, and the management WebUI will be accomplished with Open Source, OpenQRM. Each tool will sit on a Linux Operating System; Debian.

Overview
-Requirements
-Assumptions
-Tutorial Objective
About OpenQRM
-About the OpenQRM Version
-About our OpenQRM Network
-About our OpenQRM Topology and Resource Allocation
[1.0] Chapter 1 - Install OpenQRM
[1.1] Step 1: Install Debian x64
[1.2] Step 2: Install Optional GUI and NX on Debian x64
[1.3] Step 3: Firewall/DHCP/NAT (MOnowall) Configuration
[1.4] Step 4: Network Interface Configuration
[1.5] Step 5. Install OpenQRM Server
[1.6] Step 6. OpenQRM Installer Configuration
[1.7] Step 7. Database Configuration
[1.8] Step 8. OpenQRM Web Interface Manager Configuration
[2.0] Chapter 2 - Install Xen and VM
[2.1] Step 1. Install and Provision Debian x64
[2.2] Step 2. Install XEN and configure
[2.3] Step 3. Install VNC and configure
[2.4] Step 4. Configure LVM for Xen VM
[2.5] Step 5. Install Xen Guest VM, on Xen Host LV
[2.6] Step 6. Xen Troubleshooting and Optional Useful CLI Commands
[3.0] Chapter 3 - Xen and OpenQRM Integration
[3.1] Step 1. Log into OpenQRM, enable, and start Plugins
[3.2] Step 2. Integrate XEN hypervisor server with OpenQRM server
[3.3] Step 3. Provision XEN-Storage Host in OpenQRM as Resource
[3.4] Step 4. Verify XEN LVM VM on Remote/Local XEN Host Server
[3.5] Step 5. Optional PXE Boot
[3.6] Step 6. Optional Import Xen Host Kernel to OpenQRM
[3.7] Step 7. Remove and Recreate VM (vmx01cms01.cfg) cfg file
[3.8] Step 8. Configure VM Image
[3.9] Step 9. Configure Appliance
[3.10] Step 10. Start the Appliance
[3.11] Step 11. Have Fun with VM

Overview

This LVM based HVM VM setup makes for a high perfomarmance VM.

Requirements

2 servers as follows:

• 1 Server for OpenQRM Server
• 1 Server for XEN (open source) Host.

OpenQRM server, (in our case) will not need to be a high performance server, because it’s only being used to manage Xen VMs in our local/remote cloud (virtual network). Xen Host, on the other hand is a high performance server, being that it will host multiple VMs. So each VM will be alotted CPUs, Ram, HDD space, etc…, to the extent of what the XEN host provides, i.e. Xen Host has 5 gigs of ram, Xen host gives 1 gig to each of the 4 VMs.

Assumptions

• You know how to use a text editor, i.e. nano.
• If you know what Xen is, then the rest is pretty easy, since you can simply copy and paste the commands.
• Using ‘root’ user, to perform all configuration and installations

Tutorial Objective

The following is the end result, of what we’ll acheive when you finish this tutorial.

• 1 OpenQRM Server (chapter 1)
  OpenQRM Cloud Manager
  Debian x64
  Host name (Server Name) qrm01
  fqdn qrm01.lc1.cloud1
  ip address 10.1.11.10

• 1 XEN Host Server (chapter 2)
  Xen Host
  Debian x64
  Host name (Server Name) x01
  Domain Name lc1.cloud1
  fqdn x01.lc1.cloud1
  ip address 10.1.11.11

• 1 VM on Xen Host Server (chapter 2)
  Xen LVM based HVM VM
  Debian x64 v5.06
  Host name (Server Name) vmx01cms01
  Domain Name lc1.cloud1
  fqdn vmx01cms01.lc1.cloud1
  ip address dhcp, (10.1.11.254 given by OpenQRM)

About OpenQRM

NOTE:
You can alternately check out my “get her done” tutorial, which is the same tutorial, but without any absolute (noob) beginner’s comments and explanations.

If this tutorial seems overwhelming, it’s because it is overwhelming.

If you haven’t heard about the OpenQRM Virtualization phenomenon, I will explain. With OpenQRM, you can now quickly deploy Xen host and Xen VMs; stop, start, resize, snapshot, revert, clone, live migration, windows, solaris, linux, mac, Citrix, VMWare, KVM, VitrualBox, change cpu, cpu numbers, kernel, swap, nic, ram, v2p, p2v, v2v, p2p, iscsi, pxe, puppet, HP LinuxCOE, Amazon, and ""infinite"" more configurations, with an attractive easy to use WebUI. Good bye to Virt-manager, Zentific, IBM Virtualization manager, and all the gui bulls–t, time-consuming ways I’ve tried to manage Xen. And the best part of it, I am not locked into solely Xen, I can easily manage VMware’s Virtual Server and ESX. I am not locked into Citrix XenServer. And I am not locked into the new baby KVM. I can also convert any supported VMs (i.e. vmdk to xen, and vise versa). I can awesomely leverage all types of storage! All this with (HA) High Availability and Naigos. OpenQRM has set the bar.

FYI - IMO:
We’re using OpenQRM’s feature set for managing VMs in our cloud. OpenQRM, was initially intended for Cloud Resourcing, in other words, with OpenQRM managing the cloud, you can sell, lease, let use, virtual machines to your human clients. IMO, openQRM should release two brands, one for Cloud Managing (for you and me) and one for Cloud Resourcing (for the ISP, Web Host Provider, etc…). So the names would read, OpenQRM CM and OpenQRM CR.

About the OpenQRM Version

OpenQRM versions 4.6 , 4.7, and later versions come with a self installation script, which also installs all the plugins (not enabled), so no need to download any extra packages, like most dated tutorials found online. It also has a Configuration Web Interface Manager, so you don’t have to worry about connecting to db. Everything is easy peasy.

About our OpenQRM Network

First off OpenQRM runs its own DHCP service (hands out IP addresses to it’s clients). If you have an existing DHCP service (server), i.e. modem/router with 10.1.10.1.x., than you’ll need to create two separate network subnets, i.e. 10.1.10 and 10.1.11.

In my tutorial, OpenQRM will bridge its static nic (10.1.11.10) with router and OpenQRM ’s dhcp service will hand out 10.1.11.x ip addresses to it’s internal network. Bridging seems complicated, but OpenQRM and XEN makes it easy; no knowledge needed. Since OpenQRM is bridged, only one nic is needed and there is no need for NAT on OpenQRM. Tools I recommend to accomplish separate networks, is placing monowall or dd-wrt in front of OpenQRM; in this tutorial I will reference monowall.

FYI:
Setting up the two networks and NAT, for noobs will be a feat in itself (not covered in the scope of this tutorial). If you are testing this OpenQRM tutorial, than use VMware Workstation, it has a built in NAT and DHCP Service; kind of ironic, ay.

About our OpenQRM Topology and Resource Allocation

OpenQRM recommended’s three servers. Server 1 is OpenQRM/mysql/dhcp/mailserver/lvm storage (for me, I use lvm storage sort of like "My Downloads" folder), Server 2 is the iSCSI Storage Server for your VM image deployments, and Server 3 would be your hypervisor (XEN, VMware Server, KVM, etc…) which contains your VMs; hence you can add more hypervisor servers to your cloud. So a typical setup with OpenQRM, is where the Hypervisor server stores the VM’s OS on the iSCSI Storage Server; in other words the VM’s OS is not stored on the Hypervisor’s own physical hdd. Unless, of course you utilize one of many plugins, OpenQRM offers. One of which, we’ll be using is the Xen-storage plugin, where instead of the iSCSI storing the OS, the hypervisor stores the OS, natively. The same can be done, for all hypervisors OpenQRM, supports. IMO, you would need an enterprise fibre channel storage server solution, to provide (near or the same) performance a physically attached storage, provides, i.e. ultra320 scsi. This is why we are using, the physically attached drive on the hypervisor for Xen, unless of course you have money to buy a NetApp Filer, he he; which OpenQRM happily supports. I googled, and found the same agreement, here "apples to apples.."

In my tutorial, we will use 2 servers. Server 1 is the OpenQRM server, which will be installed on Debian x64; this server has one raided hdd. Server 2 is the Xen Server, which will be installed on Debian x64. One LVM based HVM VM, will be installed on this server. This server, has one raided hdd.

Let’s get started on the next page 2, Chapter 1 - Install OpenQRM.

Bookmark to:

Pages: 1 2 3 4 5 6 7 8 9 10 11