LocationPolicy(mapping=None, *, ignore_unknown_fields=False, **kwargs)
Configuration for location policy among multiple possible locations (e.g. preferences for zone selection among zones in a single region).
.. _oneof: https://proto-plus-python.readthedocs.io/en/stable/fields.html#oneofs-mutually-exclusive-fields
Attributes | |
---|---|
Name | Description |
locations |
MutableMapping[str, google.cloud.compute_v1.types.LocationPolicyLocation]
Location configurations mapped by location name. Currently only zone names are supported and must be represented as valid internal URLs, such as zones/us-central1-a. |
target_shape |
str
Strategy for distributing VMs across zones in a region. Check the TargetShape enum for the list of possible values. This field is a member of oneof _ _target_shape .
|
Classes
LocationsEntry
LocationsEntry(mapping=None, *, ignore_unknown_fields=False, **kwargs)
The abstract base class for a message.
Parameters | |
---|---|
Name | Description |
kwargs |
dict
Keys and values corresponding to the fields of the message. |
mapping |
Union[dict,
A dictionary or message to be used to determine the values for this message. |
ignore_unknown_fields |
Optional(bool)
If True, do not raise errors for unknown fields. Only applied if |
TargetShape
TargetShape(value)
Strategy for distributing VMs across zones in a region.
Values: UNDEFINED_TARGET_SHAPE (0): A value indicating that the enum field is not set. ANY (64972): GCE picks zones for creating VM instances to fulfill the requested number of VMs within present resource constraints and to maximize utilization of unused zonal reservations. Recommended for batch workloads that do not require high availability. ANY_SINGLE_ZONE (61100880): GCE always selects a single zone for all the VMs, optimizing for resource quotas, available reservations and general capacity. Recommended for batch workloads that cannot tollerate distribution over multiple zones. This the default shape in Bulk Insert and Capacity Advisor APIs. BALANCED (468409608): GCE prioritizes acquisition of resources, scheduling VMs in zones where resources are available while distributing VMs as evenly as possible across allowed zones to minimize the impact of zonal failure. Recommended for highly available serving workloads.