You can manage settings for a cloud organization virtual data centers (VDCs) from the VMware Lab Platform administrator user interface. As an administrator, you can edit settings that affect only your account. Only VMware Lab Platform technical staff can modify settings that affect all customer accounts.
To view the page, click .
The Enabled, Deployment, Assignment, Tenant Deployment, and Tenant Assignment options control the deployment and assignment for the selected cloud organization VDC.
Deployment means deploying a new vApp either as a prepopulated vApp or as an on-demand deployment. An assignment means assigning an existing prepopulated vApp to an entitlement once a user starts the lab.
To display the information option, use the Manage Columns button in the lower-left corner of the page. The following settings are displayed by default.
Setting |
Description |
|---|---|
Name |
Name of the cloud. |
Cloud Org |
Name of the cloud org VDC. |
Description |
Short description provided for the cloud organization VDC. |
Tenant Deployment Enabled |
This option applies only to the customer account and does not affect other accounts using this cloud organization VDC. The settings have meaning only if Enabled is set to True and the corresponding activity is set to True. For example, Tenant Assignment only has meaning if Assignment is set to True. You can use both to deactivate deployments or assignments for a specific account without affecting the settings for other accounts. |
Tenant Assignment Enabled |
Similar to Tenant Deployment Enabled option. The settings have meaning only if Enabled is set to True and the corresponding activity is set to True. |
Tenant Maintenance Mode |
Activates or deactivates maintenance mode for the selected cloud org VDC(s). This field is specific to an account, that is, it affects only your account. This field is useful when you do not want activity in the selected cloud org VDC (for example, due to problems or other issues or an upgrade). |
Display name |
Enter and save a display name for the cloud org VDC. |
Enabled |
Indicates whether a cloud org VDC can be used. If set to True, then the system does not use the cloud org VDC for deployments or assignments regardless of any other settings. VMware Lab Platform technical staff activates or deactivates this setting. |
Deployment Enabled and Assignment Enabled |
Both are active only if Enabled has been set to True. These fields activate or deactivate an assignment or a deployment for all customer accounts. If both are set to False, the result is the same as Enabled being set to False. VMware Lab Platform technical staff activates or deactivates these settings. |
Maintenance Mode |
Activates or deactivates maintenance mode for the selected cloud org VDCs and affects all accounts. If set to True, the system does not deploy any new vApps in the cloud org VDC and does not use any existing vApps from the cloud org VDC. Only VMware Lab Platform technical staff activates or deactivates this field. This field is useful to deactivate a cloud org VDC for maintenance. |
Preshadow Enabled |
If activated, it automatically creates a shadow of a template at VCD. |
Urn |
|
Allocation Model |
|
CPU Allocated |
|
CPU Used |
|
Memory Allocated |
|
Memory Used |
|
Storage Threshold |
|
Storage Used |
|
VM Quota |
|
vCPU |
|
Cloud Groups |
|
Date Created |
Lists the date when a cloud org VDC was created. |
Last Updated |
Lists the last updated date of a cloud org VDC. |
You can also modify the fields for Urn, usage threshold, CPU allocated and used, memory allocated and used, storage threshold, and vCPU values.
You use the three vertical dots on the right for each cloud org VDCs to drain all prepops, see full details, or delete a cloud org VDCs.
Examples
Example 1: To enable assignment for a cloud org VDC, Enabled, Assignment, and Tenant Assignment must be set to True. If any one of these is set to False, then the system cannot use the cloud org VDC for assignment.
Example 2: If a cloud org VDC is to be taken out of service, then the cloud org VDC can be activated only for assignments but not for deployments. Thus, the system cannot make new deployments to the cloud org VDC. However, the system still allows the use of existing prepops on that cloud org VDC.
Example 3: If a cloud org VDC is to be brought online, then it can be activated for deployments but not assignments. Thus, starting to deploy prepops to the cloud org VDC is valid. However, the system cannot use the prepops for labs until the cloud org VDC has officially been made available.
Additional settings for cloud org vDC
Select a cloud organization from the list and click the three ellipses next to it.
Option |
Description |
|---|---|
Drain All Prepops |
Drains all prepops from the selected cloud org VDC but retains prepops for the template in other VDCs. |
