Prepare Servers & Install OnApp

The Control Panel server hosts the OnApp user interface and database, as well as handles all cloud management processes. You do not need to set up a separate database server for your OnApp installation. OnApp provides full compatibility of Control Panel UI with desktop Google Chrome and Firefox web browsers where JavaScript is enabled. Currently, mobile and tablet browsers are not supported.

To install Control Panel server, perform the following procedure:

  1. Install CentOS 7x64 minimal on the server you will use for your OnApp cloud Control Panel.
  2. On that server, configure eth0 for the public Internet:
    • In a lab environment, set eth0 to DHCP to allocate the IPs that will be used to manage OnApp.
    • In a production environment, this should be the internal or external IP addresses that users will use to manage OnApp.

    Instead of ethX, network adapter devices may be named enoX in CentOS 7.

  3. Configure eth1 to be used for the OnApp Management Network. This should be an internal IP range that OnApp will use to manage compute resources in your cloud.

  4. Update your OS packages:

    yum -y update
  5. Add the OnApp latest repository to your OnApp Control Panel:

    bash# rpm -Uvh
  6. Install the OnApp Control Panel installer package:

    bash#> yum install onapp-cp-install
  7. Run the OnApp installation script:

    /onapp/onapp-cp-install/ -i <IP Address of eth1 (Management Interface)>, 

    Answer 'yes' to the prompts when asked

    Perform the following step (8) only if you plan to deploy Accelerator.

  8. If you plan to configure an Accelerator, run the following command:

    • For all compute resources:

      rake hypervisor:messaging:configure
    • For certain compute resources only:

      rake hypervisor:messaging:configure['']

      To perform the configuration for a number of compute resources, separate their IP addresses with a space.

      The command above runs on compute resources that are online. If some compute resources are offline, you should run the command again when they are online. The rabbitmq_host parameter in the on_app.yml file should contain the real IP address of a server with RabbitMQ installed. The rabbitmq_host parameter should not be set to 'localhost' or ''. The server with RabbitMQ installed should be available from the compute resources. For information on manual configuration for Accelerator, refer to RabbitMQ Configuration for Accelerator.

  9. Install the OnApp Storage packages:

    yum install onapp-ramdisk-centos6-kvm
    yum install onapp-ramdisk-centos7-kvm
    yum install onapp-ramdisk-centos6-xen
    yum install onapp-ramdisk-centos7-xen
    yum install onapp-ramdisk-centos7-default
  10. Run the OnApp Storage configuration script:


    This will prompt you for a password. Please enter a secure password when prompted.

  11. Restart the OnApp daemon:

    service onapp restart
  12. Once the daemon has reloaded, you’ll be able to log in to the OnApp UI: go to the IP address of the OnApp Control Panel server in a browser and log in with the default credentials: admin/changeme

  13. You will need to enter a license key – if you have not been provided one already, please contact your account manager. Enter the provided license key when prompted and save – wait 10 minutes to have full access to the OnApp GUI.

  14. We now need to enable CloudBoot and OnApp storage. Browse to Settings > Configuration and scroll about half way down the page to the CloudBoot and OnApp Storage sections.

    14. Configure the CloudBoot section – ensure that CloudBoot is enabled and then set the following to the Management Interface IP of your OnApp Control Panel node:

    • Static config target 

    • CP server CloudBoot target

    • CloudBoot Domain Name Servers

     15. Configure the OnApp Storage section – ensure that OnApp Storage and Use local read path are both enabled. If your switch does not have multicast support,  you will need to check the Use unicast button as well.

It is strongly recommended that you use a multicast-enabled network infrastructure for performance reasons.