Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This section describes the procedure for setting up advanced High Availability configuration. This configuration requires two Control Panel servers, three Database & Transactions servers and two Load Balancer servers. These servers must comply with the hardware requirements.

Table of Contents

Physical Infrastructure Configuration


Configure you physical infrastructure to set up High Availability:

  1. Add two Control Panel servers, three Database & Transactions servers and two Load Balancer servers. These servers must comply with the hardware requirements.
  2. Install CentOS /Red Hat 6x 6.x on all servers.
  3. Configure valid host names for the servers. 
  4. Configure network for the servers.
  5. Install onapp-cp, onapp-store, onapp-cp-ha on two Control Panel servers with local MySQL.:

    Code Block
    bash#> yum install onapp-cp-install
    Code Block
    yum install onapp-cp-ha
    Note

    This step is optional: if you have Integrated Storage, take this step, otherwise skip it.

    Code Block
    bash#> yum install onapp-store-install
    bash#> /onapp/onapp-store-install/onapp-store-install.sh
  6. Wait until two Control Panels get valid license.
  7. Ensure that all hostnames are reachable (DNS configured or /etc/hosts contains relevant data).
  8. Add public key of the root user of the main Control Panel to the authorized keys at a secondary Control Panel. And vice versa.
  9. Add public key of onapp users to root authorized keys on all hosts.
  10. Make sure the root user can log in from one node to another using SSH between both Control Panels. Confirm the authorization with the new fingerprint.
  11. Make sure onapp user can log in from both Control Panels using SSH to all hosts. Confirm the authorization with the new fingerprint.

 


Configuration on CP Side


Log in to any of the Control Panels and configure hosts, clusters and communication.

 


Configure Hosts

 



Configure Hosts

Add relevant hosts corresponding to physical infrastructure:

  1. Go to your Control Panel Settings menu.
  2. Click the HA Clusters > Hosts tab. 
  3. Click the New Host button or click the "+" button.
  4. On the screen that appears, fill in the hostname and click Submit.

 


Configure Clusters

 



Create Load Balancer, Database, Redis and RabbitMQ clusters:

  1. Go to your Control Panel Settings menu.
  2. Click the HA Clusters icon > Clusters tab. 
  3. Choose one of the optional clusters and click the appropriate button: Add Load BalancerAdd Database,Add Redis or Add Message Queue.
  4. Fill in required information:
    • Virtual IP - the virtual IP address of the cluster. This IP address should be unique
    • Net mask - mask of the network
    • Ports - cluster ports
  5.  Click Submit to add the cluster.
Note
  • Virtual IP for the Load Balancer cluster must be a public front end IP. 
  • Virtual IP for Database, Redis, RabbitMQ has to be in a data network (LAN) and can be the same (one for three clusters). 
  • Virtual IP for Cloudboot has to be the same as configured in main Settings, Cloudboot section. 
  • In case when you configure a Load Balancer, the system will skip any configured virtual IPs for daemon and UI clusters.
  • The Load Balancer cluster must be added first, then you will be able to add Database, Redis and Message Queue. 

Configure Communication

 



Configure relevant multicast channels. Two channels in different networks are recommended. 

Here you can select the way of communication among the hosts - Multicast or Unicast, by pressing the corresponding button: Switch to Unicast or Swith to Multicast. This will re-generate corosync configuration files and reload service.

To add a communication ring:

  1. Go to your Control Panel Settings menu.
  2. Click the HA Clusters icon > Communication tab. 
  3. Click the Add New Ring button or click the "+" button.
  4. Fill in the following parameters:
    • Network - the multicast network used by the hosts to communicate with each other
    • Multicast IP Address - the multicast IP address
    • Multicast Port - the multicast port 
    • TTL - time to live (only for the multicast configuration)
    • Members - the IP address of the hosts in the configuration. Fill in the IP address of the hosts separated by a comma (only for the unicast configuration)
  5. Click Save.
  6. At Settings > HA Clusters > Communication click Apply to save the changes.
Note

Please note, the you are required to add the correct IP address when configuring multicast. Adding incorrect IP address will affect the multicast configuration.

The maximum number of communication rings corresponds to the number of available NICs on hosts. For example, if all hosts have two NICs, you can configure a maximum of two communication rings.

Review and Confirmation

 



  1. Go to Settings > HA Clusters > General and review the modified configuration.
  2. After validating the configuration, click Enable.
Info
  • The HA configuration process is shown in the activity logs.
  • On Load Balancer cluster nodes OnApp will deploy reverse proxy servers.
  • On both Control Panels http and https ports will be modified from 80 and 443 to 10080 and 10443 respectively by default. This behavior can be overridden if you set additional options for the Load Balancer cluster: http_port, https_port.
  • OnApp applications on both Control Panels will be reconfigured to use Database, Redis and Rabbitmq clusters instead of local servers.
  • The OnApp interface application will be restarted on new ports.