Which are the requirements for OnApp's vCloud integration?
OnApp 6.1 and later
In order to install OnApp's vCloud integration there are a number of requirements that you should be aware of first.
Hardware / Infrastructure
You will need to deploy the OnApp Control Panel Server. You can either use our OVA (https://onapp.com/2020/09/21/onapp-vcenter-ova-set-up-control-panel/), or you can build a server with the following recommended minimum specifications and then follow the install guide (https://docs.onapp.com/vcd/latest/get-started/onapp-with-vmware-cloud-director-installation-guide):
- 4 CPU Cores
- 16GB RAM (32GB+ recommended)
- 100GB Disk (200GB+ recommended)
- CentOS 7.x minimal x64 (Make sure language is set to English and selinux is disabled)
For the network connectivity, it is recommended that one interface is used for public traffic (this will need to access the OnApp licensing server) and the other interface has a connection to the same network as your vCD management traffic. If you prefer to have only one interface and use NAT, that is fine as well.
An example diagram of how you should set up your OnApp vCD Integration is as follows. If you have any questions about this, please get in touch.
There are some requirements within vCD that are needed in order to deploy OnApp.
- Your vCloud Director must be version 9.1 or later. (https://docs.onapp.com/vcd/latest/get-started/vcloud-director-integration-details)
- All users require a full name and unique e-mail address set in order to be imported into OnApp.
Public Console Access
If you want users to have access to the MKS/VMRC console within OnApp then you will need to use a publicly routable IP address/domain name as the "vCloud Director public console proxy address" within your vCloud Director settings.
You can lock this IP/domain access down as required, however, it will need communication to the OnApp Control Panel over port 902 (for MKS) and 443 (for VMRC). For more information, refer to the vCenter Virtual Server Console page.
Statistics reporting into OnApp
In order for performance and resource reporting to be shown within OnApp, we require a connection between OnApp and your vCenter(s) and ESXi host(s) over port 443.
A detailed list of all communication between the different systems is listed below, including a brief description. For more information, refer to the Required Ports page.
This is required so your OnApp control panel server can communicate with the OnApp licensing dashboard.
|OnApp CP||vCloud Director||443||
HTTPS communication to consume the vCloud Director API.
|OnApp CP||Public Internet||25||
For mail notifications sent outbound from your OnApp Control Panel server.
|OnApp CP||vCenter Server(s) and ESXi Host(s)||443||
HTTPS communication to pull Stats for VS and Edge Gateway Interfaces.
|vCloud Director||OnApp CP||5672||
AMQP Communication to RabbitMQ for Bi-Directional synchronization.
HTTP/HTTPS communication for the user to access OnApp Web Interface.
|Users||vCD Console Proxy||443||
HTTPS communication for the user to access the virtual console of there virtual machines.
herein or at this place; where the speaker or writer isMore (Definitions, Synonyms, Translation)