Just in case anyone is interested, here is an update.
I have looked into using Debian Lenny, Proxmox, KVM, DRBD and Corosync to allow hot-standby of our systems and have a POC running.
This will be a 2-node setup.
We create a partition that will be replicated via DRBD.
Into this we persist our KVM VMs
Heartbeat manages the master/slave setup and starts/stops the VM via a script
On the master node we
1. mount the partition
2. copy over the KVM configs (it expects it in a certain place)
3. elevate this node to master for Proxmox
4. add the mounted partition as a resource to Proxmox
5. start the VM
on the slave exactly the opposite (if it is still running)
A nice environment with an installer CD and Web UI. It does offer many features out of he box such as migration of VMs, clustering servers and such.
Problem is, in our case we cannot use the CD so I had to revert to installing it manually and then step-by-step building up the system.
Problem 2: Proxmox does not directly support what we intend on doing.
Really rough overview of the steps:
1. Install & configure Debain Lenny amd64
2. Install and configure psmisc samba ntp ssh
3. configure network & hosts file using static IP's
4. Update the repository list for DRBD & Corosnyc (formerly Pacemaker) & PVE
5. install the PVE kernel (pve-kernel-2.6.32) and configure your boot menu
6. installing bridge-utils and bridge the network interfaces
7. install drbd8-modules-[version]-amd64 drbd8-utils (in my case version = 2.6)
WARNING: the Proxmox repo contains a drbd8-utils that is incompatible to the modules, so make sure your versions match!
For me it was 2:8.0.14-2
8. configure & set-up drbd
9. install and configure corosync
with our script mentioned above
10. install and set-up proxmox-ve-[pve kernel version]
If we install a VM that is supposed to be virtualized, we must make sure to install it to the replicated resource.
My script simply went through the list of VMs in that folder, update the config and would then start/stop them.
* for each new VM we add in, we manually have to copy the config to the replicated drive (from /etc/qemu_server), maybe a cronjob can handle this.
* Apache seems to sometimes not want to start after rebooting. A apache2 restart allows me to access the Web GUI again.
* As I mentioned, Proxmox does not really support what we want, though it has been indicated that this might be something for 2.0
If there is a desire to have a (incomplete) tutorial, pls just say so and I'll try to get clearance from my boss.
Currently I have been redirected to something else (similar, but in this case I only replicate PostgreSQL via DRBD&Corosync.. egad, anyone have a clue?) so updates might take a little.
Last edited by TheTank; 19th March 2010 at 10:27.