A cloud zone defines a set of compute resources for a cloud account type, such as AWS or vSphere, in a specific account region that are used when you deploy a blueprint. Cloud zones are specific to a project.
Additional placement controls include placement policy options, capability tags, and compute tags.
Placement policy drives host selection within the specified region.
default - Place compute resources on hosts randomly.
binpack - Place compute resources on the most loaded host.
spread - Place compute resources evenly on all available hosts.
Blueprints contain constraint tags to help determine deployment placement. During deployment, blueprint constraint tags are mapped to matching capability tags in cloud zones to determine which cloud zones are available for compute resource placement.
You can view and manage the computes that can be provisioned to this cloud zone. Compute tags help to further control placement. You can use tags to filter available compute resources to only those that match one or more tags, as shown in the following examples.
Computes contain no tags and no filtering is used.
Two computes contain the same tag but no filtering is used.
Two computes contain the same tag and the tag filter matches the tag used on the two computes.
You can view which projects have been configured to support workload provisioning to this cloud zone.
After you create a cloud zone, you can validate its configuration.