Install Control Panel Server
To install the Control Panel server, run the following procedure:
Update your server:
# yum update
Download the OnApp YUM repository file:
# rpm -Uvh http://rpm.repo.onapp.com/repo/onapp-repo-7.0.noarch.rpm
Install the OnApp Control Panel installer package:
# yum install onapp-cp-install
(Optional) You can set custom configuration options for Control Panel. It is important to set custom values before the installer script runs.
Run the Control Panel installe
For CentOS 7:
# /onapp/onapp-cp-install/onapp-cp-install.sh -i SNMP_TRAP_IPS
6. Install CloudBoot dependencies:
Install CloudBoot default ramdisk:
# yum install onapp-ramdisk-centos7-default
Depending on a compute resource type, you should install onapp-ramdisk-DISTRO-FLAVOR package(s) where:
DISTRO: centos7 FLAVOR: kvm
Depending on the need compute resource type(s), install only the corresponding package(s):
# yum install onapp-ramdisk-centos7-kvm
7. Run the following utility to configure and customize ramdisks:
# /onapp/onapp-store-install/onapp-store-install.sh
8. Install an OnApp license to activate your Control Panel. Enter a valid license key via the OnApp UI. Your default OnApp credentials are admin/changeme. You can change a password via the Control Panel > Users menu.
9. Restart the OnApp service:
# service onapp restart
10. If you plan to configure an Accelerator, run the following command:
For all compute resources:
cd /onapp/interface # rake hypervisor:messaging:configure
For certain compute resources only:
cd /onapp/interface # rake hypervisor:messaging:configure['11.0.50.111 11.0.50.112']
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 '127.0.0.1'. 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.
Perform the steps from 11 to 13 if there are compute resources added in the cloud.
11. Generate SSH keys that OnApp requires for you to access various elements of the cloud. The script provided generates and transfers keys as necessary. The script needs to be run on your Control Panel server. It overwrites any keys that already exist, so if you have custom keys already installed, you need to add them again after running the script. You need to provide your login details to various servers during the script execution. Please follow the onscreen instructions.
12. If you install a new compute resource, connect to your Control Panel server via SSH, download, and run the script:
# wget http://downloads.repo.onapp.com/install-all-keys.sh # /bin/sh install-all-keys.sh
Note that the script is applicable only if you configure your first compute resources in the cloud. If you already have some existing compute resources and install new ones, the script sets new SSH keys to all the compute resources, both new and existing.
13. If you add additional compute resources to an existing cloud, update the authorized_keys
file by running the following script on the Control Panel server:
# ssh-copy-id -i /home/onapp/.ssh/id_rsa.pub root@HV_HOST_IP
Perform the following step (14) if you do not plan to install a dedicated backup server.
14. Mount the locations for templates and backups. If you do not have a dedicated backup server, you must mount your template and backup repositories to compute resources. If your template and backup repositories are located on the Control Panel server, you can mount them as follows:
Add the repositories to /etc/exports
on the Control Panel server and then restart the NFS service:
# /onapp/templates 192.168.10.0/24(rw,no_root_squash) # /onapp/backups 192.168.10.0/24(rw,no_root_squash)
15. After you installed the Control Panel server, configure your Cloud Settings.
After the configuration is completed, Control Panel will be available in both http and https protocols. For security reasons, we recommend either closing port 80 or opening port 443. This port is used for secure web browser communication. Data transferred across such connections are highly resistant to interception. Moreover, the identity of the remotely connected server can be verified with significant confidence.
If you use a time zone with 30-minute or 45-minute offsets, you need to modify the configuration file /etc/crontab and change the startup time (rake vm:generate_hourly_stats) from 0th minute to 30th or 45th minute, depending on a time zone.
In the script, you should replace0 * * * * onapp cd /onapp/interface; RAILS_ENV=production rake vm:generate_hourly_stats
with30 * * * * onapp cd /onapp/interface; RAILS_ENV=production rake vm:generate_hourly_stats