Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow instance placement policies to be attached to a VM #258

Closed
wkharold opened this issue Aug 29, 2022 · 1 comment
Closed

Allow instance placement policies to be attached to a VM #258

wkharold opened this issue Aug 29, 2022 · 1 comment
Labels
enhancement New feature or request Stale

Comments

@wkharold
Copy link
Contributor

TL;DR

An instance placement policies allows GCP users to control where VM instances are physically located relative to each other within a zone. Two placement policies are available, spread, and compact. The latter, compact, is particularly important for HPC workloads where minimizing inter-VM communication latencies is critical.

This feature will allow users to specify a placement policy to be attached to a VM instance

Terraform Resources

Resource policies are specified by the Terraform Resource: https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_resource_policy

The [google_compute_instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_instance) resource supports specification of `resource_policies` (a max of 1 resource policy is currently supported). It's attributes are supported by the [google_compute_instance_from_template](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_instance_from_template) resource.

Detailed design

Add a new `resource_policies` variable. It should be a list of strings. Those strings represent either resource policy short names or self_links of resource policies to attach the the instance. Since only one resource policy per instance is currently supported by the provider, the length of the list will be checked and an error raised if it is > 1.

Additional information

No response

@wkharold wkharold added the enhancement New feature or request label Aug 29, 2022
@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Oct 28, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Stale
Projects
None yet
Development

No branches or pull requests

1 participant