Search Engine: Elastic

Article ID: 116551, created on Jul 25, 2013, last review on Jul 24, 2014

  • Applies to:
  • Operations Automation 5.4


There is set of requirements to be satisfied to correctly add a new physical or virtual Linux shared hosting server to POA.

The article provides a kind of checklist which allows to avoid most common mistakes during new host deployment in POA.


  1. Make sure OS version, edition and architecture of the host match requirements.

    Every single type of Linux shared hosting service has its own requirements to the servers where it may be running. Refer to the corresponding POA Deployment Guide for the official system requirements. E.g. system requirements for Linux Shared Hosting NG server may be found in the Linux Shared Hosting Deployment Guide.

  2. If you register Virtuozzo for Linux VPS (virtual server) make sure that you follow the correct steps:

    1. Register the new virtual server as VPS, not as hardware node. To correctly register virtual server do this in POA Provider Control Panel at Service Director > Virtuozzo Manager > VPSs, not at Deployment Director > Server Manager > Hardware Nodes. If you register Virtuozzo VPS as hardware node POA will not be able to manage IP addresses on the host.

    2. Register the Virtuozzo VPS as 'Shared' one, not as 'Dedicated'. This means that you must use the resource based on the Virtual Private Servers (Shared) resource class to create new VPS-based Linux shared hosting server, not the resource based on the VPS (dedicated) resource class.

    3. Make sure that correct BackNet IP address is assigned to the new VPS. This means that correct BackNet IP pool must be assigned to a Linux-based VPS Hardware Node during registration in POA. This BackNet IP pool is used during Shared VPSs provisioning - Shared VPS automatically obtains BackNet IP Address from it. BackNet IP Address is used by POA Agent installed on Shared VPS to communicate with POA Management Node.

    Documentation for configuring IP pools on hardware node for provisioning of shared VPSes and for registration of shared VPSes are described here:

    Most important part here is: Note: Usually you should select the Select IP pool(s) to use option and specify the IP Pool. In this case the VPS obtains the BackNet IP Address from the IP Pool assigned to VPS Hardware Node and the FrontNet IP Address from the specified IP Pool. In some rare cases you need to create Linux-based Shared VPS having only the BackNet IP Address, for example when you create the VPSs for MySQL or PostgreSQL database servers. In this case you should select the Select IP pool(s) to use option and do not specify any IP Pool.

    POA chooses backnet IP address implicitly by checking list of IP pools assigned to hardware node that have purpose "Infrastructure configuration" and picking the first one that has available IP addresses.

    Basic guidelines to have correct pair of IP addresses (1 backnet - used for POA agent and 1 frontnet) assigned to shared VPS is as follows:

    • IP pool with backnet IP addresses must be attached to hardware node and must have purpose "Infrastructure configuration".
    • IP pool with frontnet IP addresses must not be attached to hardware and must have purpose "Infrastructure configuration" and "Shared hosting"
    • When creating VPS, in the wizard you should choose option "Select IP pool(s)" and select 1 IP pool - the one with frontnet IP addresses.
  3. If you register physical Linux shared host in POA Control Panel at Deployment Director > Server Manager > Hardware Nodes make sure that you use BackNet IP address to do this.

  4. If you register physical Linux shared hosting server make sure that the yum utility is installed and properly configured (in part of repositories) on the host.

  5. Make sure that firewall is correctly configured on a Linux shared hosting server. Correct firewall configuration depends on type of services which will be running on a host. Refer to the corresponding part of the Parallels Automation Firewall Configuration Guide for correct firewall configuration for a particular Linux hosting server.

  6. If POA package installation fails during host registration you may find reason of problem in two places in Control Panel:
    • System Director > Notification Manager > Notifications Log. Of course, corresponding HTTP notification subscription must be created first and the needed events must be added to it, like Package installation failed, Package installed and so on.
    • If you install POA package on the host manually using PPM Group Operations then POA creates corresponding background task and its status may be monitored in Task Manager.

ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF