Page Comparison

...

This section describes the basic details to enter when creating a virtual datacenter. The following sections describe further configuration.

...

Field	Description
Name	The name of the virtual datacenter
Location	The datacenter or public cloud region where virtual appliances will be deployed. You can select any of your allowed locations
Hypervisor	The type of the hypervisor for the virtual datacenter. This option will not display if there is only one choice.
Network	Default: Create a VLAN (default private or external) in the pre-configured range Custom Private: Create a custom private VLAN (see form below)

If your environment supports NAT you may also be able to select the IP address for the default SNAT rule

Field	Description
NAT network	Optionally, select the NAT network to use for the default SNAT rule
Default NAT IP	Optionally, select the NAT IP address for the default SNAT rule for the virtual datacenter

...

Create a virtual datacenter with custom networks

...

To create a Custom private network, complete the Network section of this dialog.

...

Field	Description
Name	The name of the

...

network to create
Netmask	The network mask CIDR
Network address	The network address
Address range	The address space that the virtual datacenter can use in CIDR format. This space will define the virtual network and the private networks will be subnets within this address space.
Gateway	The IP of the gateway of the

...

network
Availability zone	The availability zone where VMs attached to this network will deploy
Primary DNS	The primary DNS of the network
Secondary DNS	The secondary DNS of the VLAN
DNS suffix	The DNS suffix for the VLAN

To manage the VLANs or other networks of your virtual datacenter, go to Virtual datacenters → Network. See Manage networks.

...

You cannot have a hard limit only
Soft limits must always be less than or equal to hard limits
When a limit is equal to 0, it means that there is no limit to resource usage at this level
When editing limits, you cannot set the hard limits below the existing resource usage, except for Local hard disk

...

Limit	Checked at	Description
Memory	Deployment	Total amount of RAM that may be used by VMs including hardware profiles assigned to VMs
Virtual CPUs	Deployment	Total number of virtual CPU cores that may be used by VMs including hardware profiles assigned to VMs
Local hard disk	Deployment	Total size of hard disk that may be used by VMs on hypervisor datastores and in public cloud providers
External storage	Configuration	Total size of external storage that may be created for VMs
VLANs	Configuration	Total number of private

VLANs

networks that may be defined.
Note that a private

VLAN

network is automatically created for every VDC, so this limit may restrict the number of VDCs that users can create
Public /floating/ NAT IPs	Configuration	Total number of public IPs, floating IPs (in public cloud), and NAT IPs that may be used
Virtual machines	Deployment	Total number of VMs that users can deploy in the location using their allowed resources
DR protected VMs	Configuration	Total number of VMs that may be protected with the disaster recovery service.

In public cloud regions, the platform
does not use DRaaS features or limits.

...

Consider a virtual datacenter with a soft limit of 1 virtual CPU and a hard limit of 4 virtual CPUs.

The user will exceed the soft limit if they deploy a virtual appliance with more than 1 CPU in the virtual datacenter.
The user will exceed the hard limit if they attempt to deploy a virtual appliance with more than 4 CPUs in the virtual datacenter.

Soft limits message

A soft-limits message popup will allow the user to to acknowledge the message and continue with the operation.

By default, the message will provide details of the limits, used, and requested resources.

For example, the limits are 5 CPUs, the users have 2 CPUs in deployed VMs, and they have requested 3 more CPUs. Soft limit exceeded Image Removed

...

The platform will also display this type of message when the users exceed soft limits at another level, for example, enterprise, enterprise in provider, or enterprise in location.

Hard limits message

A hard-limits message pop-up will allow the user to acknowledge the message and terminate the operation.

By default, the message will provide details of the limits, used, and requested resources.

For example, the limits are 5 CPUs, the users have 5 CPUs in deployed VMs, and they have requested 1 more CPU. Because the user will exceed the hard limit, the platform will not allow the user to obtain 1 CPU. Hard limit exceeded Image Removed

...

The platform will also display this type of message when the users exceed soft limits at another level, for example, enterprise, enterprise in provider, or enterprise in location.

...

Set virtual datacenter defaults

When you create a virtual datacenter, you can set some defaults according to your platform configuration.

...

Field	Description
Default datastore tier	Select the default disk service level for

your non-persistent virtual machine

VM disks on the hypervisor datastore.
This is the default datastore tier for the virtual datacenter.

To use your cloud provider's default tier, select "Configured by location"
Or select a default tier, according to the available service levels

To clear the current tier, click the black x symbol beside the tier name

Subnet

In Google Cloud Platform you must select a default subnet to deploy VMs
if you do not manually configure an IP address

After you create the virtual datacenter, you can edit it the default values.

...

Go to myCloud → Virtual datacenters
Create, edit, or onboard a virtual datacenter
Go to Roles
Image RemovedImage Added
For the Role, select a more restrictive role to replace user roles within this VDC.
For example, to give users read-only access, select the ENTERPRISE_VIEWER role
To create exceptions to the VDC role:
1. Select a Username and an exception Role for the user
2. Click Add
When you finish creating or editing the virtual datacenter, click Save