Parallels Operations Automation 2.9 Linux Platform Deployment Guide

Size: px
Start display at page:

Download "Parallels Operations Automation 2.9 Linux Platform Deployment Guide"

Transcription

1 Parallels Parallels Operations Automation 2.9 Linux Platform Deployment Guide Revision 6.44 (22 July, 2009)

2 2 ISBN: N/A Parallels 660 SW 39th Street Suite 205 Renton, Washington USA Phone: +1 (425) Fax: +1 (425) Copyright 2009, Parallels, Inc. All rights reserved Distribution of this work or derivative of this work in any form is prohibited unless prior written permission is obtained from the copyright holder. { Patented technology protected by U.S.Patents 7,328,225; 7,325,017; 7,293,033; 7,099,948; 7,076,633. Patents pending in the U.S.} Product and service names mentioned herein are the trademarks of their respective owners. Parallels Operations Automation is a registered trademark of Parallels.

3 3 Contents Preface 5 Documentation Conventions... 5 Typographical Conventions... 5 Feedback... 7 Installing Linux-based POA Management Node 8 Installation Preconditions... 8 Creating and Configuring VPS (for POA on VPS) Installing POA Management Node First Login to POA Installing License Key Deploying POA Management Node in Virtuozzo Failover Cluster 18 Deploying Linux-based POA Management Node in Virtuozzo Failover Cluster Description Deployment Scheme Network Interfaces and IP Addresses Hardware Requirements Deploying Virtuozzo Failover Cluster Installing POA Management Node Deploying Native Repositories 23 Description Deploying System Native Repository Deploying External Native Repository Deploying POA UI on Linux 27 Creating UI Server Creating Attribute Preparing Node for UI Server Installing POA Packages Marking UI Server as Ready to Provide Restarting Java on UI Server Creating Branding Server Creating Attribute Preparing Node for Apache Web Server Installing POA Packages Creating Brand Creating 'Physical Hosting (Apache)' Resource Type Creating 'Branding Access Points' Resource Type Creating Website Creating Brand PBA Online Store Publishing Automation Creating Certificate for Brand... 48

4 4 Parallels Operations Automation 2.9 Parallels Deploying Branding 50 Deploying Linux-based DNS Servers 51 Installing DNS Server on VPS Installing DNS Server on Hardware Node Deploying Privacy Proxy 55 Hardware Requirements for Privacy Proxy Server on Linux Installing POA Packages Deploying Request Tracker 57 Installing Request Tracker Service Installation Requirements for Request Tracker Service Configuring Request Tracking Adjusting Permissions for Request Tracker Users Registering Request Tracker in POA Common Operations 60 Creating Attributes Adding Attribute to Host Registering Linux-based Hardware Nodes Prerequisites Creating 'Hardware Nodes' Resource Type Creating 'Traffic' Resource Type Obtaining Host Initial Data File Generating Hardware Node Distribution Installing POA Agent Registering Linux-based VPS Hardware Nodes Prerequisites Creating 'Traffic' Resource Type Creating 'VPS Hardware Nodes' Resource Type Creating 'Shared VPSs BackNet IPs' IP Pool Synchronizing VPS Hardware Node with World Time Registering VPS Hardware Node in POA Creating VPS Installing RPM on Host Installing PPM Packages Adding a Package Installing a Package on the Host Index 83

5 C H A P T E R 1 Preface In This Chapter Documentation Conventions... 5 Typographical Conventions... 5 Feedback... 7 Documentation Conventions Before you start using this guide, it is important to understand the documentation conventions used in it. Typographical Conventions The following kinds of formatting in the text identify special information. Formatting convention Type of Information Example Special Bold Italics Items you must select, such as menu options, command buttons, or items in a list. Titles of chapters, sections, and subsections. Used to emphasize the importance of a point, to introduce a term or to designate a command line placeholder, which is to be replaced with a real name or value. Go to the QoS tab. Read the Basic Administration chapter. The system supports the so called wildcard character search.

6 6 Parallels Operations Automation 2.9 Parallels Important Note Monospace Preformatted Preformatted Bold An important note provides information that is essential to the completion of a task. Users can disregard information in a note and still complete a task, but they should not disregard an important note. A note with the heading Note indicates neutral or positive information that emphasizes or supplements important points of the main text. A note supplies information that may apply only in special cases for example, memory limitations, equipment configurations, or details that apply to specific versions of a program. The names of commands, files, and directories. On-screen computer output in your command-line sessions; source code in XML, C++, or other programming languages. What you type, contrasted with on-screen computer output. <> The value enclosed in angle brackets is variable, i.e. depending on the context it can take this or that value. CAPITALS KEY+KEY Names of keys on the keyboard. Key combinations for which the user must press and hold down one key and then press another. Important: The device drivers installed automatically during Setup are required by your system. If you remove one of these drivers, your system may not work properly. Note: If Windows prompts you for a network password at startup, your network is already set up and you can skip this section. The license file is located in the httpdocs/common/licenses directory. # ls al /files total # cd /root/rpms/php Go to unpacked OS directory: # cd <POA_DIST>/rpms/<OS SHIFT, CTRL, ALT CTRL+P, ALT+F4

7 Preface 7 Feedback If you have found a mistake in this guide, or if you have suggestions or ideas on how to improve this guide, please send your feedback using the online form at Please include in your report the guide's title, chapter and section titles, and the fragment of text in which you have found an error.

8 C H A P T E R 2 Installing Linux-based POA Management Node Any Parallels Operations Automation software deployment starts with the installation of the Management Node (MN), a POA system core. After you install the MN and log on to it, you can add all the other system components via POA User Interface (UI). This chapter informs you on POA installation requirements and procedures. POA MN can be installed on one of the following types of hosts: Virtual Private Server Physical Server In This Chapter Installation Preconditions...8 Creating and Configuring VPS (for POA on VPS)...11 Installing POA Management Node...12 First Login to POA...15 Installing License Key...16 Installation Preconditions Before installing POA software, make sure that the following preconditions are met: The physical server designated to be the POA MN meets the following requirements: Server Names Description Density LINMN POA Management Node on Linux. Server runs the POA management software. 50,000 accounts Quantity 1 OS RHEL 5 (x86 or x64) CentOS 5 (x86 or x64) RHES 4 (x86 or x64) CentOS 4 (x86 or x64) Software To be installed by the Customer: OS only

9 Installing Linux-based POA Management Node 9 Supported Virtualization CPU RAM Parallels Virtuozzo Containers (PVC) 3.x/4.0 for Linux 2 core (3GHz or higher) 4GB Disks Array 1: Disk Partitioning Array 1: NICs OS and software - 3 x 72GB, SCSI, RAID 5 (hardware impl.) / 5GB - for OS 2 x RAM size (8GB) - swap /usr - 20GB - for software /var - remaining space - for POA system database and logs BackNet

10 10 Parallels Operations Automation 2.9 Parallels At least one external DNS server is configured. SMTP server with the open relay for MN is configured. If you are installing POA on Physical Server, the following supplementary preconditions must be met: 1 The target server is assigned a BackNet IP Address (it is assigned during configuring the server for MN installation). 2 Hostname for the server is configured in the /etc/hosts file. 3 Resolver DNS servers are specified in the /etc/resolv.conf file in the format: nameserver RESOLVER_DNS_SERVER_IP_ADDRESS RESOLVER_DNS_SERVER_IP_ADDRESS - is an IP address of resolver DNS server. If you have several DNS server, specify all of them in that file. It will look like: nameserver RESOLVER_DNS_SERVER_IP_ADDRESS nameserver RESOLVER_DNS_SERVER_IP_ADDRESS nameserver RESOLVER_DNS_SERVER_IP_ADDRESS Important: Hostname of the MN must explicitly contain the "dot" symbol. For example, host.com. If you are installing POA on VPS, you need Parallels Virtuozzo Containers 3.0/4.0 or higher with the required OS Template installed. For the Parallels Virtuozzo Containers installation instructions, refer to the Parallels Virtuozzo Containers Installation guide. If you install RHEL5 or CentOS5 on the Management Node, you should disable the SELinux service on it (by default, this service is enabled). To do it, perform the following actions: 1 Log on to this Hardware Node with root privileges. 2 Open the file /etc/sysconfig/selinux and set SELINUX=disabled. 3 Reboot the Node.

11 Installing Linux-based POA Management Node 11 Creating and Configuring VPS (for POA on VPS) Note: If you are installing POA MN on a physical server, please skip this instruction. 1 Deliver POA_DISTRIB/doc/VZconfigs/ve-managementnode.conf-sample file into the /root/ directory of the VPS Hardware Node where MN VPS will be created. 2 Log in to VPS Hardware Node via SSH under root user's credentials. 3 Copy the file ve-managementnode.conf-sample into the directory /etc/sysconfig/vz-scripts: # cp /root/ve-managementnode.conf-sample /etc/sysconfig/vz-scripts/ 4 Create a VPS: If EZ Template is used: # vzctl create <MN_VPS_ID> --ostemplate <template_name> --config managementnode If Standard Template is used: # vzctl create <MN_VPS_ID> --pkgset <template_name>/<template_version> --config managementnode where: <MN_VPS_ID> is the unique numeric identifier of the MN VPS. You can enter any number from 2 to 99. <template_name> is the name of Parallels Virtuozzo Containers OS Template. <template_version> is the version of Parallels Virtuozzo Containers OS Template. 5 Start the created VPS: vzctl start <MN_VPS_ID> 6 Add an IP address to the VPS: # vzctl set <MN_VPS_ID> --save -ipadd <IP address> where <IP address> is the internal IP address to be used for MN VPS. 7 Add a hostname to the VPS: # vzctl set <MN_VPS_ID> --save -hostname <hostname> where <hostname> is the name of the MN host. Note: You need to use a FQDN for the hostname of the VPS MN. For example, "mn.host.com". 8 Set the DNS server for the VPS: # vzctl set <MN_VPS_ID> --save -nameserver <dns server> where <dns server> is the IP address of the DNS server you are going to use for the system. 9 Add the root user and set the access password:

12 12 Parallels Operations Automation 2.9 Parallels # vzctl set <MN_VPS_ID> --save --userpasswd root:<passwd> where <passwd> is the root password for accessing VPS. 10 Deliver POA distribution into the /root directory of MN VPS. Note: If the ability to reboot the Management Node from PCP is required, the VPS Hardware Node should be configured according to the instructions of Parallels Virtuozzo Containers for Linux User's Guide, Advanced Tasks > Rebooting Container. Installing POA Management Node 1 Deliver POA distribution into the /root/ directory of the Hardware Node where MN will be created. 2 Go to the directory where the POA distribution package is located. 3 Run the following command:./install The first Wizard screen appears. Click Yes to continue. Figure 1: POA Management Node Installation Wizard 1 4 You are be offered to read the License agreement: Figure 2: POA Management Node Installation Wizard 2

13 Installing Linux-based POA Management Node 13 Click OK. The License agreement will be displayed. 5 Read the offered License agreement. You can use PageUp and PageDown keys to browse through the document. When you are done with reading, press ENTER to continue. 6 At the next screen select Yes and click ENTER if you agree to the terms of the license. 7 Specify certain information to properly configure the POA Management Node. The parameters are displayed in the form of a menu. To enter a specific piece of information, select the number of the parameter in the list and press ENTER. Use TAB to move around the fields. You will be prompted to enter or choose the appropriate value. Note: Certain parameters already contain information by default. Although all parameters can be modified, you are strongly advised to use the default settings where available. FQDN of target host - MN hostname is placed by default. Important: MN hostname must explicitly contain the "dot" symbol (for example, host.com). Internal network interface - The system will offer you the list of currently available network interfaces. Select the BackNet interface and the BackNet IP address. These interface and IP address will be used to communicate with POA components/agents installed on other hosts. External network interface - Enter the network interface with BackNet IP address, BackNet IP address and mask parameter of where the POA services will be installed. For example, eth0 address= netmask= Path to license file - Shows the path to the POA license file (by default, <POA_DIST>/util/default.license). Administrator UI login - You will have to use this name for the first login to POA UI. Administrator UI password - This password will be used for the first login to POA UI. Administrator address - Enter the address, which will be used for sending system notifications. SMTP server address - Enter the name of the server to be used for sending notification messages. In case if you don't have the configured mail server yet, indicate the local IP address here: the notification mails would go to the root user. From field for notifications - Type in the text to be displayed in the 'FROM' field in the messages the system sends. System DB hostname - By default, the MN hostname is offered. This database server will be used for storing all POA internal data. System DB port - The port to access POA System DB. When all the necessary information is provided, highlight the Finished item and press OK to confirm the provided data and continue.

14 14 Parallels Operations Automation 2.9 Parallels 8 At the next step define the hosting type you wish to provide inside POA. The packages associated with them will be installed. You can choose All components option, if you need to install all the listed components. In this case, you don't need to select items in the list one by one. Figure 3: POA Management Node Installation Wizard 3 Click OK to start the installation. Note: If some RPMs are missing, the message will appear to inform you about the missing RPMs. You need to install the missing RPMs, and then pass the Wizard once again up to the current step. This time, you will have only to click OK on the Wizard pages, as all the parameters will have the values you specified at the first attempt to pass the Wizard. 9 When the installation completes, you will see the congratulation note stating that the installation has finished successfully. Click OK.

15 Installing Linux-based POA Management Node 15 Now you can log in to POA user interface. First Login to POA POA Control Panel opens only after you log in to it using your credentials. If this is your first login after the Management Node installation, perform the following steps: 1 Open your browser. 2 In the Address field, input the URL like: where backnet_ip is a proper BackNet IP address. 3 When the login screen appears, type your username and password into the corresponding fields. If POA is provided with the language packs, the Language field is available where you can select the language you wish the text in POA Control Panel to be displayed in. Figure 4: Login to POA 4 Click on the Login button. POA Contol Panel will open.

