I am not sure if this has been discussed before - but thought I would mention it as a potential 'solution' in some environments.
The one issue I have always had with OpenVZ containers is the fact that I have to use local storage. As a business I am pushing constantly to use the SAN, yet find myself being pulled towards the ease of OpenVZ.
Nothing really wrong with local storage, but live migrations are in my experience - hit and miss, and yet again.. it is another node to 'backup actively'.
It dawned on me eventually... why not put a maxed out KVM box on the SAN, and install Proxmox into the KVM box. That way I can run my OpenVZ containers in the KVM unit and then easily 'live migrate' the whole node!
Well. The good news is that it worked beautifully. Yes.. the containers are slightly slower because of the KVM overhead, but with the right hardware - it just works!
Stranger is the option you have of joining your KVM node to the master cluster. Plain weird when you are using nested proxmox installs!
Key things I have done on my virtualised proxmox installs are:
1. Make Sure you use virtio for storage and network
2. Use a RAW disk
3. In the kernel boot options I have found 'nohz=1' and 'elevator=noop' to improve overall performance. (no idea why!)
Might not be the right fit for you.. but this solution does work quite well for me
Rob
The one issue I have always had with OpenVZ containers is the fact that I have to use local storage. As a business I am pushing constantly to use the SAN, yet find myself being pulled towards the ease of OpenVZ.
Nothing really wrong with local storage, but live migrations are in my experience - hit and miss, and yet again.. it is another node to 'backup actively'.
It dawned on me eventually... why not put a maxed out KVM box on the SAN, and install Proxmox into the KVM box. That way I can run my OpenVZ containers in the KVM unit and then easily 'live migrate' the whole node!
Well. The good news is that it worked beautifully. Yes.. the containers are slightly slower because of the KVM overhead, but with the right hardware - it just works!
Stranger is the option you have of joining your KVM node to the master cluster. Plain weird when you are using nested proxmox installs!
Key things I have done on my virtualised proxmox installs are:
1. Make Sure you use virtio for storage and network
2. Use a RAW disk
3. In the kernel boot options I have found 'nohz=1' and 'elevator=noop' to improve overall performance. (no idea why!)
Might not be the right fit for you.. but this solution does work quite well for me
Rob