Installing OnApp for vCloud Director is a pretty straightforward process. Here’s a quick guide to get you started.
We offer a range of different installation options for OnApp, including both free and paid installs – but you can also install OnApp for vCD yourself.
This guide takes you through the install process, and then how to follow up with billing plan configuration, so you’re in a position to start onboarding customers.
OnApp server prerequisites
First let’s check the server requirements for your install.
|RAM:||16GB (32GB+ recommended for larger environments)|
|OS:||CentOS 6.x 64bit|
|Network:||External access outbound with access to vCloud Director and vCenter|
Installing the OnApp CP
1. Download and install the latest OnApp repository:
2. Install the OnApp installer package:
# yum install onapp-cp-install
3. Update the CentOS base components:
# /onapp/onapp-cp-install/onapp-cp-install.sh -y
4. Run the OnApp installer:
# /onapp/onapp-cp-install/onapp-cp-install.sh -i <OnApp Server IP>
Once the installer has finished running, you will be able to access the OnApp UI via your choice of web browser by accessing the IP: http://<OnApp Server IP>. You can login with the default credentials as follows:
When you log in for the first time, you will be prompted to enter the license key that will be provided to you by your OnApp sales rep, or you can retrieve the key yourself by logging in to our dashboard: https://admin.onapp.com
Once the license has been added, it will take around 5-10 minutes to confirm and then you will be able to access the full OnApp user interface.
Note: Ensure that your OnApp controller can access our licensing server licensing.onapp.com over port 443
Integrating vCloud Director into OnApp
Asuming your vCloud Director environment meets all of our prerequisites we can immediately add this in to your OnApp environment.
1. Retrieve OnApp’s RabbitMQ details and add these to vCloud Director
[root@OnApp ~]# cat /onapp/interface/config/on_app.yml |grep rabbit rabbitmq_login: rbtvcd rabbitmq_password: EO!uyJZKZi rabbitmq_vhost: "/" rabbitmq_host: 127.0.0.1 rabbitmq_port: 5672
The login and password from this file should be added to the vCloud Director AMQP Settings (via System > Administration > Extensibility > ‘AMQP Broker Settings’).
Note: Ensure that “Enable Notifications” is enabled!
The AMQP host should be the IP address that vCD can communicate with OnApp on and set the exchange to a name of your choosing. Ensure the “Test AMQP Connection” works correctly and save the settings.
2. Connect to the OnApp UI
Navigate to Settings > Compute Resources > Add New Compute Resource:
Add the details of your vCloud Director environment as follows:
|Label:||The name of your vCloud Director environment that your end users will see.|
|Compute resource type:||vcloud|
|Compute zone:||You can leave the default zone selected or choose a specific zone if you have created one already.|
|API URL:||The base URL to your vCloud Director environment (must be accessible by the OnApp server)|
|Login:||A system administrator level user inside of your vCloud Director instance.|
|Password:||The password for the above user.|
|Exchange:||The exchange name you specified in the vCloud Director AMQP configuration.|
Once this information has been saved, it will trigger the import process of all of the assets from vCloud Director into OnApp. You can monitor this import process via the SSH console:
# tail -f /onapp/interface/log/production_vcloud.log | grep import
3. Once this process has completed, stop the OnApp Daemon.
[root@OnApp ~]# service onapp stop Stopping OnApp Engine... 3 pids found: 3494, 27700, 26910 Terminating 3494 Terminating 27700 Terminating 26910 [ OK ] Stopping VNC Proxy: [ OK ] Stopping SSH Agent: [ OK ]
4. And then start it back up again.
[root@OnApp ~]# service onapp start Starting SSH Agent: [ OK ] Starting OnApp Engine... Spawning engine... Spawned 5540 [ OK ] Starting VNC Proxy: [ OK ]
5. The next step is to confirm the synchronisation is working correctly.
You can do this by checking the following log file and confirming there are keep-alive signals being sent every minute or so.
# tail -f /onapp/interface/log/production_vcloud.log
You should see entries like this if everything is working OK:
[root@OnApp ~]# tail -f /onapp/interface/log/production_vcloud.log 2016-12-02 10:56:37 +0000: true.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.a93c9db9-7471-3192-8d09-a8f7eeda85f9.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.com.vmware.vcloud.event.session.login 2016-12-02 10:56:37 +0000: true.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.a93c9db9-7471-3192-8d09-a8f7eeda85f9.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.com.vmware.vcloud.event.session.authorize 2016-12-02 10:57:37 +0000: true.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.a93c9db9-7471-3192-8d09-a8f7eeda85f9.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.com.vmware.vcloud.event.session.login 2016-12-02 10:57:37 +0000: true.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.a93c9db9-7471-3192-8d09-a8f7eeda85f9.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.com.vmware.vcloud.event.session.authorize 2016-12-02 10:57:37 +0000: true.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.a93c9db9-7471-3192-8d09-a8f7eeda85f9.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.com.vmware.vcloud.event.session.login 2016-12-02 10:57:37 +0000: true.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.a93c9db9-7471-3192-8d09-a8f7eeda85f9.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.com.vmware.vcloud.event.session.authorize 2016-12-02 10:58:37 +0000: true.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.a93c9db9-7471-3192-8d09-a8f7eeda85f9.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.com.vmware.vcloud.event.session.login 2016-12-02 10:58:37 +0000: true.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.a93c9db9-7471-3192-8d09-a8f7eeda85f9.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.com.vmware.vcloud.event.session.authorize 2016-12-02 10:58:37 +0000: true.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.a93c9db9-7471-3192-8d09-a8f7eeda85f9.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.com.vmware.vcloud.event.session.login 2016-12-02 10:58:37 +0000: true.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.a93c9db9-7471-3192-8d09-a8f7eeda85f9.b6542aa4-22f2-42ee-a481-7e9970d4d2b1.com.vmware.vcloud.event.session.authorize
The integration of vCloud Director is now complete. There are a few more configuration steps that are recommended to do next, to ensure that everything will work as expected.
Basic Billing Plan Configuration
In order to utilize all of the vCloud Directorassets that have been imported, we need to do some basic billing plan configuration first. We have to ensure that the User and Company billing plans that your customers will use can access the correct vCloud Director resources.
(For more information about how billing plans are used in vCloud Director, please refer to my previous blog post on vCD billing plans)
1. Navigate to the Billing > Plans section of the OnApp UI and open the “default billing plan”.
2. Then click the “Company Plans” tab and open the “default company billing plan”.
In both of these plans, under the following 3 sections, you should add all resources that you can.
LIMITS & PRICING FOR COMPUTE ZONES
LIMITS & PRICING FOR DATA STORE ZONES
LIMITS & PRICING FOR NETWORK ZONES
Note, at this stage you can leave the defaults and there is no need to enter pricing information: this can be changed at a later date.
You should also ensure that any users that have automatically imported into OnApp from vCD are using the correct User Billing Plan.
At this stage, everything should be ready to go. You are now ready to onboard new customers.There’s a handy guide for onboarding here.