Orchestrating vCloud Air and vCloud Director Deployments¶
Do you use vCloud Air as the VMware public cloud or vCloud Director as your VMware private cloud? Connect them in ElasticBox for complete workload automation. Once you define the automation of your workloads in ElasticBox, you can launch them to other clouds as well as VMware. vCloud Air and vCloud Director are available in ElasticBox through the vCloud Director provider, which supports vCloud Director API version 5.1 and above.
In this article:
- Connect vCloud Air or vCloud Director in ElasticBox
- Deploy to vCloud Air or vCloud Director
To orchestrate vCloud Air and vCloud Director deployments through ElasticBox, you need the following setup:
Connect vCloud Air or vCloud Director in ElasticBox¶
Follow these steps to add a provider in ElasticBox that integrates with your virtual data center in vCloud Air public cloud or vCloud Director private cloud. Each provider connects to the virtual data center in that specific location.
In ElasticBox, on the Providers page, click New Provider.
Select VMware vCloud Director and enter the credentials as given.
- vCloud Director. Enter the URL to access the vCloud Director portal.
- vCloud Air. Enter the login URL followed by the compute API endpoint in this format, <vCloud_air_login_URL>/api/compute. Example: https://us-california-1-3.vchs.vmware.com/api/compute/
- Organization. Enter the organization name or GUID.
- For vCloud Air, select the virtual data center to see the org name in the URL as in this example: ?orgName=c946391d-a811-40c5-b39e-df8bf2b88917.
- For vCloud Director, enter system if the user is a global administrator.
Username. Enter the username to log in to vCloud Air or to the vCloud Director portal.
Password. Enter the password for the vCloud Air or vCloud Director portal.
Deploy to vCloud Air or vCloud Director¶
Create a deployment policy to encapsulate parameters required to deploy Linux or Windows vApps through the vCloud Air or vCloud Director provider in ElasticBox. At deploy time, ElasticBox auto provisions vApps, one template per VM, and orchestrates workload automation on them.
Note: Auto provisioning may fail if you specify virtual CPUs, memory, and virtual disk capacity that exceeds the limit in your virtual data center.
Edit the deployment policy to set the following parameters for deploying to vCloud Air or vCloud Director.
|Organization||Select the organization in vCloud Air or vCloud Director. The organization is a virtual container for vApp templates, vApps, media images, and disks.|
|Catalog||Select the catalog that contains the vApp template for deployment. The catalog stores vApp templates and media files. Select from shared, private, and public catalogs that your organization can access.|
|vApp Template||Select a vApp template from the catalog. VMs imported as OVFs then uploaded as templates are also listed.|
|Customization Password||Optionally, provide a custom VM administrator password. If you leave this empty, the default administrator password from the template applies.|
|Instances||Specify the number of instances to spawn from the same template.|
|Virtual Data Center||Select the virtual data center from vCloud Air or vCloud Director.|
|Network||Select the network for the virtual data center.|
|Virtual CPUs||Specify the number of CPUs. See the VMware docs for vCloud Air VM CPU limit.|
|Memory||Specify the virtual RAM in GB. See the VMware docs for vCloud Air VM RAM limit.|
|Disk||Specify the storage capacity in GB. See the VMware docs for vCloud Air VM storage limit.|