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

add cpu options support via cpu_core_count and cpu_threads_per_core #4490 #5159

Merged
merged 2 commits into from
Jul 21, 2018

Conversation

brokenbot
Copy link

Fixes #4490

Changes proposed in this pull request:

  • adds optional attribute cpu_core_count to set CpuOptions.CoreCount
  • adds optional attribute cpu_threads_per_core to set CpuOptions.ThreadsPerCore

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccAWSAvailabilityZones'

...

@ghost ghost added the size/M Managed by automation to categorize the size of a PR. label Jul 11, 2018
@bflad bflad added enhancement Requests to existing resources that expand the functionality or scope. service/ec2 Issues and PRs that pertain to the ec2 service. labels Jul 11, 2018
Fixed Type in TestInstanceCpuThreadsPerCoreSchema
@ghost ghost added the size/M Managed by automation to categorize the size of a PR. label Jul 11, 2018
@jen20
Copy link
Contributor

jen20 commented Jul 21, 2018

Hi @brokenbot! Thanks for opening a pull request. I've gone through and cleaned up a couple of typos in the docs and merged this, it should appear in the next release of the AWS provider.

@jen20 jen20 merged commit 24c99c0 into hashicorp:master Jul 21, 2018
@bflad bflad added this to the v1.29.0 milestone Jul 26, 2018
@bflad
Copy link
Contributor

bflad commented Jul 26, 2018

This has been released in version 1.29.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

@cskalyan
Copy link

cskalyan commented Aug 3, 2018

I have been trying to use these arguments cpu_options and cpu_threads_per_core. When terraform apply fails for the first time some reason and when I execute terraform apply again, it is destryoing the existing instance and creating a new instance. Without cpu_options and cpu_threads_per_core, Instance does not get destroyed.

@bflad
Copy link
Contributor

bflad commented Aug 3, 2018

@cskalyan I'd suggest opening a new bug report issue with all the relevant details from the issue template so we can further troubleshoot, thanks. 👍

@ghost
Copy link

ghost commented Apr 4, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ec2 Issues and PRs that pertain to the ec2 service. size/M Managed by automation to categorize the size of a PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature Request: Support EC2 Optimize CPU Options
5 participants