16 16 Parallels Operations Automation 2.9 Parallels Installing License Key In POA, a license is a file that contains information on resource limits and their expiration periods, which affect POA functionality usage. By default, the trial license is used, which is installed from the POA distribution package automatically. To obtain the real license, you must send the request to the vendor. It is possible to add several licenses which are differentiated by the restrictions to the POA functionality they define. Note: All the licenses are created for the particular POA installation and are not valid for the others except for the trial licenses they are valid for any POA installation, though they are very limited. 1 If you have installed Parallels Operations Automation on VPS, your request needs to include the Hardware ID - the unique identifier of the VPS Hardware Node where MN VPS is located. To obtain the Hardware ID, do the following: Note: Physical Hardware Node does not require the Hardware ID. For the Linux-based MN VPS: 1. Log in to the MN VPS via SSH as the root user. 2. Execute the following command: # cat /proc/vz/hwid For the Windows-based MN VPS: 1. Log in to the VPS Hardware Node where MN VPS is located via RDP as the Administrator user. 2. Go to Start > Run, type the cmd in the Open field and click on the OK button. The Command Prompt window opens. 3. Execute the following command: # vzkeygen You will receive the string like: D5BF.E590.E547.B87E.FDDC.50BD C9F Note: This ID will be used to generate the license that will be valid exceptionally for the configuration of the actual MN VPS. Thus, if you decide to migrate your MN to some other physical server or make a hardware upgrade of the existing one in the future, POA might not run. To avoid such situation, you are strongly recommended to notify your vendor in advance about the planned hardware upgrade or replacement. 1 In POA, go to Top > System Director > License Manager. You will see the page containing active license information and the list of available licenses (if there are any). 2 Click on the Upload license button.

17 Installing Linux-based POA Management Node 17 3 Into the Local path field, input the local path to the license file, or use the Browse button to show the way to the license key at local computer. 4 Click on the Submit button. The new license will be shown in the list and become available for activation. 5 Click on the just added license in the list. You will be taken into the license information page, where you will see the following information: ID license unique number. Status license current condition (Active, Not active, Invalid). Description general license overview. Signature string that identifies this particular license. Product name name of POA. Product version version of POA. Company name vendor of POA. Resource Limits - table form that shows the availability expiration dates and the amount of resource units provided by a license. If the license is not active, you will see the Activate button. 6 Click on the Activate button. The license key will be immediately replaced with the new key you have activated. Now, the functionality provided by the system as well as proper limitations will be set according to the properties defined by the new license key. Note: You can delete any license in the list simply by checking it in the corresponding checkbox and clicking the Delete button. However, you cannot delete the active license, but replace it with another one from the current list of licenses. In the list of licenses, there can be only one active license; the rest are considered inactive.

18 C H A P T E R 3 Deploying POA Management Node in Virtuozzo Failover Cluster In This Chapter Deploying Linux-based POA Management Node in Virtuozzo Failover Cluster. 19

19 Deploying POA Management Node in Virtuozzo Failover Cluster 19 Deploying Linux-based POA Management Node in Virtuozzo Failover Cluster Description POA Management Node can be deployed in cluster configuration with the use of Virtuozzo Failover Cluster. Such cluster configuration provides High Availability for POA Management Node and represents the following: Two hosts (or cluster node) are combined in a cluster with the use of the Red Hat Cluster Suite. Both hosts are attached to a shared storage (SAN). This shared storage is intended to store PVC data, such as OS/Application Templates, VPSs' private areas, VPSs' backups. PVC for Linux 4.0 is installed on both hosts. Management Node VPS is created and Management Node is installed. Shared storage, IP Address for PVC management, and the vz service are represented as cluster resources. One cluster node (active cluster node) owns appropriate cluster resources. It means that on the active cluster node shared storage is mounted, IP Address for PVC Management is configured, the vz service is active, Management Node VPS is started. Another cluster node is a standby cluster node (or passive cluster node). If one cluster node fails by certain reason, for example, due to hardware failure, it will be fenced and another cluster node will become an owner of cluster resources. Deployment Scheme

20 20 Parallels Operations Automation 2.9 Parallels Figure 5: Failover Cluster Deployment Scheme for Linux Network Interfaces and IP Addresses It is required to configure Network Interface Cards (NICs) and IP Addresses on the cluster nodes in the following way: First cluster node BackNet NIC Cluster Node BackNet IP Address SAN Connectivity NIC (optional) SAN Connectivity Network IP Address Second cluster node BackNet NIC Cluster Node BackNet IP Address SAN Connectivity NIC (optional) SAN Connectivity Network IP Address BackNet NICs and Cluster Node BackNet IP Addresses are used for the following purposes: Accessing cluster node via SSH. Cluster services communication.

21 Deploying POA Management Node in Virtuozzo Failover Cluster 21 SAN Connectivity NICs and SAN Connectivity Network IP Addresses are used for access to shared storage via SAN Connectivity Network from cluster nodes. This network is optional, the BackNet network can be used for access to shared storage (shared storage should be available in the BackNet network in this case). But, it is recommended to use a separate network for access to shared storage in order to separate traffic between shared storage and cluster nodes, and minimize the load on the BackNet network. Additionally, the following BackNet IP Addresses should be prepared: PVC Management IP Address - this IP Address is used for PVC management purposes. Management Node VPS IP Address - this IP Address is used by Management Node VPS. Hardware Requirements Both cluster nodes should meet the following hardware requirements: Server Names Description Density LINMNCL01, LINMNCL02 Virtuozzo Failover Cluster Node. It runs POA Management Node VPS. 50,000 accounts Quantity 2 OS RHEL 5 (x86 or x64) Software Supported Virtualization CentOS 5 (x86 or x64) To be installed by the Customer: OS Parallels Virtuozzo Containers (PVC) 4.0 for Linux CPU RAM 2 core (3GHz or higher) 4GB Disks Array 1: OS and software - 2 x 36, SCSI RAID 1 Array 2: PVC data - SAN, 3 x 72GB Disk Partitioning Array 1:

22 22 Parallels Operations Automation 2.9 Parallels / - remaining space - for OS and software 2 x RAM size (8GB) - swap NICs Array 2: /vz (mount point) - for PVC data BackNet SAN Connectivity (optional) Deploying Virtuozzo Failover Cluster Two-nodes Virtuozzo Failover Cluster should be deployed. Instructions are provided in the Deploying RHCS Clusters in Virtuozzo-Based Systems document, in the Deploying Virtuozzo Failover Cluster section. Note: It is recommended to use the Conga web-based cluster management interface to build a cluster. It does not require the X Window System installed on the cluster nodes. Installing POA Management Node Create the Management Node VPS and install the Management Node. Instructions on how to do this are provided in the Installing Linux-based POA Management Node (on page 8) section.

23 C H A P T E R 4 Deploying Native Repositories This section describes on how to deploy the System and External Native Repositories. In This Chapter Description Deploying System Native Repository Deploying External Native Repository Description Native Repository stores and indexes native packages (RPMs in our case) in such a way that the YUM (Yellow dog Updater, Modified) package manager can effectively and automatically update and install/remove these packages by resolving package dependencies. POA uses the Native Repositories to automatically install the required RPM packages on the Linux-based Hardware Node during the POA Packages installation. Thus, if it is planned to use the Linux-based Hardware Nodes for POA services installation, create the following Native Repositories for target OS: System Native Repository - It contains the POA-specific RPMs. To obtain the instructions on how to create a System Native Repository, refer to the Deploying System Native Repository section (on page 24). External Native Repository - It contains the standard RPMs, which are included to the OS distribution package. To obtain the instructions on how to create an External Native Repository, refer to the Deploying External Native Repository section (on page 25). Note: Native Repository deployment is not required if the Linux-based VPSs will be used for services installation.

24 24 Parallels Operations Automation 2.9 Parallels Deploying System Native Repository To create a System Native Repository, follow these instructions: 1 In POA CP, go to Top > Deployment Director > Applications Manager > Native repositories. 2 Click on the Add New Repository button. 3 Specify the repository general parameters: a Select the System option. b In the Repository Platform drop-down list, select the required platform. Click on the Next button. Figure 6: Selecting "System" Option 4 Select a host for a system repository by clicking on its name. 5 Click Finish. 6 Into the just created native repository, upload the RPMs from the os/<os name>/<os version>/rpms directory. To add a RPM package to the System Native Repository, follow these steps: 1 Obtain the RPM. RPMs that are shipped with POA distribution available by the following path: POA_DISTRIBUTION_DIRECTORY/os/OS_TYPE/OS_VERSION/RPMS/ where POA_DISTRIBUTION_DIRECTORY - Directory where POA distribution is located.

25 Deploying Native Repositories 25 OS_TYPE - Type of Operating System, for example: RHES. OS_VERSION - Version of Operating System. 2 In POA CP, go to Top > Deployment Director > Applications Manager > Native Repositories. The list of existing Native Repositories opens. Figure 7: IP Address of System Native Repository Host 3 Obtain the IP Address of the host where the target System Native Repository resides. 4 Deliver the RPM package to the host where the target System Native Repository resides to the POA_INSTALLATION_DIRECTORY/sysvhosts/ppmmirror/data/OS_TYPE/OS_V ERSION/YUM/ directory. Where: POA_INSTALLATION_DIRECTORY - Directory where POA is installed. Typically, POA_INSTALLATION_DIRECTORY is the /usr/local/pem/. OS_TYPE - Type of Operating System, for example: RHES. OS_VERSION - Version of Operating System. 5 In POA CP, go to Top > Deployment Director > Applications Manager > Native Repositories. The list of existing Native Repositories opens. 6 Select the checkbox opposite the target System Native Repository and click on the Reindex button. Pop-up window appears with the following text: "You are ready to perform reindex operation for selected repositories. Do you really want to proceed?". 7 Click on the OK button to proceed. The Status of the target System Native Repository becomes Needs reindex. When the Status of target the System Native Repository becomes Ready, repository is ready to use. Deploying External Native Repository To register an External Native Repository in POA, follow these instructions: 1 In POA CP, go to Top > Deployment Director > Applications Manager > Native repositories. 2 Click on the Add New Repository button. 3 Specify the repository general parameters:

26 26 Parallels Operations Automation 2.9 Parallels a Select the External option. b In the Repository Platform drop-down list, select the required platform. Figure 8: Selecting "External" Option Click on the Next button. 4 Specify the URL for the existing external repository. 5 Click Finish.

27 C H A P T E R 5 Deploying POA UI on Linux After the Management Node is installed, POA UI can be opened by entering the following URL into the address field of a browser: However, it is not recommended to run UI on Management Node. You should deploy UI on a separate, ready to provide server, deploy Branding Server, and create a Brand for the access to this UI Server. Everybody who opens POA Control Panel via the Brand will physically use the separate UI Server, not the Management Node. To deploy POA Control Panel using Linux-based servers, perform the following steps: 1 Create a separate, ready to provide UI Server. This server should be attached to BackNet only. 2 Create a Branding Server. This server is an Apache Web Server, which is attached to BackNet and FrontNet. It acts as proxy and delivers requests to UI Server. 3 Create Brand to access POA Control Panel. 4 Create certificate for the Brand. In This Chapter Creating UI Server...28 Creating Branding Server...32 Creating Brand...38 PBA Online Store Publishing Automation...44 Creating Certificate for Brand...48

28 28 Parallels Operations Automation 2.9 Parallels Creating UI Server Creating Attribute Create the attribute with the name ui node. For the instructions, refer to the Creating Attributes section (on page 60). Preparing Node for UI Server For POA UI server, you need a computer that meets the following requirements: Server Names Description Density LINUI POA UI Server on Linux. This server is responsible for running the POA user interface. Multiple UI servers can be used for scalability. Also it is possible to have a separate UI Server for each brand. 20,000 accounts Quantity 1 OS RHES 4 (x86) Software Supported Virtualization CentOS 4 (x86) RHEL 5 (x86 or x64) CentOS 5 (x86 or x64) To be installed by the Customer: OS only Parallels Virtuozzo Containers (PVC) 3.x/4.0 for Linux CPU RAM 2 core (3GHz or higher) 4GB Disks Array 1: Disk Partitioning Array 1: OS and software - 2 x 80GB, SATA, RAID 1 (software impl.) 2 x RAM size (8GB) - swap / - remaining space - for OS and software NICs BackNet

29 Deploying POA UI on Linux 29 You can install UI server on a Hardware Node, or on a VPS. For either case, refer to the corresponding topic below. Important! Firewall on the UI Server must allow TCP connections to port 8080 from Branding server. UI Server on Hardware Node 1 Register a Hardware Node that meets the above requirements. Please find instructions in the Registering Linux-Based Hardware Nodes section (see page 66). 2 Install the following RPM packages on the Hardware Node: For RHES 4 and CentOS 4: cronolog jre For RHEL 5 and CentOS 5: cronolog jre libxslt Refer to the Installing RPM Packages on Hardware Nodes section (on page 73). 3 Add the ui node attribute to the Hardware Node. Please find instructions in the Adding Attribute to Host section (see page 61).

30 30 Parallels Operations Automation 2.9 Parallels UI Server on VPS 1 Create the Resource Type based on the VPS Hardware nodes Resource Class: a In POA Control Panel, go to Top > Service Director > Provisioning Manager > Resource Types. b Click on the Add New Resource Type button. c In the list of Resource Classes, click VPS Hardware nodes. d Specify the name (for example, "VPS Hardware nodes") and description of the new Resource Type. Click Next to continue. e Specify the activation parameters for the Resource Type: Specify the number of dedicated VPSs by entering this number into the Number of Dedicated VPS field. Enter "5" into the Maximum of simultaneous migrations per Hardware Node field. f Click Next. Click Finish. 2 Create the Resource Type based on the Virtual Private Servers (Shared) Resource Class: a In POA Control Panel, go to Top > Service Director > Provisioning Manager > Resource Types. b Click on the Add New Resource Type button. c In the list of Resource Classes, click Virtual Private Servers (Shared). d Specify the name (for example, "UI VPS") and description of the new Resource Type. In the Platforms drop-down list, select the newest platform. Click Next. e f Note: If you have only one platform, the Platforms drop-down list will be unavailable. Select the required PVC Template type (EZ or Standard). Click Next. Specify OS Template for VPSs based on the Resource Type being created. Click Next to continue. g Specify network parameters for VPSs based on the Resource Type being created: Select IP Pools from which the IPs for VPSs will be taken. Type the IP address of the DNS server you are going to use for VPSs. Click Next to continue. h Select the following Application Templates:.pa-ui.pa-pleskd vzpem-ui For RHEL 5 and CentOS 5: For RHES 4 and CentOS 4:

