Configuring a Proxmox VE 2.x cluster running over a private OpenVPN intranet

From Proxmox VE
Jump to: navigation, search

You can find a detailed, step-by-step guide on how to configure a Proxmox VE 2.x cluster which runs inside a private OpenVPN subnet at the links below. This lets you configure some hand rolled High Availability using bargain basement servers which may or may not be located any near one another. It also lets you straddle clusters across NAT boundaries, so you could have a node in your house at home for example.

Part 1

http://www.nedproductions.biz/wiki/configuring-a-proxmox-ve-2.x-cluster-running-over-an-openvpn-intranet/configuring-a-proxmox-ve-2.x-cluster-running-over-an-openvpn-intranet-part-1

  1. Prepare Proxmox VE 2.x
  2. Configure the OpenVPN bridge on the public server
  3. Move the Proxmox on the OpenVPN server over to running exclusively on the VPN private subnet
  4. Adding additional Proxmox nodes

Part 2

http://www.nedproductions.biz/wiki/configuring-a-proxmox-ve-2.x-cluster-running-over-an-openvpn-intranet/configuring-a-proxmox-ve-2.x-cluster-running-over-an-openvpn-intranet-part-2

  1. . Configure a HTTP proxy so VMs can get security updates
  2. Final steps
    • Make non-web services on VMs appear on the public interface
    • Make web services on VMs appear on the public interface: haproxy, varnish, nginx

Part 3

http://www.nedproductions.biz/wiki/configuring-a-proxmox-ve-2.x-cluster-running-over-an-openvpn-intranet/configuring-a-proxmox-ve-2.x-cluster-running-over-an-openvpn-intranet-part-3

  1. Setting up self-replicating node storage using DRBD
  2. Configuring backing storage for the replicated data
  3. Setting up DRBD
  4. Adding the DRBD replicated storage to LVM so Proxmox can use it
  5. Making the replicated storage available for OpenVZ as well
  6. Accessing replicated content from one of the peer nodes
  7. Encrypted off-site backup (content added "3 months ago" ref -- 2012-08-17 17:25 UTC) (no content -- 2012-04-24 13:50 CEST)