Quick Start Guide Plesk Automation 11.5

Quick Start Guide Plesk Automation 11.5

Quick Start Guide Plesk Automation 11.5 Introduction Contents Introduction ................................................................................................................3 1. Installing PA on the Management Node ...............................................................6 2. Adding Service Nodes ...........................................................................................7 2.1 Logging In to PA ....................................................................................................... 7 2.2 Configuring the DNS Server ...................................................................................... 7 2.3 Adding a Service Node with Apache Web Hosting ..................................................... 9 2.4 Adding a Service Node with Mail Server .................................................................. 10 2.5 Adding a Service Node with PA billing ..................................................................... 12 3. Installing License Keys ........................................................................................ 17 4. Offering Services to Customers .......................................................................... 19 4.1 Creating a Service Plan ........................................................................................... 19 4.2 Creating a Customer Account ................................................................................. 24 4.3 Creating a Subscription for a Customer ................................................................... 26 4.4 Logging in to Panel as a Customer .......................................................................... 28 Getting Help with PA ............................................................................................... 30 Introduction C H A P T E R 1 Introduction PA is a scalable, multi-server automation solution for shared hosting, giving growing hosters the power, performance, and scale previously only available to hosting giants. PA is designed to centrally manage thousands of customers from a central point. PA Architecture The idea behind the PA architecture is a distributed environment with one central server. This server, called a management node, controls an arbitrary number of servers with various roles - web, mail, DNS, and others. In terms of PA, these controlled servers are called service nodes. Service nodes provide a full set of hosting services that are delivered to customers through the management node. All operations including infrastructure and hosting management are also performed through this central node. Introduction The diagram below represents the PA architecture. The PA User Interface The PA UI consists of the following components: • Administration Panel. Administrators use this panel to manage PA infrastructure: add and configure service nodes, manage IP pools, and so on. • Hosting Panel. Customers use this panel to manage their hosting services: add domains and mailboxes, manage website content and so on. • (Optional) Billing solution. Administrators and resellers can employ a billing solution to automate subscribing customers to hosting plans as well as to automate the monetization of this process. Currently, PA supports the following solutions: • Plesk Automation billing. • Odin Business Automation Standard. Introduction • Web Host Manager Complete Solution (WHMCS). • Any homegrown billing system integrated with PA by means of API. Note: Administration and Hosting panels are hosted on the management node. Service nodes do not provide the UI. Running PA Putting PA into operation involves the following steps: • Installation of PA packages to the management node. • Deploying attendant infrastructure (registering and configuring service nodes). • Installing and configuring a billing solution. • Installing license keys for the management and service nodes. • Configuring PA to start serving customers (creating a hosting plan). This guide is intended for hosting providers who plan to deploy PA. It shows how to quickly start working with PA by covering the five main steps mentioned above. In addition, the guide describes such basic administration tasks as troubleshooting and system monitoring. 1. Installing PA on the Management Node C H A P T E R 2 1. Installing PA on the Management Node A management node is the central server in a distributed system, which allows performing all operations including infrastructure and hosting management. Thus, the first step in deploying PA is to install its packages to the management node. The PA installation is fully automated and performed by the single script file ppa_installer. To install PA management node components on your server: 1 Log in to your server as root. 2 Download the PA installation script. #wget http://download.automation.odin.com/ppa/11.5/ppa_installer 3 Allow script execution. #chmod +x ppa_installer 4 Run the script with the following options. #./ppa_installer --password setup --admin_email [email protected] where • setup - the PA login password. • [email protected] - your e-mail address. 2. Adding Service Nodes C H A P T E R 3 2. Adding Service Nodes After the installation is finished, proceed to infrastructure deployment, or, in other words, registering your auxiliary servers (service nodes) that will provide various hosting services. In this guide, we will explain how to register a Linux-based service node for running a billing system called Plesk Automation billing, one Apache web service node, and one Postfix mail service node. In this chapter: 2.1 Logging In to PA ...............................................................................................7 2.2 Configuring the DNS Server ...............................................................................7 2.3 Adding a Service Node with Apache Web Hosting .............................................9 2.4 Adding a Service Node with Mail Server .............................................................10 2.5 Adding a Service Node with PA billing ................................................................12 2.1 Logging In to PA To log in to PA, type the following address in your browser: https://<IP_address>: 8443 where <IP_address> is the IP address of your management node, or its host name. When PA prompts to enter the administrator's credentials, use the admin username and the password you specified during the PA installation. 2.2 Configuring the DNS Server By default, DNS services are provided by the management node. It acts as a master DNS server for all zones registered in the system. You can configure PA to use DNS servers installed on separate service nodes. Setup of DNS zones for newly added domains is automated: When a customer adds a new domain in the Hosting Panel, PA automatically generates its zone file and registers it in the name server's database. If you want to run the DNS server on a separate service node, complete the following steps: 2. Adding Service Nodes 1 Go to Infrastructure > Service Nodes, and click Add New Node. A list of server roles is displayed. 2 Select the DNS server role from the list. 3 Specify the node's host name or IP address, and a root password. 4 Click Next, and then click Finish. Once you add the node, it appears in the list of registered PA name servers, which is available in Services > DNS Zones > DNS > Nameservers. Note: The value of the ready to provide setting is ignored by PA on DNS nodes. 2. Adding Service Nodes 5 Set this node as a master or slave name server in the DNS resource type properties at Products > Resources > DNS > Activation Parameters tab > Edit. In addition, you can set the SOA record template parameters: refresh and retry intervals, expiration period, and minimum TTL. The template settings are applied to the SOA record of all zones but can be overridden for a specific zone. You can learn more about this in PA: Operations Guide, chapter Configuring DNS, section Managing DNS Zones. 2.3 Adding a Service Node with Apache Web Hosting To provide web hosting services, we will add a service node running the Apache web server: 1 Go to Infrastructure > Service Nodes, and click Add New Node. A list of server roles is displayed. 2 Select the Apache web server role from the list. 2. Adding Service Nodes 3 Specify the node's host name or IP address, and a root password. 4 Click Next, and then click Finish. Normally, when the installation is complete, the node is marked as Ready to provide its services. If this does not happen, resolve the issue and mark it manually in node properties (Infrastructure > Service Nodes > node's hostname > Mark as ready to provide). After you add the web server node, PA will automatically install all necessary packages on that server. To make sure that all operations were performed successfully, check that the task log (Operations > Tasks > Task Log) does not contain any failed tasks. 2.4 Adding a Service Node with Mail Server To provide mail services, we will add a service node running the Postfix mail server: 2. Adding Service Nodes 1 Go to Infrastructure > Service Nodes, and click Add New Node. A list of server roles is displayed. 2 Select the Postfix mail server role from the list. 3 Specify the node's host name or IP address, and a root password. 4 Click Next, and then click Finish. Normally, when the installation is complete, the node is marked as Ready to provide its services. If this does not happen, resolve the issue and mark it manually in node properties (Infrastructure > Service Nodes > node's hostname > Mark as ready

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    30 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us