Multiserver Setup with Virtual Servers - Infrastructure

Discussion in 'Installation/Configuration' started by arraken, Oct 31, 2013.

  1. arraken

    arraken Member HowtoForge Supporter

    Hello all!

    I postet some questions about ISPConfig multiserver setup and virtualization in the priority support forum. (see: I haven't got an answer yet, and i thought that maybe somebody has some answers, but cannot post in the priority support forum. So I started a new thread with the same questions (see the post below) in this forum. I hope that's ok, and if it's not i'll just delete one of the threads.
  2. arraken

    arraken Member HowtoForge Supporter


    At the moment I got an ISPConfig3 Server running in a standard singleserver setup, meaning all services are running on one root server (from hetzner).

    Now it's time to move on to a more sophisticated multiserver setup. My goal is to have 2-3 physical servers, with multiple virtual servers running on them. However i'm rather new to virtualization, and I never did a multiserver setup before, so I have a few questions.

    Below you see the general setup I want to achieve.


    From the tutorials and the posts in the forum I have read, I came up with the following procedure:

    1. Install OpenVZ and ISPConfig on Root1 following this tutorial:

    2. Following the same tutorial, create 3 VM's on root1 for www1, DNS1 and DB

    Now my first question:
    Q1: I want to install OpenVZ VMs for Mail, DNS2, WWW2, and DB2 on the Root2 and Root3 servers, as shown in the picture. I want to create and manage those VM's through the ISPConfig-Interface on Root1. How can that be done, and what do I have to install on Root2 and Root3. Only OpenVZ, or also ISPConfig as slave?

    If this all works as planned, I should have an infrastructure into which I can install an ISPConfig multiserver setup.

    Regarding that, I have another question:
    Q2: Where should I create the ISPConfig master for my multiserver setup?

    A: Should I make the ISPConfig installation on Root1 which manages the VM's the ISPConfig-Master
    B: Should I make WWW1 the ISPConfig master, which would result in a very similar setup to this tutorial:

    Option B would have the advantage that I don't mix my "virtual-machine management" with my "webhosting management". The ISPConfig installation on Root1 would only be used for VM's. But does this create any problems I may overlook?

    Q3: I also found this tutorial for a multiserver setup with OpenVZ which uses the OpenVZ Web Panel to manage the VMs

    Are there any advantages / disadvantages to using ISPConfig for managing the VM's?

    Regarding OpenVZ in general I have another question:
    Q4: I've read that Ubuntu 12.04 and OpenVZ don't work out of the box? (Discussed here:

    I have been only working with ubuntu server until now, and ideally I want to keep it that way. I found a guide by Falko which describes how to install openvz in Ubuntu 13.10 with some workarounds - but i'm not sure if it's a good idea to use that in production? The main goal of my setup is that it's stable and easily maintainable.

    So, that's all for now - I know that's a lot of questions, but I really want to get my setup right from the start, and I hope there are some experts who can help me out here.

    If I get my setup working and everything works as planned, I promise to make a nice summary so others may learn from it too. :)

Share This Page