OnApp for VMware vCenter: technical information

DocumentationRelease notes

OnApp improves vCenter automation, enables multi-tenant self-service with fine control over access, permissions and billing, and enables you to manage multiple vCenter environments through a single portal.

OnApp manages VMs hosted within a VMware vSphere environment by connecting to a vCenter server.  The OnApp components can be installed on virtual machines within this environment if required. You can add OnApp to new or existing vCenter environments.

OnApp manages VMs hosted within a VMware vSphere environment by connecting to a vCenter server.

Hardware requirements

To use OnApp for vCenter, you will need to deploy a server that the OnApp software will be installed on – a “Control Panel Server”. These are the minimum and recommended specs:

To use OnApp for vCenter, you will need to deploy a server that the OnApp software will be installed on

Control Panel Server

  Minimum Recommended
Processor 4 cores 8 cores
Memory 16GB 32GB
Disk 100GB 250GB
Network Adapters 1Gbps 1Gbps
Operating System CentOS 7 x64 CentOS 7 x64

 

Template Server (optional)

The OVAs that OnApp uses to build virtual machines can either be stored on the OnApp Control Panel Server, or on a dedicated Template Server. These are the minimum and recommended specs for a dedicated Template Server:

 

  Minimum Recommended
Processor 2 cores 4 cores
Memory 8GB 16GB
Disk 100GB 250GB
Network Adapters Dual port 1Gbps Dual port 1Gbps
Operating System CentOS 7 x64 CentOS 7 x64

 

vCenter requirements

The OnApp Control Panel (CP) server communicates with vCenter over the OnApp management network.

These are the requirements for vCenter integration with the OnApp Control Panel:

  • VMware vCenter 6 or 6.5
  • VMware vCenter data centre with one or more clusters
  • ESXi servers must already be added to the cluster inside of vCenter
  • Ensure that the Control Panel Server has access to the management network used by vCenter and all of the ESXi servers in the cluster
  • One or more DVswitch is required, as we do not recognize host-only networks

PLEASE NOTE: when using OnApp’s vCenter integration, end users will be able to build virtual machines on any cluster or datacentre within each vCenter instance.

 

The OnApp Control Panel (CP) server communicates with vCenter over the OnApp management network.

Networking requirements

Below is the list of communication types that need to take place between the OnApp Control Panel Server and external networks.

Networking requirements

 

Source Destination Port Details
OnApp CP licensing.onapp.com 443 This is required so your OnApp control panel server can communicate with the OnApp licensing dashboard.
OnApp CP Public Internet 25 For mail notifications sent outbound from your OnApp Control Panel server.
OnApp CP vCenter Server 443 Communication between OnApp and vCenter
End Users OnApp CP 80/443 HTTP/HTTPS communication for users to access the OnApp GUI.

Network example 1

Using a flat management network for OnApp, vCenter and ESXi hosts

Network example 2

Using separate management networks for vCenter and OnApp.

More detail

Latest updates

Talk to an expert