31 Deploying POA UI on Linux 31 vzpem-pleskd i j k l Click Next to continue. In the Based on option group, select One of the VPS sample configurations. Click Next to continue. In the Sample configuration option group, select Basic. Click Next to continue. Specify CPU, Disk Quota, UBC parameters. Click Next to continue. In the list of available attributes, select ui node. Click Next to continue. m Click Finish. 3 Register the VPS Hardware Node in POA. Refer to the Registering Linux-based VPS Hardware Nodes section (on page 66). 4 Add the ui node attribute to the just registered VPS Hardware Node. Refer to the Adding Attribute to Host section (on page 61). 5 Create the VPS to be used as UI server. Refer to the Creating VPS section (on page 71). 6 Add the ui node attribute to the VPS. Refer to the Adding Attribute to Host section (on page 61). Installing POA Packages Install the following packages on the UI server: 1 em-gui (type: other). Several packages will be installed as the em-gui (type: other) package. 2 Install the skin packages that you want to use for the UI server brand. Refer to the Installing PPM Packages section (on page 73) for the step-by-step instructions. Marking UI Server as Ready to Provide If you plan to bind a brand to your UI server, you need to mark this server as ready to provide. 1 Click on the name of the (VPS) Hardware Node. The Summary tab opens. 2 Click the Mark as ready to provide link. As a result, the Marked as ready to provide indicator located on the left side of the General box becomes green saying Yes.

32 32 Parallels Operations Automation 2.9 Parallels Restarting Java on UI Server In order to have your new UI server working, restart Java: 1 Log on to the created UI server via SSH. 2 Execute the following command: # /etc/init.d/pemui stop # /etc/init.d/pemui start Creating Branding Server Creating Attribute Create the attribute with the name web. For the instructions, refer to the Creating Attributes section (on page 60). Preparing Node for Apache Web Server For Apache Web server, you need a computer that meets the following requirements: Server Names Description LINBR Branding Server on Linux. It hosts websites, which are used for branding purposes. Density 1 Quantity OS RHES 4 (x86) Software Supported Virtualization CentOS 4 (x86) RHEL 5 (x86 or x64) CentOS 5 (x86 or x64) To be installed by the Customer: OS only Parallels Virtuozzo Containers (PVC) 3.x/4.0 for Linux CPU RAM 2 core (3GHz or higher) 4GB Disks Array 1:

33 Deploying POA UI on Linux 33 Disk Partitioning Array 1: NICs OS and software - 3 x 146GB, SCSI, RAID 5 (hardware impl.) / 4GB - for OS 2 x RAM size (8GB) - swap /usr - remaining space - for software and data FrontNet, BackNet You can install Apache Web server on a Hardware Node, or on a VPS. For either case, refer to the corresponding topic below.

34 34 Parallels Operations Automation 2.9 Parallels Apache Web Server on Hardware Node 1 Register a Hardware Node that meets the above requirements. Refer to the Registering Linux-based Hardware Node section (on page 62). 2 Install the following RPM packages on the Hardware Node: mod_cband mod_frontpage mod_init_crypto mod_limitipconn pem-suexec perl-berkeleydb php4 php4-curl php4-domxml php4-gd php4-imap php4-ldap php4-mbstring php4-mcrypt php4-mhash php4-mysql php4-ncurses php4-odbc php4-pear php4-pear-http-request php4-pgsql php4-snmp php4-xmlrpc libc-client libmcrypt libmhash webalizer db1 MySQL4-client MySQL-shared-compat

35 Deploying POA UI on Linux 35 MySQL-python mx perl-dbd-mysql perl-dbd-pg postgresql-libs mod_ssl frontpage proftpd php5-cgi httpd vixie-cron perl curl Refer to the Installing RPM on Host section (on page 73). 3 Add the web attribute to the Hardware Node. Refer to the Adding Attribute to Host section (on page 61). 4 Mark the Hardware Node as ready to provide: a Click on the name of the Hardware Node. The Summary tab opens. b Click the Mark as ready to provide link. As a result, the Marked as ready to provide indicator located on the left side of the General box becomes green saying Yes.

36 36 Parallels Operations Automation 2.9 Parallels Apache Web Server on VPS 1 Create the Resource Type based on the Virtual Private Servers (Shared) Resource Class: a In POA Control Panel, go to Top > Service Director > Provisioning Manager > Resource Types. b Click on the Add New Resource Type button. c In the list of Resource Classes, click Virtual Private Servers (Shared). d Specify the name (for example, "Web VPS") and description of the new Resource Type. In the Platforms drop-down list, select the newest platform. Click Next. e f Note: If you have only one platform, the Platforms drop-down list will be unavailable. Select the required PVC Template type (EZ or Standard). Click Next. Specify OS Template for VPSs based on the Resource Type being created. Click Next to continue. g Specify network parameters for VPSs based on the Resource Type being created: Select IP Pools from which the IPs for VPSs will be taken. Type the IP address of the DNS server you are going to use for VPSs. Click Next to continue. h Select the following Application Templates:.mod_ssl.pa-apache-httpd.pa-frontpage.pa-mysql-client.pa-pgsql-client.pa-php.pa-php5-cgi.pa-proftpd.pa-webalizer mod_ssl For RHEL 5 and CentOS 5: For RHES 4 and CentOS 4: vzpem-apache-httpd vzpem-frontpage vzpem-mysql-client vzpem-pgsql-client vzpem-php

37 Deploying POA UI on Linux 37 vzpem-php5-cgi vzpem-proftpd vzpem-webalizer i j k l Click Next to continue. In the Based on option group, select One of the VPS sample configurations. Click Next to continue. In the Sample configuration option group, select Basic. Click Next to continue. Specify CPU, Disk Quota, UBC parameters. Click Next to continue. In the list of available attributes, select web. Click Next to continue. m Click Finish. 2 Register the VPS Hardware Node in POA. Refer to the Registering Linux-based VPS Hardware Nodes section (on page 66). 3 Add the web attribute to the just registered VPS Hardware Node. Refer to the Adding Attribute to Host section (on page 61). 4 Create the VPS to be used as Web server. Refer to the Creating VPS section (on page 71). 5 Mark the VPS Hardware Node as ready to provide: a Click on the name of the VPS Hardware Node. The Summary tab opens. b Click the Mark as ready to provide link. As a result, the Marked as ready to provide indicator located on the left side of the General box becomes green saying Yes.

38 38 Parallels Operations Automation 2.9 Parallels Installing POA Packages Refer to the Installing PPM Packages section (on page 73), install the following packages: 1 On the Management Node, install the apache (type: sc) service controller. 2 On the UI server, install the apache (type: cp) package. 3 On the Apache Web server, install the packages: webve (type: other) static_ui_content packages for skins Note: You need to install here the same skin packages as you installed on the UI server. Creating Brand You cannot build your own brands until: Brand-related POA packages (SC and CP) are installed on the POA MN and on the ready to provide UI servers. Appropriate Resource Types are created in POA. For details, see the Deploying Branding section (on page 50). Creating 'Physical Hosting (Apache)' Resource Type 1 In POA Control Panel, go to Top > Service Director > Provisioning Manager > Resource Types. 2 Click on the Add New Resource Type button. 3 Select the Physical Hosting (Apache) Resource Class. 4 Specify the Name and Description of the new Resource Type. Click Next to continue. 5 Specify the following activation parameters: Web prefix for Customer Domains. Specify the prefix to be used to create additional DNS records for the domains and subdomains of your Customers. Assign exclusive IP during provisioning (Yes:1, No:0). Set this activation parameter to 1 if you want the system to provision websites on exclusive IP addresses. Instant Access URL prefix template. Specify the prefix template for the instant access domain name. See the Instant Access URL Prefix Template topic (on page 40) for detailed information.

39 Deploying POA UI on Linux 39 Default Domain's Identifier. Specify the identifier of your domain that is used to build instant access domain names. Note: This identifier is used in case a webspace is created either through OpenAPI or through a non-branded CP only. If the webspace is created through a branded CP, the branded domain name is used. Web prefix for Provider Domains. Specify the prefix to be used to create additional DNS records for domains and subdomains. Web inodes usage hard limit. Enter the number of files a subscriber will be able to create. Web inodes usage soft limit. Enter the number of files a subscriber will be able to create before the overusage notification is sent. Web disk space usage hard limit. Enter the value of diskspace a subscriber will be able to use. Web disk space usage soft limit. Enter the value of diskspace a subscriber will be able to create before the overusage notification is sent. Limit of simultaneous requests per Virtual Host. Specify how many computers will be able to connect to the webspace simultaneously. Click Next to continue. 6 Select the web attribute. Click Next to continue. 7 Click on the Finish button.

40 40 Parallels Operations Automation 2.9 Parallels Instant Access URL Prefix Template The Instant Access URL prefix template consists of: Symbols: [0-9 A-Z a-z]. Every new Instant Access URL will begin with the symbols you put at the beginning of the prefix template. Properties: ${domain_name} or ${subscription_id}. The domain name may be subject to conversion, by specifying :suffix after the property name: ${domain_name:suffix}. If the domain name includes a specified suffix, the name will be used in Instant Access URL without this suffix. Special property ${unique}. It should be always included into a prefix template for the sake of prefix uniqueness. This property will expand into nothing for the first (autounique) prefix and into 1, -2, -3, and so forth for subsequent prefixes that are assigned to different home directories. Here are some examples of Instant Access URL prefix templates: ${domain_name}${unique}. For example, if the domain name is customer.domain.com, the Instant Access URL for the first Web hosting provisioned with the domain will be customer-domain-com, for the second - customer-domain-com-1, and so on (customer-domain-com-2, customer-domain-com-3, ). ${domain_name:.info}${unique}. For example, if the domain name is customer.domain.info, the Instant Access URL for the first Web hosting provisioned with the domain will be customer-domain, for the second Web hosting - customer-domain-1, and so on. d${subscription_id}${unique}. For example, Subscription identifier will expand into d for the first Web hosting provisioned by this Subscription, into d for the second Web hosting, and so on. Creating 'Branding Access Points' Resource Type 1 In POA Control Panel, go to Top > Service Director > Provisioning Manager > Resource Types. 2 Click on the Add New Resource Type button. 3 Select the Branding access points Resource Class. 4 Specify the Name and Description of the new Resource Type. Click Next to continue. 5 Select the ui node attribute. Click Next to continue. 6 Click Finish.

41 Deploying POA UI on Linux 41 Creating Website 1 In POA Control Panel, click the Hosting CP link. The POA Customer's Control Panel opens. 2 Go to Hosting > Configuration & Administration > Domain Overview > Domain Administration. 3 Start creating a new domain. For this purpose, click on one of the following buttons: Register New Domain Transfer Existing Domain Add existing domain registered elsewhere 4 Enter the general parameters for a new domain: Into the Domain field, type the name you wish to assign to your domain. Select the Zone management ability option if you want to get the ability of managing DNS zone for your domain. This includes the possibility to add and change zone records and tune zone time settings. In the Web Hosting area, select Website. In parentheses after Website, the web server type is indicated: Apache or Microsoft IIS. Click Next. 5 In the Webspace group box, select the Create new webspace option. Into the Location field, type the path to the directory on the Apache Web server where your website will be located. Click Next. 6 In the IP Address Type drop-down list, select Exclusive. Click to select the SSL support check box. Click Next. 7 Select resources for traffic and diskspace. Click Next. 8 Click Finish.

42 42 Parallels Operations Automation 2.9 Parallels Creating Brand 1 In POA Control Panel, go to Marketing Director > Branding Manager > Brands. 2 Click on the Add New Brand button to launch the Wizard for website branding. 3 Select the Existing domain option, and select the just created website from the Domain choice drop-down list. Click Next to continue. 4 Provide the necessary information as indicated below: In the Brand name field, type any name you find appropriate for distinguishing this brand among other brands. In the URL suffix field, type a suffix that will be added to your domain. For example, if you choose x for path suffix of your domain your access point to Control Panel will be Without the suffix, the domain and the access point to Control Panel will be inaccessible. This branded domain will be used for access to POA Control Panel. In the Skin drop-down list, select the skin you want to give to your website interface. Select the Upload skin for further customization check box if you wish to upload the skin to the branding website for manual editing. In the Custom Logo field provide the location of the logotype file that will be attached to your website. If you leave the field blank, the default logo will be used.

43 Deploying POA UI on Linux 43 Figure 9: Adding New Brand 5 After you have provided all the parameters, click on the Finish button.

