Hi,
did a setup of Proxmox VE Cluster and tested it in the last days.
Most of it works quite well, especially considering the fact, that I never used Proxmox before.
As I had some minor issues I'd like to report about the setup and ask a few questions.
I used two Core2 machines with 4GB Ram each as Cluster-nodes.
For storing the images I used our centralized storage, connecting via NFS.
The nodes where setup via the 2.0beta ISO-Image and connected as discribed in the Wiki.
As guests I installed 4 different Debian squeeze machines containing a house-made toolset to emulate our standard requirements.
As an addition I installed a Windows2008R2 server as a guest to play around with Windows as well - despite we don't use windows in our normal day-to-day work.
Each of these guests got assigned 2GB of RAM.
Migrating the vm's from one node to the other worked like a charm most of the time, even running all of them on one node and rebooting the other node worked perfectly. I even tried to migrate while doing some heavy calculations in a Firebird-SQL database - this worked as well.
Two times (out of may be 100) the guest machine stopped running on migration (both times the Windows Server) although I checked the "live" checkbox when migrating. Unfortunatly I was not able to reproduce this error.
There are still some open questions:
- When using a cluster I would like to get an automatic failover upon Hardware-failure of one of the nodes. We already have automatic failover for the storage, so no problem here. Can someone recommend a path to follow?
- I did'nt find a clear way to backup the machines. What is the recommended way?
- When opening a console I get some undefined keymap. e.g. I did'nt find a way to send a - to the guest. So no way of typing "apt-get update" in the guest machine. On the node we use german keyboards and I even tried to do a "dpkg-reconfigure locales" on the nodes - but no success. The same problem is on the Windows-Guest.
- when connecting with Firefox from a 64Bit Linux box the console crashes Firefox frequently. It worked with some Proxmox 1.9 test-installation. For now we use Chromium as a browser which works ok.
regards
Lukas
did a setup of Proxmox VE Cluster and tested it in the last days.
Most of it works quite well, especially considering the fact, that I never used Proxmox before.
As I had some minor issues I'd like to report about the setup and ask a few questions.
I used two Core2 machines with 4GB Ram each as Cluster-nodes.
For storing the images I used our centralized storage, connecting via NFS.
The nodes where setup via the 2.0beta ISO-Image and connected as discribed in the Wiki.
As guests I installed 4 different Debian squeeze machines containing a house-made toolset to emulate our standard requirements.
As an addition I installed a Windows2008R2 server as a guest to play around with Windows as well - despite we don't use windows in our normal day-to-day work.
Each of these guests got assigned 2GB of RAM.
Migrating the vm's from one node to the other worked like a charm most of the time, even running all of them on one node and rebooting the other node worked perfectly. I even tried to migrate while doing some heavy calculations in a Firebird-SQL database - this worked as well.
Two times (out of may be 100) the guest machine stopped running on migration (both times the Windows Server) although I checked the "live" checkbox when migrating. Unfortunatly I was not able to reproduce this error.
There are still some open questions:
- When using a cluster I would like to get an automatic failover upon Hardware-failure of one of the nodes. We already have automatic failover for the storage, so no problem here. Can someone recommend a path to follow?
- I did'nt find a clear way to backup the machines. What is the recommended way?
- When opening a console I get some undefined keymap. e.g. I did'nt find a way to send a - to the guest. So no way of typing "apt-get update" in the guest machine. On the node we use german keyboards and I even tried to do a "dpkg-reconfigure locales" on the nodes - but no success. The same problem is on the Windows-Guest.
- when connecting with Firefox from a 64Bit Linux box the console crashes Firefox frequently. It worked with some Proxmox 1.9 test-installation. For now we use Chromium as a browser which works ok.
regards
Lukas