ansible-collections/google.cloud
1
0
Fork 0
mirror of https://github.com/ansible-collections/google.cloud.git synced 2025-07-28 07:31:29 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Placement policy support for Compute Instance (#3256) (#194)

Browse source 
* Revert "Revert "Placement policy support for Compute Instance (#3217)" (#3250)"

This reverts commit 18d6446fcf9284ac5562d1693877df1c75cc28a2.

* Auto restart false, us central a

* Create two instances during collocate test

* Add note on collocation and vm_count

Signed-off-by: Modular Magician <magic-modules@google.com>
This commit is contained in:
The Magician 2020-04-15 14:42:58 -07:00 • committed by GitHub
commit 1c3481e2c3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 118 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

28
plugins/modules/gcp_compute_resource_policy_info.py
View file

@ -242,6 +242,34 @@ resources:
- Whether to perform a 'guest aware' snapshot.
returned: success
type: bool
groupPlacementPolicy:
description:
- Policy for creating snapshots of persistent disks.
returned: success
type: complex
contains:
vmCount:
description:
- Number of vms in this placement group.
returned: success
type: int
availabilityDomainCount:
description:
- The number of availability domains instances will be spread across. If
two instances are in different availability domain, they will not be put
in the same low latency network .
returned: success
type: int
collocation:
description:
- Collocation specifies whether to place VMs inside the same availability
domain on the same low-latency network.
- Specify `COLLOCATED` to enable collocation. Can only be specified with
`vm_count`. If compute instances are created with a COLLOCATED policy,
then exactly `vm_count` instances must be created at the same time with
the resource policy attached.
returned: success
type: str
region:
description:
- Region where resource policy resides.