44 44 Parallels Operations Automation 2.9 Parallels PBA Online Store Publishing Automation Parallels Business Automation (PBA) provides Online Store for Provider s and for Resellers Accounts. PBA Online Store is a web-based tool that allows you to sell hosting services online. Also, there is an ability for Providers and Resellers to have multiple Online Stores per an Account in PBA. Every Online Store can be fully customized to suit the needs of a store owner. Customization allows you to change the layout, style, colors, content, localization, and ordering process. Parallels Operations Automation (POA) integrated with PBA allows you to enable an access to the PBA Online Store during the Brand creating/modifying in POA. You can create an access point, which will be used to access POA/PBA Control Panels and PBA Online Store. For example, a Brand is created on the base of example-brand.com Domain. In this example, POA/PBA Control Panels are accessible through URL and PBA Online Store is accessible through URL. Note: PBA supports Online Store publishing automation starting from version. To enable an access to PBA Online Store during Brand creation, perform the following steps: 1 In POA Control Panel, go to Top > Marketing Director > Branding Manager > Brands. The list of existing Brands opens. 2 Click on the Add New Brand button. The Add New Brand wizard starts. 3 Pass through the Add New Brand wizard till the last step (process of Brand creating is described in the Provider's Guide > Marketing Operations > Branding in Parallels Operations Automation > Branding Domains Hosted in POA > Branding Website section). 4 Specify parameters in the Parameters area: a Fill out the URL suffix field. For example, if your Brand is based on the examplebrand.com Domain and the URL suffix is controlpanel, POA/PBA Control Panels are accessible via URL. b Select a skin and upload a Custom Logo, if required. 5 Select the Enable store checkbox in the Online store area. 6 There is the Store ID drop-down list. This list contains your existing PBA Online Stores. Select the required Online Store. Note: Your Account should has the Online Store(s) created, configured, and synchronized in PBA. To obtain instructions on how to manage PBA Online Stores, refer to the PBA Online Store guide, the Managing Online Store section.

45 Deploying POA UI on Linux 45 7 Fill out the Store URL suffix field. The value of this field is used to define the suffix of PBA Online Store access URL. For example, if your Brand is based on the examplebrand.com Domain and the Store URL suffix is onlinestore, the PBA Online Store is accessible via URL. 8 Click on the Finish button. Figure 10: PBA Online Store Parameters Note: You can update values of the Store ID and the Store URL suffix parameters by editing the Brand, if required. To enable an access to PBA Online Store for existing Brand, perform the following steps: 1 In POA Control Panel, go to Top > Marketing Director > Branding Manager > Brands. The list of existing Brands opens. 2 Click on the Brand. The General tab of the selected Brand appears.

46 46 Parallels Operations Automation 2.9 Parallels Figure 11: Brand - General Tab 3 Click on the Edit button. The General tab of the selected Brand appears in editing mode. 4 Select the Enable store checkbox in the Online store area. 5 There is the Store ID drop-down list. This list contains your existing PBA Online Stores. Select the required Online Store. Note: Your Account should has the Online Store(s) installed in PBA. To obtain instructions on how to manage PBA Online Stores, refer to the PBA Online Store guide, the Managing Online Store section. 6 Fill out the Store URL suffix field. The value of this field is used to define suffix of PBA Online Store access URL. For example, if your Brand is based on the examplebrand.com Domain and the Store URL suffix is onlinestore, the PBA Online Store is accessible via URL. 7 Click on the Finish button. Note: You can update values of the Store ID and the Store URL suffix parameters by editing the Brand, if required. You can disable an access to PBA Online Store for the Brand. To do this, perform the following steps:

47 Deploying POA UI on Linux 47 1 In POA Control Panel, go to Top > Marketing Director > Branding Manager > Brands. The list of existing Brands opens. 2 Click on the Brand. The General tab of the selected Brand appears. 3 Click on the Edit button. The General tab of the selected Brand appears in editing mode. 4 Clear the Enable store checkbox in the Online store area. 5 Click on the Finish button.

48 48 Parallels Operations Automation 2.9 Parallels Creating Certificate for Brand 1 In POA Control Panel, go to Top > Personal Info > Certificates. Click on the Self-signed link in the main window. 2 Click the Self-signed link in the Certificates area. 3 Fill out the following fields: Bits - Select the level of encryption of your SSL. Key type - For asynchronous encryption and signing, keys are needed. For generating your certificate you can choose between the RSA and DSA keys. Country - Select a country from the drop-down list. State/Province - Specify a state or a province. Location (City) - Specify a location (city). Organization name - Enter an appropriate organization name. Organization Unit name - Type an appropriate department/division of your organization. Domain name - Enter the branded domain name. This will be the only domain name to be used to access the Control Panel without receiving a certificate warning in the browser. - Specify your address. Valid from / Valid to - Define the period during which the self-signed certificate will be valid for using it. Store in user repository - RSA private keys and certificates are stored in the user repository automatically. You must clean the checkbox if you do not want to store them. Click on the Submit button. 4 On the displayed page you can see two different text sections: Certificate and Private Key. In the Certificate form you can see the certificate you have just generated. Click the Store button to immediately store the generated certificate to the repository, or the Download button to download the certificate to your local computer. In the Private Key form below the private key is displayed. Do not lose it. You will need this key during the certificate installation process. Losing it is likely to result in the need to generate another certificate. You can store the key to the repository immediately by clicking the Store button or download it to your local computer by clicking the Download button. Your self-signed certificate will be immediately generated and added to the repository. Note: The Store button is hidden if the Store in user repository option was checked during the private keys/certificates generating.

49 Deploying POA UI on Linux 49 5 After performing the corresponding operations, click OK. All your generated keys or obtained by a Certificate Authority certificates are stored in the user repository. When creating your self-signed certificate, you can store it immediately or add any certificate to the user repository later on by clicking the Store button.

50 C H A P T E R 6 Deploying Branding Branding is creating an immediately recognizable identity. It is intended to identify and distinguish the product or service from competing products or services. Studies have shown that the majority of e-commerce buyers make their purchase decisions based on recognizing a familiar brand. Brand is the symbolic embodiment of all the information connected with a company, product or service. A brand typically includes a name, logo, and other visual elements such as images, fonts, color schemes, or symbols. In POA, both providers and resellers can create their own brands. Furthermore, resellers can hide all provider's addresses or use their domains instead of provider's domains in paths to services. To enable the branding functionality, install the following POA packages: BrandingManager (type: sc) - on the POA Management Node. branding (type: cp) - on the ready to provide UI server. Refer to Installing PPM Packages (on page 73) to know how to install packages. Now, you are ready to perform the follow-up operations: creating Resource Type, providing resellers with branding, creating brands. See details in the POA Provider's Guide, in Marketing Operations > Branding in POA > Creating Service Template for Branding.

51 C H A P T E R 7 Deploying Linux-based DNS Servers The main purpose of a Domain Name System (DNS) server is to translate domain names to IP addresses, and vice versa. A DNS server is also used to determine the mail server for a given domain name. Of course, you can use an external DNS server. But if you want a DNS server to be managed via POA, you need to install your own DNS server. This section explains how to deploy DNS hosting on a Linux server, and to provide it with POA support. It is strongly recommended that DNS servers be placed on different Hardware Nodes inside VPSs. You need at least two DNS servers each one installed on a computer that meets the following requirements: Server Names Description Density LINDNS01, LINDNS02 DNS Server on Linux 60,000 DNS zones / 300,000 DNS resource records per server Quantity OS RHES 4 (x86) Software Supported Virtualization Minimum 2 are required. Can be deployed as a VPS on one of the Multi-Purpose servers - see below. CentOS 4 (x86) RHEL 5 (x86 or x64) CentOS 5 (x86 or x64) To be installed by the Customer: OS only Parallels Virtuozzo Containers (PVC) 3.x/4.0 for Linux CPU RAM 2 core (3GHz or higher) 2GB Disks Array 1: OS and software - 2 x 36GB, SCSI, RAID 1 Disk Partitioning Array 1: / - 4GB - for OS and software 2 x RAM size (4GB) - swap /var - remaining space - for DNS zone files NICs FrontNet, BackNet

52 52 Parallels Operations Automation 2.9 Parallels Note: You can deploy DNS server as a VPS on one of the Multi-Purpose servers. In This Chapter Installing DNS Server on VPS Installing DNS Server on Hardware Node... 54

53 Deploying Linux-based DNS Servers 53 Installing DNS Server on VPS 1 Create the attribute dns node. Refer to the Creating Attributes section (on page 60). 2 Create the Resource Type based on the VPS Hardware nodes Resource Class if it is not yet created. 3 Create the Resource Type based on the Virtual Private Servers (Shared) Resource Class: a In POA Control Panel, go to Top > Service Director > Provisioning Manager > Resource Types. b Click on the Add New Resource Type button. c In the list of Resource Classes, click Virtual Private Servers (Shared). d Specify the name (for example, DNS VPS) and description of the new Resource Type. In the Platforms drop-down list, select the newest platform. Click Next. e f Note: If you have only one platform, the Platforms drop-down list will be unavailable. Select the Standard template package type. Click Next. Specify OS Template for VPSs based on the Resource Type being created. Click Next to continue. g Specify network parameters for VPSs based on the Resource Type being created: Select IP Pool from which the FrontNet IPs for VPSs will be taken. Type the IP address of the DNS server you are going to use for VPSs. Click Next to continue. h Select the vzpem-pleskd-as4 Application Templates. Click Next to continue. i j k l In the Based on option group, select One of the VPS sample configurations. Click Next to continue. In the Sample configuration option group, select Basic. Click Next to continue. Specify CPU, Disk Quota, UBC parameters. Click Next to continue. In the list of available attributes, select dns node. Click Next to continue. m Click Finish. 4 Register the VPS Hardware Node in POA. Refer to the Registering Linux-based VPS Hardware Nodes section (on page 66). 5 Add the dns node attribute to the just registered VPS Hardware Node. Refer to the Adding Attribute to Host section (on page 61). 6 Create the VPS to be used as DNS Server. Refer to the Creating VPS section (on page 71). While creating the VPS, select DNS VPS as the Resource Type to base your DNS VPS on. 7 Install the package bind9 (type: service) on the DNS server VPS. Refer to the Installing PPM Packages section (on page 73).

54 54 Parallels Operations Automation 2.9 Parallels 8 Change DNS hosting type to make the system "know" that the domain is served by the POA name servers, not the external ones. a In POA, go to Top > Operations Director > Domain Manager > Domains. b Click on the name of the Provider's domain. c Move to the DNS Hosting tab and click Change DNS Hosting. d At the displayed page switch the radio-button to Internal name server and click Next. e Click Finish. Installing DNS Server on Hardware Node 1 Register a Hardware Node that meets the above requirements. Refer to the Registering Linux-based Hardware Node section (on page 62). 2 Install the package bind9 (type: service) on the Hardware Node. Refer to the Installing PPM Packages section (on page 73). Note: bind9 package requires the bind rpm installed on the Hardware Node.

55 C H A P T E R 8 Deploying Privacy Proxy Privacy Proxy service is responsible for transferring XMLRPC or HTTP(S) requests from the protected internal network (BackNet) to the external network (FrontNet). For example, from a VPS Hardware Node to Internet (in case of Templates updating), or from the Management Node to: Dedicated server Parallels Plesk Server Administrator Internet (in case of Templates upload) Privacy Proxy server is necessary for Plesk in VPS Hosting, and Dedicated Hosting. Privacy Proxy is also highly recommended for all other types of hosting where VPSs are used. You can install the Privacy Proxy service on any POA-registered host that has both BackNet and FrontNet network interfaces. You can also use a separate host specially designated for Privacy Proxy service. In This Chapter Hardware Requirements for Privacy Proxy Server on Linux Installing POA Packages Hardware Requirements for Privacy Proxy Server on Linux The Privacy Proxy Server host must satisfy the following system requirements: Server Names Description LINPPS Privacy Proxy Server on Linux Density Quantity 1 OS RHES 4 (x86) CentOS 4 (x86)

56 56 Parallels Operations Automation 2.9 Parallels Software Supported Virtualization CPU RAM To be installed by the Customer: OS only Parallels Virtuozzo Containers (PVC) 3.x/4.0 for Linux 1 core (2GHz or higher) 512MB Disks Array 1: Disk Partitioning Array 1: OS, software, and data - 40 GB, SATA 2 x RAM size (1GB) - swap / - remaining space - for OS, software, and data NICs FrontNet, BackNet Installing POA Packages To deploy the Privacy Proxy service, install the following packages: On the Management Node - PrivacyProxy (type: sc) On the Privacy Proxy Server - PrivacyProxy (type: service) Note: The privoxy RPM must be installed on the Linux-based Privacy Proxy Server. If you add a Hardware Node before the Privacy Proxy service is installed, this Hardware Node will connect directly to Internet if the external connection is required (for example, for Templates upload). Later, after you install the Privacy Proxy service, such connections will be executed via Privacy Proxy. After the Privacy Proxy service is installed, every new Hardware Node will be automatically configured to use Privacy Proxy for external connections.

57 C H A P T E R 9 Deploying Request Tracker This chapter provides the procedure of installing and registering Request Tracker service in POA. In This Chapter Installing Request Tracker Service Installing Request Tracker Service Request Tracker (hereafter RT) is an enterprise-grade ticketing system which enables a group of people to intelligently and efficiently manage tasks, issues, and requests submitted by a community of users. Written in object-oriented Perl, RT is a high-level, portable, platform independent system that eases collaboration within organizations and makes it easy for them to take care of their customers. To help service providers to speedily resolve technical issues submitted by their customers and keep track of the resolved issues for billing purposes, RT can be easily integrated into POA. Installation Requirements for Request Tracker Service System-wide Requirements Management Node UI Node(s) RequestTracker (SC) rt (CP)

58 58 Parallels Operations Automation 2.9 Parallels Note: SC should be installed on Management Node and CP should be installed on all UI Servers. After these requirements are satisfied, follow the instruction in the Request Tracker documentation to install it on the target host. The Request Tracker installation guides can be found at Remember that the host you intend to install RT to needs two network interfaces: internal and external. The internal IP will be used by the Management Node, the external IP - for the public access. When RT is properly installed, perform the steps at adjust permissions for RT users (on page 59) and register it in POA (on page 59). If the RT installation fails because of the error 404, it means the new RT version (rt-3.4) must not be yet uploaded by the RT producer. In this case, follow these steps: 1 Download the repository from x.repo. 2 Open the downloaded file and correct the text in the following way: [rt-3.0.x] name=rt 3.0.x, updates and extra perl module packages baseurl= gpgcheck=0... [root@webspace root]# cat rt-3.0.x.repo>>/etc/yum.conf [root@webspace root]# yum install rt rt-mail-dispatcher Configuring Request Tracking 1 Edit the /etc/rt/rt_siteconfig.pm file: Replace Set($WebBaseURL, " to Set($WebBaseURL, " 2 Since the RT requires two network interfaces (BackNet and FrontNet), you need to create two virtual hosts. # cd /etc/httpd/conf.d/ # cp rt.conf rt1.conf # vi rt.conf Replace your.ip.address by the BackNet IP of the RT VPS. Replace your.rt.server.hostname by the hostname of the RT VPS. 3 Execute the following command: # /usr/sbin/rt-setup-database --action init --dba root --prompt-fordba-password 4 Re-start HTTPD: # service httpd restart

59 Deploying Request Tracker 59 Adjusting Permissions for Request Tracker Users 1 In a browser, open the URL: 2 Enter the login and password you specified while installing the RT. 3 Go to Configuration > Global > Group Rights. 4 Grant to the Everyone group the following rights: Comment On Ticket Create Ticket Own Ticket Reply to Ticket See Queue Show Ticket Note: You may use CTRL button to grant several rights at once. Registering Request Tracker in POA 1 In POA Provider's Control Panel, go to Top > Marketing Director > Support Manager > Setup. 2 Click on the Edit button. 3 Enter the following RT URL: (FrontNet IP Address) 4 Enter RT Management URL: (BackNet IP Address). 5 Enter the appropriate administrator login and password. 6 Click on the Submit button.

60 C H A P T E R 10 Common Operations In This Chapter Creating Attributes Adding Attribute to Host Registering Linux-based Hardware Nodes Registering Linux-based VPS Hardware Nodes Creating VPS Installing RPM on Host Installing PPM Packages Creating Attributes The Attributes mechanism allows to link the resource to be provided and the Hardware Node/VPS/VPS Hardware Node, where this resource should be provisioned. An Attribute is a special label with which the Provider marks the resource (more precisely, Resource Type) to be provided. The same label is marked on the Hardware Node/VPS/VPS Hardware Node, where this resource should be provisioned on. To create an Attribute, follow these steps: 1 In Provider's Control Panel, go to Top > Service Director > Provisioning Manager > Attributes. 2 Click on the Add New Attribute button. 3 Enter values for the Attribute name and description. 4 Click on the Submit button.

61 Common Operations 61 Adding Attribute to Host To assign a Provisioning Attribute to the host, perform the following actions: 1 In POA Control Panel, go to the target host (path in Control Panel depends on type of host): Hardware Node: Top > Deployment Director > Server Manager > Hardware Nodes. VPS Hardware Node: Top > Service Director > Virtuozzo Manager > VPS Hardware Nodes. VPS: Top > Service Director > Virtuozzo Manager > VPSs. 2 Click on the host. The Summary tab opens. 3 Go to the General tab > Attributes subtab. 4 Click on the Assign button. The list of existing Attributes opens. 5 Select the required Attribute. 6 Click on the Submit button.

62 62 Parallels Operations Automation 2.9 Parallels Registering Linux-based Hardware Nodes This section describes how to register a Linux-based Hardware Node in POA. Prerequisites Before registering a Linux-based Hardware Node in POA, the following prerequisites should be satisfied: Operating System is installed. Credentials of the root user are available. The following network settings are configured on the Hardware Node: BackNet IP Address FrontNet IP Address (if required) Gateway DNS Server If the Hardware Node you are going to add to POA works under RHEL5 or CentOS5, disable the SELinux service on it (by default, this service is enabled). To do it, perform the following actions: 1. Log on to this Hardware Node with root privileges. 2. Open the file /etc/sysconfig/selinux and set SELINUX=disabled. 3. Reboot the Node. Creating 'Hardware Nodes' Resource Type To register Hardware Node in POA, the special Resource Type intended for Hardware Nodes registration should be created. Typically, one such Resource Type is enough for Linux-based Hardware Nodes registration purposes. 1 Go to Top > Service Director > Provisioning Manager > Resource Types. 2 Click on the Add New Resource Type button. The list of Resource Classes appears. 3 In the list of Resource Classes, click on Hardware nodes Resource Class. 4 Specify the name and description of the Resource Type. For example, use the Hardware Nodes name. Click Next twice. 5 Click Finish.

63 Common Operations 63 Creating 'Traffic' Resource Type To be able to register a Hardware Node in POA, the Traffic Resource Type must be created in the system. To create the Traffic Resource Type, follow the steps: Note: If the Traffic Resource Type is already created in POA, skip this operation. 1 Go to Top > Service Director > Provisioning Manager > Resource Types and click on the Add New Resource Type button. The list of existing Resource Classes opens. 2 In the list click on the Traffic Resource Class. The Add New Resource Type wizard starts. 3 Specify the general parameters (name and description) for the new Resource Type based on the Traffic Resource Class. Click Next twice. 4 Click on the Finish button.

64 64 Parallels Operations Automation 2.9 Parallels Obtaining Host Initial Data File 1 Go to Top > Deployment Director > Server Manager > Hardware Nodes. The list of registered Hardware Nodes appears. 2 Click on the Add New Host button. The Add New Host wizard starts. 3 Select the Unix host type and click on the Next button. The list of Resource Types based on Hardware nodes Resource Class appears. 4 Choose the Hardware Nodes Resource Type by clicking on it. The host initial data file screen appears. 5 Click on the Download button to download the host-initial-data file. You will be required to supply this file later, when registering the Hardware Node in the system. 6 Save the file under a desired name. 7 Upload the file onto the Hardware Node you wish to register in POA. Note: On the host initial data file screen, you are also offered the URL to host-initial-data file location. You can write down or just copy to clipboard the full path to the location where this file is stored. You can upload this file on Hardware Node with help of wget utility, for example: wget HOST_INITIAL_DATA_FILE_URL. Generating Hardware Node Distribution 1 Log on to the Hardware Node you are going to add with root privileges. 2 Copy POA distribution to the Hardware Node. 3 Go to the POA distribution directory. 4 Execute the following script: #./make_sn_dist -o Linux -O <OS version> -d <output directory> [-f] for example: #./make_sn_dist -o RHES -O 4 -d rhes4sn Note: The rhes4sn directory may already exist. Use the -f flag if you want the directory to be recreated in any case. Without the flag, the system will notify you that directory with such name already exists and another name is required. Installing POA Agent 1 Run the host installation script: # sh rhes4sn/install The Hardware Node Registering Wizard starts.

65 Common Operations 65 Figure 12: Registering Linux-based Hardware Node Wizard 2 You will be offered to supply certain information to register the Hardware Node. The parameters are displayed in the form of a menu. 3 To enter a specific piece of information, select parameter in the list and press ENTER. You will be prompted to enter or choose the appropriate value. Note: Certain parameters already contain information by default. Although all parameters can be modified, you are strongly advised to use the default settings where available. To confirm the default value, just click ENTER. a FQDN of target host. The system determines the hostname automatically. 1. Internal network interface. The system will offer you the list of currently available network interfaces. Select the one with the BackNet IP Address configured. This IP Address will be used to communicate with Management Node. For example, eth0 address= netmask= External network interface. The system will offer you the list of currently available network interfaces. Select the one with the FrontNet IP Address configured. This IP Address will be used by POA services installed on Hardware Node. For example, eth0 address= netmask= Note: In some cases a Hardware Node located in the BackNet is only required, for example, Hardware Node intended to store Customers' Backups. To register such Hardware Node, select the network interface having BackNet IP Address configured. b Administrator UI login. Enter login of Provider Account's Staff Member (typically it is admin). c Administrator UI password. Enter password of Provider Account's Staff Member. Note: This login and password will be used for the first login to POA user interface.

66 66 Parallels Operations Automation 2.9 Parallels d Host initial data file. Enter the path to the host-initial-data file that you obtained earlier. e When all the necessary information is provided, highlight the Finished item and click OK to confirm the provided data. POA Agent installation process starts. Just like POA Agent installation process is completed, Hardware Node is registered in POA. Registering Linux-based VPS Hardware Nodes This section describes how to register Linux-based VPS Hardware Node in POA. Prerequisites Before registering VPS Hardware Node in POA, the following prerequisites should be satisfied: Credentials of the root user is available. The following network settings are configured on the VPS Hardware Node: BackNet IP Address FrontNet IP Address Gateway DNS Server (resolver DNS Server, that is not managed by POA) VPS Hardware Node is accessible by its hostname from others VPS Hardware Nodes. VPS Hardware Node hostname is resolved to the VPS Hardware Node BackNet IP Address. It can be done by the following ways: DNS Record of the A type is created on the resolver DNS Server (DNS Server that is not managed by POA). Record is added to the hosts file and this file is distributed among all VPS Hardware Nodes. Format of the record is the following: VPS_HN_BACKNET_IP FQDN_VPS_HN_HOSTNAME VPS_HN_HOSTNAME Where: VPS_HN_BACKNET_IP - BackNet IP Address of the VPS Hardware Node. FQDN_VPS_HN_HOSTNAME - Fully qualified domain name of the VPS Hardware Node. VPS_HN_HOSTNAME - "Short" VPS Hardware Node hostname. For example: linvpshn01.hosting.local linvpshn01 Parallels Virtuozzo Containers (PVC) for Linux 4.xx is installed on the node according to instructions provided in the Parallels Virtuozzo Containers for Linux Installation Guide.

67 Common Operations 67 Valid PVC license is installed according to instructions provided in the Parallels Virtuozzo Containers for Linux User's Guide, Managing Hardware Nodes > Managing Virtuozzo Licenses section. PVC software is up to date. Instructions on how to update PVC software are provided in the Parallels Virtuozzo Containers for Linux User's Guide, Keeping Your Virtuozzo System Upto-Date section. Service Level Management (SLM) support is enabled on VPS Hardware Node (it is enabled by default on fresh PVC installation). To obtain instructions how to manage SLM support for VPS Hardware Node, refer to the Parallels Virtuozzo Containers for Linux User's Guide, Managing Resources > Managing System Parameters section. Note: For Virtuozzo 3.xx BackNet IP Address on Service VPS should be configured and credentials of the vzagent0 user should be available. Creating 'Traffic' Resource Type To be able to register VPS Hardware Node in POA, the Traffic Resource Type must be created in the system. To create the Traffic Resource Type, follow the steps: Note: If the Traffic Resource Type is already created in POA, skip this operation. 1 Go to Top > Service Director > Provisioning Manager > Resource Types and click on the Add New Resource Type button. The list of existing Resource Classes opens. 2 In the list click on the Traffic Resource Class. The Add New Resource Type wizard starts. 3 Specify the general parameters (name and description) for the new Resource Type based on the Traffic Resource Class. Click Next twice. 4 Click on the Finish button.

68 68 Creating 'VPS Hardware Nodes' Resource Type To register VPS Hardware Node in POA, the special Resource Type intended for VPS Hardware Nodes registration should be created. Typically, one such Resource Type is enough for VPS Hardware Nodes registration purposes. To create a new Resource Type for VPS Hardware Nodes registration, follow these steps: 1 In POA, go to Service Director > Provisioning Manager > Resource Types. 2 Click on the Add New Resource Type button. 3 In the list of the opened Resource Classes click on the VPS Hardware nodes Resource Class. 4 Enter general parameters for the new Resource Type: Name: for example, VPS Hardware Nodes. Description: for example, This Resource Type is used to register VPS Hardware Nodes intended for the provisioning of VPSs in POA. Click Next to continue. 5 Specify the following Activation Parameters: Number of VPS per HW node capacity. This Activation Parameter sets default value for VPS Number per HW node Capacity of VPS Hardware Node. Note: VPS Number per HW node Capacity limits maximum amount of VPSs, which are allowed to provision on VPS Hardware Node. This Capacity can be changed in the following way: Top > Service Director > Virtuozzo Manager > VPS Hardware Nodes > VPS_HARDWARE_NODE > General tab > Capacities. Maximum number of simultaneous migrations per Hardware Node. This Activation Parameter sets default value for Maximum of simultaneous VPS migrations Capacity of VPS Hardware Node. Note: Maximum of simultaneous VPS migrations Capacity limits amount of simultaneous VPSs migrations from/to VPS Hardware Node. This Capacity can be changed in the following way: Top > Service Director > Virtuozzo Manager > Setup > Migration Settings tab. 6 Click Next to continue. 7 Check values entered on previous steps and click Finish.

69 Common Operations 69 Creating 'Shared VPSs BackNet IPs' IP Pool This section describes how to create Shared VPSs BackNet IP Pool. This IP Pool will be attached and will be bound to VPS Hardware Node during its registration in POA. Shared VPSs 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 Management Node. Note: The number of IP Addresses of this IP Pool should be not less than the total number of Shared VPSs (both Linux-based and Windows-based). To create Shared VPSs BackNet IP Pool, follow these steps: 1 Go to Top > Operations Director > IP Manager > IP Pools. 2 Click on the Add New IP Pool button. 3 Specify the following parameters: Name - name of this IP Pool, for example: Shared VPSs BackNet IPs. Initial IP - lower bound IP Address. Final IP - upper bound IP Address. Netmask - netmask of the IP Pool subnet. Gateway - default gateway of the IP Pool subnet. Specify the Pool available for parameter, select the Everyone value. 4 Specify the purpose of IP Pool, select the Infrastructure configuration checkbox in the Purpose area. 5 Click on the Submit button. The newly created IP Pool will be immediately added to the IP Pools list.

70 70 Parallels Operations Automation 2.9 Parallels Synchronizing VPS Hardware Node with World Time Synchronize the world time and the VPS Hardware Node you are going to add to POA: 1 Log on to the VPS Hardware Node by SSH. 2 Ensure that NTP is installed. For this purpose, perform the following command: rpm -qa grep ntp- Install if necessary. 3 Perform the following synchronization commands: echo "server time.nist.gov" > /etc/ntp.conf chkconfig --level 2345 ntpd on service ntpd stop ntpdate time.nist.gov service ntpd start

71 Common Operations 71 Registering VPS Hardware Node in POA 1 In POA, go to Top > Service Director > Virtuozzo Manager > VPS Hardware Nodes. The list of already added VPS Hardware Nodes is displayed. 2 Click on the Register New VPS Hardware Node button. 3 Select the VPS Hardware Nodes Resource Type. Note: The Traffic Resource Type must be created in the system in order to be able to register VPS Hardware Node in POA. 4 Click Next to continue. Note: If you have only one available VPS Hardware Nodes like Resource Type, it is chosen automatically. In this case this step is omitted. 5 Fill out the following fields: Address - enter the BackNet IP Address of the VPS Hardware Node. Username - enter the root value to this field. Password - enter the password of the root user. Backnet IP Pool - using drop-down box, select the Shared VPSs BackNet IPs IP Pool. Note: To register PVC having version lower than 4.xx (e.g. 3.xx), enter BackNet IP Address of the Service VPS to the Address field, enter vzagent0 value to the Username field, enter password of the vzagent0 user to the Password field. Click Next to continue. 6 Check if the information entered is correct. If all is OK, click Finish. The list of the VPS Hardware Nodes registered in the system reopens with the new VPS Hardware Node in it. Status of the new VPS Hardware Node is Registering. VPS Hardware Node registration process takes time. During this time period POA collects the necessary information about VPS Hardware Node, such as Virtuozzo Version, amount of existing VPSs, whether Service Level Management (SLM) support is enabled. When all the necessary information is collected, VPS Hardware Node Status becomes Running. After that, VPS Hardware Node can be managed from POA. Note: If Status of VPS Hardware Node is Registration failed, you can find the reason of problem in Task Manager by checking logs of register HW Node with Agent IP IP_ADDRESS task. Task Manager is available by the following path: Top > System Director > Task Manager > Background Tasks. After that problem is fixed, this task can be restarted to proceed the process of registration. Creating VPS 1 In POA, go to Top > Service Director > Virtuozzo Manager > VPSs.

72 72 Parallels Operations Automation 2.9 Parallels 2 Click on the Add New VPS button to start the Wizard. 3 Select the Resource Type to base your VPS on. Click Next. 4 Choose the way you wish the new VPS will be named: Generate hostname automatically - Enable the system to generate the random name for the VPS that will be resolved to the external domain. Generate hostname based on the existing domain - Enable the system to generate the random name for the VPS that will be resolved to the POA domain. Specify hostname based on the existing domain - Enter the desired hostname for the VPS that will be accessible on the POA domain. Custom hostname - Enter the desired hostname for the VPS that will be resolved to the external domain. 5 Set the desired access password to the VPS. Click Next. 6 Click Finish to schedule the VPS for creation.

73 Common Operations 73 Installing RPM on Host This section describes how to install a RPM on host. 1 Deliver the RPM file to the target host. RPMs that are shipped with POA distribution available by the following path: POA_DISTRIBUTION_DIRECTORY/os/OS_TYPE/OS_VERSION/RPMS/ where POA_DISTRIBUTION_DIRECTORY - Directory where POA distribution is located. OS_TYPE - Type of Operating System, for example: RHES. OS_VERSION - Version of an Operating System (OS). Other required RPMs can be obtained from the OS distribution. 2 Log in to the target host via SSH under the root user's credentials. 3 Execute the command: rpm -ihv RPM_FILE_NAME where RPM_FILE_NAME is the name of the RPM file. For example: rpm -ihv mc i386.rpm Installing PPM Packages This section describes the following operations: Adding a Package Manifest to the Packages Repository. Adding a Package Tarball to the Packages Repository Mirror. Installing a Package on the host.

74 74 Parallels Operations Automation 2.9 Parallels Adding a Package Prior to installing a Package on the host, the following actions should be performed: 1 A Package Manifest should be added to the Packages Repository. 2 A Package Tarball should be placed to the Packages Repository Mirror. Note: Typically, a Package has a Manifest (file having pdl.asc extension) and a Tarball (file having tgz extension). But, in some cases, a Package has a Manifest only. OS specific Packages Manifests and Packages Tarballs are available by the following location: POA_DISTRIBUTION_DIRECTORY/os/OS_TYPE/OS_VERSION/packages/ where: POA_DISTRIBUTION_DIRECTORY - Directory where POA distribution is located. OS_TYPE - Type of Operating System, for example: Win32, RHES. OS_VERSION - Version of Operating System. Common Packages Manifests and Packages Tarballs are available by the following location: POA_DISTRIBUTION_DIRECTORY/common/ Adding a Package Manifest to the Packages Repository There are the following options available how to add Package Manifest to the Packages Repository: Adding Package Manifest from local workstation. To do this, perform the following steps: 1. Deliver Package Manifest from POA distribution to the local workstation. 2. In POA Control Panel, go to Top > Deployment Director > Applications Manager > Packages Repository. The Packages tab opens.

75 Common Operations 75 Figure 13: Packages Repository - Packages List Screen 3. Click on the Add new package button. The input box appears prompting you for the name of the file. Figure 14: Packages Repository - Add New Package Screen 4. Enter the absolute path to the Package Manifest into the provided File text input field. You can also use the Browse... button to find the desired Package Manifest by means of the standard dialog window. 5. Click on the Submit button to import the selected Package Manifest into the Package Repository. Note: To check that Package Manifest is added to the Package Repository, the following options are available: 1. Go to Top > Deployment Director > Applications Manager > Packages Repository, switch to the Packages tab, and check that Package is present in the list of Packages. 2. Use the Notification system. Notification system is described in the POA Provider's Guide, Monitoring System > Managing Notifications section. Adding Package Manifest by specifying the Package Manifest location URL. To do this, perform the following steps: 1. Deliver Package Manifest to the Web or FTP server. 2. In POA Control Panel, go to Top > Deployment Director > Applications Manager > Packages Repository. The Packages tab opens.

76 76 Parallels Operations Automation 2.9 Parallels Figure 15: Packages Repository - Packages List Screen 3. Click on the Add new package from URL button. Figure 16: Packages Repository - Add New Package from URL Screen 4. Enter the URL address of the Package Manifest into the provided URL text input field. 5. Click on the Submit button to import the selected Package Manifest into the Package Repository. Note: To check that Package Manifest is added to the Package Repository, the following options are available: 1. Go to Top > Deployment Director > Applications Manager > Packages Repository, switch to the Packages tab, and check that Package is present in the list of Packages. 2. Use the Notification system. Notification system is described in the POA Provider's Guide, Monitoring System > Managing Notifications section. Adding a Package Tarball to the Packages Repository Mirror / Initial POA Tarballs Storage

77 Common Operations 77 Linux-based Management Node. In this case Packages Repository Mirror is located on the Management Node itself. Obtain Package Tarball and deliver it to the Management Node to the POA_INSTALLATION_DIRECTORY/sysvhosts/ppmmirror/data directory. Typically, POA_INSTALLATION_DIRECTORY is /usr/local/pem/. Windows-based Management Node. In this case Initial POA Tarballs Storage is located on the Management Node itself. Obtain Package Tarball and deliver it to the Management Node to the POA_INSTALLATION_DIRECTORY\install\tarballs directory. Typically, POA_INSTALLATION_DIRECTORY is C:\Program Files\SWsoft\PEM\.

78 78 Parallels Operations Automation 2.9 Parallels Installing a Package on the Host This section describes the following operations: Installing a package on the host. Use this operation to install one package on one host. For example, to install a Service Controller on the Management Node. Installing a set of packages on the group of hosts. Use this operation to install a set of packages on the group of hosts. For example, to install a Control Panels on several UI Servers. Installing a Package on the Host To install a package on the host, perform the following steps: 1 In POA Control Panel, go to the target host (path in Control Panel depends on type of host): Hardware Node: Top > Deployment Director > Server Manager > Hardware Nodes. VPS: Top > Service Director > Virtuozzo Manager > VPSs. 2 Select the host you wish to install the package on by clicking on it. The Summary tab opens. 3 Click on the Packages tab. The list of installed packages appears. Figure 17: Installing Package - List of Installed Packages 4 Click on the Install Package button. You will be offered the list of available components, not yet installed.

79 Common Operations 79 Figure 18: Installing Package - List of Available Components 5 Select the package you'd like to install and click on appropriate Install package icon in the Actions column. The list of components that should be installed on the host is displayed. Figure 19: Installing Package - List of Components That Should Be Installed There are the following types of packages: Package has no editable properties. In this case the following icon is displayed in the Actions column:

80 80 Parallels Operations Automation 2.9 Parallels Package has editable properties. Properties have default values and can be customized. In this case the following icon is displayed in the Actions column: Package has editable properties. Properties have no default values and should be defined prior to package installation. In this case the following icon is displayed in the Actions column: 6 Click on or icon and specify package's properties. Click on the Submit button. Figure 20: Installing Package - Edit Package Properties Screen Note: This step is performed if a package has editable properties or properties that are mandatory to fill out. 7 Click the Finish button to install the package. Note: To check that a package is installed on the host, the following options are available: 1. Select the target host, switch to the Packages tab, and check that package is available in the list of installed packages. 2. Use the Notification system. Notification system is described in the POA Provider's Guide, Monitoring System > Managing Notifications section. Installing Set of Packages on Group of Hosts To install a set of packages on the group of hosts, perform the following actions: 1 Fill out the mandatory properties of packages you wish to install. To do that, execute the following steps: a In POA Control Panel, go to Top > Deployment Director > Applications Manager > Packages Repository. b Select the target package and click on c icon in the Actions area. Fill out mandatory package properties and click on the Submit button. Important! Execute these steps for every package which participates in the installing operation and has mandatory properties. 2 In POA Control Panel, go to Top > Deployment Director > Applications Manager > PPM group operations.

81 Common Operations 81 3 Click on the Create new PPM group operation link. The Create PPM group operation wizard starts. 4 Select the Installation option in the Operation area and click on the Next button to continue. Figure 21: PPM Group Operations Wizard - Select Operation Type Screen 5 Select target hosts and click on the Next button to continue. Figure 22: PPM Group Operations Wizard - Select Target Hosts Screen 6 Select packages to install and click on the Next button to continue. Figure 23: PPM Group Operations Wizard - Select Packages Screen

How To Back Up Your Pplsk Data On A Pc Or Mac Or Mac With A Backup Utility (For A Premium) On A Computer Or Mac (For Free) On Your Pc Or Ipad Or Mac On A Mac Or Pc Or

How To Back Up Your Pplsk Data On A Pc Or Mac Or Mac With A Backup Utility (For A Premium) On A Computer Or Mac (For Free) On Your Pc Or Ipad Or Mac On A Mac Or Pc Or Parallels Plesk Control Panel Copyright Notice ISBN: N/A Parallels 660 SW 39 th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 1999-2008, Parallels,

More information

Parallels Operations Automation 5.5

Parallels Operations Automation 5.5 Parallels Operations Automation 5.5 Privileges Reference Revision 6.52 (October 28, 2013) 1999-2013 Copyright 1999-2013 Parallels IP Holdings GmbH and its affiliates. All rights reserved. Parallels IP

More information

Legal and Copyright Notice

Legal and Copyright Notice Parallels Helm Legal and Copyright Notice ISBN: N/A Parallels 660 SW 39 th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 2008, Parallels, Inc.

More information

Provider's Guide to Integrating Parallels Presence Builder 12 with Parallels Automation

Provider's Guide to Integrating Parallels Presence Builder 12 with Parallels Automation Parallels Automation Provider's Guide to Integrating Parallels Presence Builder 12 with Parallels Automation Last updated: 23 January 2015 Copyright 1999-2015 Parallels IP Holdings GmbH and its affiliates.

More information

Legal and Copyright Notice

Legal and Copyright Notice Parallels Helm Legal and Copyright Notice ISBN: N/A Parallels 660 SW 39 th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 2010, Parallels, Inc.

More information

Legal and Copyright Notice

Legal and Copyright Notice Parallels Helm Legal and Copyright Notice ISBN: N/A Parallels 660 SW 39 th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 2008, Parallels, Inc.

More information

Parallels Panel. Parallels Small Business Panel 10.2: User's Guide. Revision 1.0

Parallels Panel. Parallels Small Business Panel 10.2: User's Guide. Revision 1.0 Parallels Panel Parallels Small Business Panel 10.2: User's Guide Revision 1.0 Copyright Notice ISBN: N/A Parallels 660 SW 39 th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax:

More information

Parallels Plesk Control Panel

Parallels Plesk Control Panel Parallels Plesk Control Panel Copyright Notice ISBN: N/A Parallels 660 SW 39 th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 1999-2008, Parallels,

More information

Parallels Plesk Automation

Parallels Plesk Automation Parallels Plesk Automation Contents Get Started 3 Infrastructure Configuration... 4 Network Configuration... 6 Installing Parallels Plesk Automation 7 Deploying Infrastructure 9 Installing License Keys

More information

Plesk for Windows Copyright Notice

Plesk for Windows Copyright Notice 2 Plesk for Windows Copyright Notice ISBN: N/A SWsoft. 13755 Sunrise Valley Drive Suite 325 Herndon VA 20171 USA Phone: +1 (703) 815 5670 Fax: +1 (703) 815 5675 Copyright 1999-2007, SWsoft Holdings, Ltd.

More information

Getting Started With Parallels Business Automation 4.4

Getting Started With Parallels Business Automation 4.4 Parallels Getting Started With Parallels Business Automation 4.4 Reseller's Guide Revision 1.0.18 (c) 1999-2008 ISBN: N/A Parallels 660 SW 39th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425)

More information

Parallels Plesk Panel

Parallels Plesk Panel Parallels Plesk Panel Copyright Notice ISBN: N/A Parallels 660 SW 39th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 1999-2009, Parallels, Inc.

More information

Plesk 8.3 for Linux/Unix Acronis True Image Server Module Administrator's Guide

Plesk 8.3 for Linux/Unix Acronis True Image Server Module Administrator's Guide Plesk 8.3 for Linux/Unix Acronis True Image Server Module Administrator's Guide Revision 1.0 Copyright Notice ISBN: N/A SWsoft. 13755 Sunrise Valley Drive Suite 600 Herndon VA 20171 USA Phone: +1 (703)

More information

Legal and Copyright Notice

Legal and Copyright Notice Parallels Confixx Legal and Copyright Notice ISBN: N/A Parallels 660 SW 39 th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 2008, Parallels GmbH

More information

Parallels Server Bare Metal 5.0

Parallels Server Bare Metal 5.0 Parallels Server Bare Metal 5.0 Getting Started Guide Copyright 1999-2011 Parallels Holdings, Ltd. and its affiliates. All rights reserved. Parallels Holdings, Ltd. c/o Parallels International GMbH. Parallels

More information

Legal and Copyright Notice

Legal and Copyright Notice Parallels Helm Legal and Copyright Notice ISBN: N/A Parallels 660 SW 39 th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 2010, Parallels, Inc.

More information

Parallels Containers for Windows 6.0

Parallels Containers for Windows 6.0 Parallels Containers for Windows 6.0 Upgrade Guide June 11, 2014 Copyright 1999-2014 Parallels IP Holdings GmbH and its affiliates. All rights reserved. Parallels IP Holdings GmbH Vordergasse 59 8200 Schaffhausen

More information

Parallels Plesk Control Panel

Parallels Plesk Control Panel Parallels Plesk Control Panel Copyright Notice ISBN: N/A Parallels 660 SW 39 th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 1999-2008, Parallels,

More information

VPS Hosting User Guide

VPS Hosting User Guide TM VPS Hosting User Guide VPS Hosting Control Panel Managing VPS... 1 Opening Power Panel...... 1 Starting/Stopping VPS... 2 Changing VPS Hostname... 2 Enabling/Disabling Automatic Updates... 5 Installing

More information

SWsoft Plesk 8.3 for Linux/Unix Backup and Restore Utilities

SWsoft Plesk 8.3 for Linux/Unix Backup and Restore Utilities SWsoft Plesk 8.3 for Linux/Unix Backup and Restore Utilities Administrator's Guide Revision 1.0 Copyright Notice ISBN: N/A SWsoft. 13755 Sunrise Valley Drive Suite 600 Herndon VA 20171 USA Phone: +1 (703)

More information

Counter-Strike Game Server Management Module

Counter-Strike Game Server Management Module SWsoft, Inc. Counter-Strike Game Server Management Module Administrator's Guide ISBN: N/A SWsoft, Inc. 13755 Sunrise Valley Drive Suite 325 Herndon VA 20171 USA Phone: +1 (703) 815 5670 Fax: +1 (703) 815

More information

Parallels Plesk Panel

Parallels Plesk Panel Parallels Plesk Panel Copyright Notice ISBN: N/A Parallels 660 SW 39th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 1999-2009, Parallels, Inc.

More information

Parallels Virtual Automation 6.0

Parallels Virtual Automation 6.0 Parallels Virtual Automation 6.0 Installation Guide for Windows Copyright 1999-2012 Parallels IP Holdings GmbH and its affiliates. All rights reserved. Parallels IP Holdings GmbH. c/o Parallels International

More information

Deploying IBM Lotus Domino on Red Hat Enterprise Linux 5. Version 1.0

Deploying IBM Lotus Domino on Red Hat Enterprise Linux 5. Version 1.0 Deploying IBM Lotus Domino on Red Hat Enterprise Linux 5 Version 1.0 November 2008 Deploying IBM Lotus Domino on Red Hat Enterprise Linux 5 1801 Varsity Drive Raleigh NC 27606-2072 USA Phone: +1 919 754

More information

Parallels Business Automation 5.5

Parallels Business Automation 5.5 Parallels Business Automation 5.5 Trustwave SSL Plug-in Configuration Guide Revision 1.2 (June 20, 2014) Copyright 1999-2014 Parallels IP Holdings GmbH and its affiliates. All rights reserved. Parallels

More information

SWsoft, Inc. Plesk File Server. Administrator's Guide. Plesk 7.5 Reloaded

SWsoft, Inc. Plesk File Server. Administrator's Guide. Plesk 7.5 Reloaded SWsoft, Inc. Plesk File Server Administrator's Guide Plesk 7.5 Reloaded (c) 1999-2005 ISBN: N/A SWsoft Inc 13755 Sunrise Valley Drive Suite 325 Herndon VA 20171 USA Tel: +1 (703) 815 5670 Fax: +1 (703)

More information

Key-Systems Registrar Plug-in PBA Configuration Guide Revision 1.1

Key-Systems Registrar Plug-in PBA Configuration Guide Revision 1.1 Key-Systems Registrar Plug-in PBA Configuration Guide Revision 1.1 1999-2012 1/13 Parallels IP Holdings GmbH. Vordergasse 59 CH8200 Schaffhausen Switzerland Tel: + 41 526320 411 Fax: + 41 52672 2010 www.parallels.com

More information

Parallels Plesk Panel

Parallels Plesk Panel Parallels Plesk Panel Copyright Notice ISBN: N/A Parallels 660 SW 39th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 1999-2009, Parallels, Inc.

More information

Parallels Virtual Automation 6.1

Parallels Virtual Automation 6.1 Parallels Virtual Automation 6.1 Installation Guide for Windows April 08, 2014 Copyright 1999-2014 Parallels IP Holdings GmbH and its affiliates. All rights reserved. Parallels IP Holdings GmbH. c/o Parallels

More information

Plesk 8.3 for Linux/Unix System Monitoring Module Administrator's Guide

Plesk 8.3 for Linux/Unix System Monitoring Module Administrator's Guide Plesk 8.3 for Linux/Unix System Monitoring Module Administrator's Guide Revision 1.0 Copyright Notice ISBN: N/A SWsoft. 13755 Sunrise Valley Drive Suite 600 Herndon VA 20171 USA Phone: +1 (703) 815 5670

More information

Parallels Cloud Server 6.0

Parallels Cloud Server 6.0 Parallels Cloud Server 6.0 Getting Started Guide Copyright 1999-2012 Parallels IP Holdings GmbH and its affiliates. All rights reserved. Parallels IP Holdings GmbH. Vordergasse 59 CH8200 Schaffhausen Switzerland

More information

HP Intelligent Management Center v7.1 Virtualization Monitor Administrator Guide

HP Intelligent Management Center v7.1 Virtualization Monitor Administrator Guide HP Intelligent Management Center v7.1 Virtualization Monitor Administrator Guide Abstract This guide describes the Virtualization Monitor (vmon), an add-on service module of the HP Intelligent Management

More information

F-Secure Messaging Security Gateway. Deployment Guide

F-Secure Messaging Security Gateway. Deployment Guide F-Secure Messaging Security Gateway Deployment Guide TOC F-Secure Messaging Security Gateway Contents Chapter 1: Deploying F-Secure Messaging Security Gateway...3 1.1 The typical product deployment model...4

More information

Copyright Notice. ISBN: N/A Parallels 660 SW 39th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444

Copyright Notice. ISBN: N/A Parallels 660 SW 39th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Parallels Panel Copyright Notice ISBN: N/A Parallels 660 SW 39th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 1999-2009, Parallels, Inc. All rights

More information

Parallels Plesk Automation

Parallels Plesk Automation Parallels Plesk Automation Copyright Notice Parallels IP Holdings GmbH Vordergasse 59 CH-Schaffhausen Switzerland Phone: +41 526320 411 Fax: +41 52672 2010 Global Headquarters 500 SW 39th Street, Suite

More information

Parallels Panel. Deployment Guide. Plesk Automation 11.5. Revision 1.0

Parallels Panel. Deployment Guide. Plesk Automation 11.5. Revision 1.0 Parallels Panel Deployment Guide Plesk Automation 11.5 Revision 1.0 Contents Getting Started 3 Infrastructure Configuration... 4 Network Configuration... 6 Installing Plesk Automation 8 Upgrading Plesk

More information

Parallels Plesk Panel

Parallels Plesk Panel Parallels Plesk Panel Copyright Notice ISBN: N/A Parallels 660 SW 39th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 1999-2009, Parallels, Inc.

More information

POA 2.8 Hotfix 02 Release Notes

POA 2.8 Hotfix 02 Release Notes Parallels POA 2.8 Hotfix 02 Release Notes Revision 1.7 (December 30, 2008) 1999-2008 C H A P T E R 1 New Features Exchange 2007 Branding Since POA 2.8 HF 02, Provider and Reseller get the possibility to

More information

OnCommand Performance Manager 1.1

OnCommand Performance Manager 1.1 OnCommand Performance Manager 1.1 Installation and Setup Guide For Red Hat Enterprise Linux NetApp, Inc. 495 East Java Drive Sunnyvale, CA 94089 U.S. Telephone: +1 (408) 822-6000 Fax: +1 (408) 822-4501

More information

WHM Administrator s Guide

WHM Administrator s Guide Fasthosts Customer Support WHM Administrator s Guide This manual covers everything you need to know in order to get started with WHM and perform day to day administrative tasks. Contents Introduction...

More information

Interworks. Interworks Cloud Platform Installation Guide

Interworks. Interworks Cloud Platform Installation Guide Interworks Interworks Cloud Platform Installation Guide Published: March, 2014 This document contains information proprietary to Interworks and its receipt or possession does not convey any rights to reproduce,

More information

SWsoft Plesk 8.2 for Linux/Unix Backup and Restore Utilities. Administrator's Guide

SWsoft Plesk 8.2 for Linux/Unix Backup and Restore Utilities. Administrator's Guide SWsoft Plesk 8.2 for Linux/Unix Backup and Restore Utilities Administrator's Guide 2 Copyright Notice ISBN: N/A SWsoft. 13755 Sunrise Valley Drive Suite 325 Herndon VA 20171 USA Phone: +1 (703) 815 5670

More information

Parallels Plesk Panel

Parallels Plesk Panel Parallels Plesk Panel Copyright Notice ISBN: N/A Parallels 660 SW 39th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 1999-2009, Parallels, Inc.

More information

Parallels Plesk Panel

Parallels Plesk Panel Parallels Plesk Panel Copyright Notice Parallels Holdings, Ltd. c/o Parallels International GmbH Vordergasse 59 CH-Schaffhausen Switzerland Phone: +41-526320-411 Fax: +41-52672-2010 Copyright 1999-2011

More information

http://docs.trendmicro.com

http://docs.trendmicro.com Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice. Before installing and using the product, please review the readme files,

More information

Plesk 8.0 for Linux/UNIX Backup and Restore Utilities

Plesk 8.0 for Linux/UNIX Backup and Restore Utilities SWsoft, Inc. Plesk 8.0 for Linux/UNIX Backup and Restore Utilities Administrator s Guide Revision 1.1 (31 May 2006) (c) 1999-2006 ISBN: N/A SWsoft, Inc. 13755 Sunrise Valley Drive Suite 325 Herndon VA

More information

Plesk 11 Manual. Fasthosts Customer Support

Plesk 11 Manual. Fasthosts Customer Support Fasthosts Customer Support Plesk 11 Manual This guide covers everything you need to know in order to get started with the Parallels Plesk 11 control panel. Contents Introduction... 3 Before you begin...

More information

Patented hosting technology protected by U.S.Patents 7,0909,948; 7,076,633. Patents pending in the U.S.

Patented hosting technology protected by U.S.Patents 7,0909,948; 7,076,633. Patents pending in the U.S. Copyright Notice ISBN: N/A SWsoft. 13755 Sunrise Valley Drive Suite 600 Herndon VA 20171 USA Phone: +1 (703) 815 5670 Fax: +1 (703) 815 5675 Copyright 1999-2007, SWsoft Holdings, Ltd. All rights reserved

More information

Plesk for Windows Copyright Notice

Plesk for Windows Copyright Notice 2 Plesk for Windows Copyright Notice ISBN: N/A SWsoft. 13755 Sunrise Valley Drive Suite 325 Herndon VA 20171 USA Phone: +1 (703) 815 5670 Fax: +1 (703) 815 5675 Copyright 1999-2007, SWsoft Holdings, Ltd.

More information

Parallels Plesk Panel

Parallels Plesk Panel Parallels Plesk Panel Copyright Notice ISBN: N/A Parallels 660 SW 39th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 1999-2010, Parallels, Inc.

More information

LOCKSS on LINUX. CentOS6 Installation Manual 08/22/2013

LOCKSS on LINUX. CentOS6 Installation Manual 08/22/2013 LOCKSS on LINUX CentOS6 Installation Manual 08/22/2013 1 Table of Contents Overview... 3 LOCKSS Hardware... 5 Installation Checklist... 6 BIOS Settings... 9 Installation... 10 Firewall Configuration...

More information

Parallels Virtuozzo Containers for Windows

Parallels Virtuozzo Containers for Windows Parallels Parallels Virtuozzo Containers for Windows Installation Guide Version 4.0 Copyright 1999-2008 Parallels Software International Inc. ISBN: N/A Parallels Holdings Ltd. 13755 Sunrise Valley Drive

More information

Parallels Panel. Parallels Small Business Panel 10.2: Administrator's Guide. Revision 1.0

Parallels Panel. Parallels Small Business Panel 10.2: Administrator's Guide. Revision 1.0 Parallels Panel Parallels Small Business Panel 10.2: Administrator's Guide Revision 1.0 Copyright Notice ISBN: N/A Parallels 660 SW 39 th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282

More information

Moving to Plesk Automation 11.5

Moving to Plesk Automation 11.5 Moving to Plesk Automation 11.5 Last updated: 2 June 2015 Contents About This Document 4 Introduction 5 Preparing for the Move 7 1. Install the PA Moving Tool... 8 2. Install Mail Sync Software (Windows

More information

SWsoft, Inc. Plesk VPN. Administrator's Guide. Plesk 7.5 Reloaded

SWsoft, Inc. Plesk VPN. Administrator's Guide. Plesk 7.5 Reloaded SWsoft, Inc. Plesk VPN Administrator's Guide Plesk 7.5 Reloaded (c) 1999-2004 ISBN: N/A SWsoft Inc 13800 Coppermine Drive Suite 112 Herndon VA 20171 USA Tel: +1 (703) 815 5670 Fax: +1 (703) 815 5675 Copyright

More information

Parallels Plesk Panel

Parallels Plesk Panel Parallels Plesk Panel Copyright Notice Parallels Holdings, Ltd. c/o Parallels International GmbH Vordergasse 59 CH-Schaffhausen Switzerland Phone: +41-526320-411 Fax: +41-52672-2010 Copyright 1999-2011

More information

Parallels Operations Automation 5.0 Public API Reference

Parallels Operations Automation 5.0 Public API Reference Parallels Parallels Operations Automation 5.0 Public API Reference Revision 9.34 (June 12, 2010) 1999-2010 2 ISBN: N/A Parallels 500 SW 39th Street Suite 200 Renton, WA 98057 USA Phone: +1 (425) 282 6400

More information

Parallels Plesk Control Panel. Plesk 8.3 for Windows Advanced Administration Guide. Revision 1.0

Parallels Plesk Control Panel. Plesk 8.3 for Windows Advanced Administration Guide. Revision 1.0 Parallels Plesk Control Panel Plesk 8.3 for Windows Advanced Administration Guide Revision 1.0 Contents Preface 5 Documentation Conventions... 5 Typographical Conventions... 5 Feedback... 6 About This

More information

Preface 6. Typographical Conventions... 6 Feedback... 7. Operating Inside Parallels Containers 8. Becoming Familiar with Parallels Plesk Panel 10

Preface 6. Typographical Conventions... 6 Feedback... 7. Operating Inside Parallels Containers 8. Becoming Familiar with Parallels Plesk Panel 10 Parallels Panel Copyright Notice Parallels Holdings, Ltd. c/o Parallels International GmbH Vordergasse 59 CH-Schaffhausen Switzerland Phone: +41-526320-411 Fax: +41-52672-2010 Copyright 1999-2011 Parallels

More information

Parallels Plesk Panel

Parallels Plesk Panel Parallels Plesk Panel Copyright Notice ISBN: N/A Parallels 660 SW 39th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 1999-2009, Parallels, Inc.

More information

SWsoft, Inc. Plesk Firewall. Administrator's Guide

SWsoft, Inc. Plesk Firewall. Administrator's Guide SWsoft, Inc. Plesk Firewall Administrator's Guide (c) 1999-2004 ISBN: N/A SWsoft Inc 13800 Coppermine Drive Suite 112 Herndon VA 20171 USA Tel: +1 (703) 815 5670 Fax: +1 (703) 815 5675 Copyright 1999-2004

More information

Parallels Virtuozzo Containers for Windows

Parallels Virtuozzo Containers for Windows Parallels Parallels Virtuozzo Containers for Windows Templates Management Guide Version 4.0 Copyright 1999-2008 Parallels Software International Inc. ISBN: N/A Parallels Holdings Ltd. 13755 Sunrise Valley

More information

Hillstone StoneOS User Manual Hillstone Unified Intelligence Firewall Installation Manual

Hillstone StoneOS User Manual Hillstone Unified Intelligence Firewall Installation Manual Hillstone StoneOS User Manual Hillstone Unified Intelligence Firewall Installation Manual www.hillstonenet.com Preface Conventions Content This document follows the conventions below: CLI Tip: provides

More information

Parallels Automation 5.5

Parallels Automation 5.5 Parallels Automation 5.5 Hardware Requirements Revision 10.62 (October 31, 2013) Copyright 1999-2013 Parallels IP Holdings GmbH and its affiliates. All rights reserved. Parallels IP Holdings GmbH Vordergasse

More information

Domain Central Reseller Billing 4.2

Domain Central Reseller Billing 4.2 Domain Central Domain Central Reseller Billing 4.2 Getting Started - Resellers Guide Revision 1.1.05 (c) 1999-2007 2 Contents Preface 3 Documentation Conventions...3 Typographical Conventions...3 Feedback...4

More information

Figure: Top Navigation Frame: Ability to Add Services from Different Subscriptions Is Enabled

Figure: Top Navigation Frame: Ability to Add Services from Different Subscriptions Is Enabled Working with Domains TM Control Panel User Guide Working with Domains 1 After you have selected a Subscription, you will need to add a Webspace for your domain. This will provide you with the ability of

More information

http://docs.trendmicro.com

http://docs.trendmicro.com Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice. Before installing and using the product, please review the readme files,

More information

Preface 8. Typographical Conventions... 8 Feedback... 9. Operating Inside Parallels Containers 10. What s New in Parallels Plesk Panel 12

Preface 8. Typographical Conventions... 8 Feedback... 9. Operating Inside Parallels Containers 10. What s New in Parallels Plesk Panel 12 Parallels Panel Copyright Notice Parallels Holdings, Ltd. c/o Parallels International GmbH Vordergasse 59 CH-Schaffhausen Switzerland Phone: +41-526320-411 Fax: +41-52672-2010 Copyright 1999-2011 Parallels

More information

Core Protection for Virtual Machines 1

Core Protection for Virtual Machines 1 Core Protection for Virtual Machines 1 Comprehensive Threat Protection for Virtual Environments. Installation Guide e Endpoint Security Trend Micro Incorporated reserves the right to make changes to this

More information

Parallels Cloud Server 6.0

Parallels Cloud Server 6.0 Parallels Cloud Server 6.0 Installation Guide Copyright 1999-2013 Parallels IP Holdings GmbH and its affiliates. All rights reserved. Parallels IP Holdings GmbH. Vordergasse 59 CH8200 Schaffhausen Switzerland

More information

LOCKSS on LINUX. Installation Manual and the OpenBSD Transition 02/17/2011

LOCKSS on LINUX. Installation Manual and the OpenBSD Transition 02/17/2011 LOCKSS on LINUX Installation Manual and the OpenBSD Transition 02/17/2011 1 Table of Contents Overview... 3 LOCKSS Hardware... 5 Installation Checklist... 7 BIOS Settings... 10 Installation... 11 Firewall

More information

WEB2CS INSTALLATION GUIDE

WEB2CS INSTALLATION GUIDE WEB2CS INSTALLATION GUIDE FOR PARALLELS / POA HTTP://WWW.XANDMAIL.COM XandMail 32, rue de Cambrai 75019 PARIS - FRANCE Tel : +33 (0)1 40 388 700 - http://www.xandmail.com TABLE OF CONTENTS 1. INSTALLING

More information

insync Installation Guide

insync Installation Guide insync Installation Guide 5.2 Private Cloud Druva Software June 21, 13 Copyright 2007-2013 Druva Inc. All Rights Reserved. Table of Contents Deploying insync Private Cloud... 4 Installing insync Private

More information

Parallels Panel. Achieving PCI Compliance for Servers Managed by Parallels Small Business Panel 10.2. Revision 1.0

Parallels Panel. Achieving PCI Compliance for Servers Managed by Parallels Small Business Panel 10.2. Revision 1.0 Parallels Panel Achieving PCI Compliance for Servers Managed by Parallels Small Business Panel 10.2 Revision 1.0 Contents Preface 3 Typographical Conventions... 3 Feedback... 4 Securing Servers in Compliance

More information

Parallels Virtuozzo Containers 4.7 for Linux

Parallels Virtuozzo Containers 4.7 for Linux Parallels Virtuozzo Containers 4.7 for Linux Deploying Clusters in Parallels-Based Systems Copyright 1999-2011 Parallels Holdings, Ltd. and its affiliates. All rights reserved. Parallels Holdings, Ltd.

More information

SWsoft PEM 2.6. Provider's Guide. Revision 4.0.9 (April 4, 2007)

SWsoft PEM 2.6. Provider's Guide. Revision 4.0.9 (April 4, 2007) SWsoft PEM 2.6 Provider's Guide Revision 4.0.9 (April 4, 2007) (c) 1999-2007 2 Contents Preface 11 About This Guide...12 Who Should Read This Guide...12 Organization of This Guide...12 Documentation Conventions...13

More information

Server Installation Guide ZENworks Patch Management 6.4 SP2

Server Installation Guide ZENworks Patch Management 6.4 SP2 Server Installation Guide ZENworks Patch Management 6.4 SP2 02_016N 6.4SP2 Server Installation Guide - 2 - Notices Version Information ZENworks Patch Management Server Installation Guide - ZENworks Patch

More information

Parallels Cloud Server 6.0

Parallels Cloud Server 6.0 Parallels Cloud Server 6.0 Getting Started Guide August 15, 2013 Copyright 1999-2013 Parallels IP Holdings GmbH and its affiliates. All rights reserved. Parallels IP Holdings GmbH Vordergasse 59 8200 Schaffhausen

More information

Admin Guide Virtual Private Server (VPS) MailStreet Hosting Control Panel (CP)

Admin Guide Virtual Private Server (VPS) MailStreet Hosting Control Panel (CP) Admin Guide Virtual Private Server (VPS) MailStreet Hosting Control Panel (CP) DOCUMENT REVISION DATE: September 1, 2009 Virtual Private Server (VPS) Admin Guide / Table of Contents Page 2 of 87 Table

More information

Quick Start Guide for Parallels Virtuozzo

Quick Start Guide for Parallels Virtuozzo PROPALMS VDI Version 2.1 Quick Start Guide for Parallels Virtuozzo Rev. 1.1 Published: JULY-2011 1999-2011 Propalms Ltd. All rights reserved. The information contained in this document represents the current

More information

PARALLELS SERVER BARE METAL 5.0 README

PARALLELS SERVER BARE METAL 5.0 README PARALLELS SERVER BARE METAL 5.0 README 1999-2011 Parallels Holdings, Ltd. and its affiliates. All rights reserved. This document provides the first-priority information on the Parallels Server Bare Metal

More information

Quick Start Guide 0514US

Quick Start Guide 0514US Quick Start Guide Copyright Wasp Barcode Technologies 2014 No part of this publication may be reproduced or transmitted in any form or by any means without the written permission of Wasp Barcode Technologies.

More information

http://www.trendmicro.com/download

http://www.trendmicro.com/download Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice. Before installing and using the software, please review the readme files,

More information

Legal and Copyright Notice

Legal and Copyright Notice Parallels Confixx Legal and Copyright Notice ISBN: N/A Parallels 660 SW 39 th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 2009, Parallels GmbH

More information

Deploying Microsoft Clusters in Parallels Virtuozzo-Based Systems

Deploying Microsoft Clusters in Parallels Virtuozzo-Based Systems Parallels Deploying Microsoft Clusters in Parallels Virtuozzo-Based Systems Copyright 1999-2008 Parallels, Inc. ISBN: N/A Parallels Holdings, Ltd. c/o Parallels Software, Inc. 13755 Sunrise Valley Drive

More information

Setting Up a Unisphere Management Station for the VNX Series P/N 300-011-796 Revision A01 January 5, 2010

Setting Up a Unisphere Management Station for the VNX Series P/N 300-011-796 Revision A01 January 5, 2010 Setting Up a Unisphere Management Station for the VNX Series P/N 300-011-796 Revision A01 January 5, 2010 This document describes the different types of Unisphere management stations and tells how to install

More information

virtualization.info Review Center SWsoft Virtuozzo 3.5.1 (for Windows) // 02.26.06

virtualization.info Review Center SWsoft Virtuozzo 3.5.1 (for Windows) // 02.26.06 virtualization.info Review Center SWsoft Virtuozzo 3.5.1 (for Windows) // 02.26.06 SWsoft Virtuozzo 3.5.1 (for Windows) Review 2 Summary 0. Introduction 1. Installation 2. VPSs creation and modification

More information

XenClient Enterprise Synchronizer Installation Guide

XenClient Enterprise Synchronizer Installation Guide XenClient Enterprise Synchronizer Installation Guide Version 5.1.0 March 26, 2014 Table of Contents About this Guide...3 Hardware, Software and Browser Requirements...3 BIOS Settings...4 Adding Hyper-V

More information

Parallels Plesk Panel

Parallels Plesk Panel Parallels Plesk Panel Copyright Notice ISBN: N/A Parallels 660 SW 39th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 1999-2010, Parallels, Inc.

More information

Installing GFI MailSecurity

Installing GFI MailSecurity Installing GFI MailSecurity Introduction This chapter explains how to install and configure GFI MailSecurity. You can install GFI MailSecurity directly on your mail server or you can choose to install

More information

Parallels Virtuozzo Containers 4.6 for Linux

Parallels Virtuozzo Containers 4.6 for Linux Parallels Parallels Virtuozzo Containers 4.6 for Linux User's Guide Copyright 1999-2010 Parallels Holdings, Ltd. and its affiliates. All rights reserved. Parallels Holdings, Ltd. c/o Parallels International

More information

The SSL device also supports the 64-bit Internet Explorer with new ActiveX loaders for Assessment, Abolishment, and the Access Client.

The SSL device also supports the 64-bit Internet Explorer with new ActiveX loaders for Assessment, Abolishment, and the Access Client. WatchGuard SSL v3.2 Release Notes Supported Devices SSL 100 and 560 WatchGuard SSL OS Build 355419 Revision Date January 28, 2013 Introduction WatchGuard is pleased to announce the release of WatchGuard

More information

Plesk 8.1 for Windows Counter-Strike Game Server

Plesk 8.1 for Windows Counter-Strike Game Server SWsoft, Inc. Plesk 8.1 for Windows Counter-Strike Game Server Administrator Guide (revision 2.2) (c) 1999-2006 ISBN: N/A SWsoft, Inc. 13755 Sunrise Valley Drive Suite 325 Herndon VA 20171 USA Phone: +1

More information

Parallels Plesk Control Panel

Parallels Plesk Control Panel Parallels Plesk Control Panel Copyright Notice ISBN: N/A Parallels 660 SW 39 th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 Copyright 1999-2008, Parallels,

More information

JAMF Software Server Installation Guide for Linux. Version 8.6

JAMF Software Server Installation Guide for Linux. Version 8.6 JAMF Software Server Installation Guide for Linux Version 8.6 JAMF Software, LLC 2012 JAMF Software, LLC. All rights reserved. JAMF Software has made all efforts to ensure that this guide is accurate.

More information

APS Package Certification Guide

APS Package Certification Guide APS Package Certification Guide Revision 1.0.15 Copyright 1999-2012 by Parallels Holdings Ltd. and its affiliates. rights reserved. All Contents Feedback If you have found a mistake in this guide, or if

More information

DocuShare Installation Guide

DocuShare Installation Guide DocuShare Installation Guide Publication date: February 2011 This document supports DocuShare Release 6.6.1 Prepared by: Xerox Corporation DocuShare Business Unit 3400 Hillview Avenue Palo Alto, California

More information

This document describes the new features of this release and important changes since the previous one.

This document describes the new features of this release and important changes since the previous one. Parallels Virtuozzo Containers 4.0 for Linux Release Notes Copyright 1999-2011 by Parallels Holdings, Ltd. All rights reserved. This document describes the new features of this release and important changes

More information

PARALLELS SERVER 4 BARE METAL README

PARALLELS SERVER 4 BARE METAL README PARALLELS SERVER 4 BARE METAL README This document provides the first-priority information on Parallels Server 4 Bare Metal and supplements the included documentation. TABLE OF CONTENTS 1 About Parallels

More information

Getting Started Guide. Getting Started With Your Dedicated Server. Setting up and hosting a domain on your Linux Dedicated Server using Plesk 8.0.

Getting Started Guide. Getting Started With Your Dedicated Server. Setting up and hosting a domain on your Linux Dedicated Server using Plesk 8.0. Getting Started Guide Getting Started With Your Dedicated Server Setting up and hosting a domain on your Linux Dedicated Server using Plesk 8.0. Getting Started with Your Dedicated Server Plesk 8.0 Version

More information