ITjes en datjes

Dingen uit dagelijks IT werk

Proxmox Virtual Environment 1.9 cluster (en)

NL versie

Because it was time to refresh the network at home I started looking at avirtual cluster solution.

Previously I used FreeBSD with jails to seperate the servers and I wanted to keep that functionality. What I wanted op top of that was failover, to be able to move the servers in case of maintenance or problems with the virtual host.

My first experiences with Proxmox VE 1.9 were good, except that I wanted a different partitioning of the host as the standard bare-metal installation uses up the whole disk. Luckily that’s no problem as Proxmox can be installed on top of an existing Debian Lenny 64 bit server.

During the installation of Debian I set up a partial RAID layout with the software RAID option in Linux. Only the virtual environment needs to run on RAID 1, the important part of my data will be secured with a backup. All other data can be downloaded or ripped again (software, my own DVD and CD collection for my media center, etc.) so there’s no real need to use RAID here.
This way I still have redundancy but I won’t lose all my disk space on RAID.

I use the following layout:
/dev/md0, 512 MB RAID 1, ext2, /boot
/dev/sda2 + sdb2, 1GB, swap
/dev/md1, 8GB RAID 1, LVM, /
/dev/md2, 100GB RAID 1, LVM, /var/lib/vz
/dev/sda5 + sdb5, *, ext3, /data/local/01 + 02

Sda5 and sdb5 contain regular data, backup of the virtual machines from the other cluster and the backup of important data from the other cluster. This will be available through NFS shares.
Swap is optional as the servers have plenty of memory installed.

Installation of Debian is done with as few options as possible, after this the sources.list will be modified to include the Proxmox repository and the installation will be finished according to the instructions on the Proxmox Wiki.

What’s left are tweaks to the vzmigrate script to speed up migration and extra network bridges to seperate host traffic from virtual server traffic.

There’s no real high availability yet for VZ containers on shared storage but I’m looking at keeping downtime as short as possible using a combination of Heartbeat, DRBD and rsync.

Written by mnystrom

2011/11/16 bij 10:02

%d bloggers op de volgende wijze: