OnApp has developed a new integration between the OnApp Infrastructure-as-a-Service platform and VMware vCloud Director. Starting with OnApp 4.2 you can import multiple vCDs into OnApp.
The new integration enables existing vCloud Director installations to use the OnApp CP as their front-end UI. With the new integration, OnApp:
Provide new UI options for vCloud Director users (VS monitoring)
Expand vCloud Director capabilities with integrated billing plans
- Control Panel with vCloud Director integration should have at least 3 onappd instances (vcloud L1, vcloud L2 and another one).
- Currently OnApp supports only default vCD roles. These roles are mapped using the label, therefore, please do not change the labels of the default user roles in vCloud Director. Users with custom roles are not imported into OnApp.
OnApp and vCloud Director connection is supported with RabbitMQ. To integrate OnApp with the vCloud Director, you must specify RabbitMQ credentials both on the OnApp CP and the vCloud Director (in beta version, RabbitMQ will be delivered with the OnApp RPMs. RabbitMQ will be synchronizing OnApp and the vCloud Director: it will get the list of actions happen in the vCD and report it to the CP).
After that, add the vCloud Director instance as an OnApp compute resource (vcloud type) and specify the vCloud Director URL and vCloud Director system admin credentials. After that, all the existing vCloud Director resources will be shown in OnApp.
Starting with OnApp 5.5 version, vCloud administrator is imported into OnApp as "System owner" together with VSs and vApps, which belong to this user. "System owner" user can not be edited in OnApp, but cloud administrator has a possibility to reassign "System owner"'s VSs or vApps to other owners.
At the moment, importing a vCloud Director into OnApp includes the following components:
vCloud Director instance (as an OnApp compute resource)
Organizations (added as OnApp user groups)
- Networks (organization vDC networks, external networks and vApp networks)
- Storage policies
Users and their roles (except system administrators)
The import of other vCloud Director components into OnApp is scheduled for the following releases.
vCloud Director instance
Virtual servers, built on a guest operating system, can be used to install and run software compatible with that operation system.
VSs between Vcloud Director and Vcenter are mapped using moref ID.
VApp consists of one or more virtual servers that communicate over a network and use resources and services in a deployed environment.
A vApp template is a virtual server image that is loaded with an operating system, applications, and data. VApp templates are added to catalogs.
A catalog is a container for vApp templates and media files. You can view the list of catalogs at OnApp Control Panel > Catalogs menu of your OnApp Cloud.
Edge Gateway is a virtual router for organization vDC (virtualDataCenter) networks. You can view the list of edge gateways (together with firewall rules, NAT rules and VPN service) at OnApp Control Panel > Edge Gateways menu of your OnApp Cloud.
vCloud Director Resource Pools
Resource pool is an allocation model which determines how and when the provider virtual data center compute and memory resources are committed to the organization virtual data center. There are three types of resource pools:
- Allocation Pool
- Reservation Pool
Orchestration models enable you to provide your customers with a ready environment which they can use to deploy virtual servers.
vCD Organizations are displayed in OnApp as user groups.
Company Billing Plans
Company billing plan is a set of limits and prices for the resources used by vCloud Director organizations imported as user groups into OnApp.
External, organization and vApp network types, as well as network pools, are imported into OnApp as networks and network zones of the VPC type. Below are the details on how different vCD networks are imported:
Each network pool is imported into OnApp as two network zones:
- Isolated network zone - this zone contains isolated organization and vApp networks imported from vCloud Director.
- Routed network zone - this zone contains routed organization and vApp networks imported from vCloud Director.
External networks are imported both as a network zone and as a network within that zone. Importing external networks as network zones enables administrators to configure billing for external network usage.
Organization networks are imported into OnApp as Org networks and are associated with a network zone. Depending on the type of the organization network, it will be associated with a certain zone.
- Routed organization networks are associated with their network pool imported as a routed network zone.
- Isolated organization networks are associated with their network pool imported as an isolated network zone.
- Direct organization networks are associated with their external network imported as a network zone.
vApp networks are imported into OnApp as networks and are associated with a network zone. Depending on the type of the vApp network, it will be associated with a certain zone.
- Routed vApp networks are associated with their network pool imported as a routed network zone.
- Isolated vApp networks are associated with their network pool imported as an isolated network zone.
- Direct vApp networks are associated with their parent organization network and are assigned to the network zone to which their parent networks are assigned. So depending on the parent network, they can be imported to Isolated, Routed, or External network zone.
Provider storage policies are imported to OnApp as data store zones of the VPC type. Storage policies appear in the OnApp UI as data stores. You can select them during vApp creation. To view storage policies and the list of disks and VSs associated with them, go to the Settings > Data Stores menu.
Users are imported with their existing roles. Currently OnApp supports only default vCD roles. These roles are mapped using the label. Users with custom roles are not imported into OnApp. OnApp imports the username and creates that user in OnApp. From that point forward, changes to the user should be made inside OnApp. OnApp will generate a random password for each imported user. The user will be emailed with the instructions to change this password to be able to log into OnApp. After the log in, user will be asked to confirm the vCloud Director password.
Also vCloud users can log in using SAML authentication. The process is the same as for usual OnApp users.