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

ec2_instance - Support throughtput parameter for GP3 volume types #433

Conversation

alinabuzachis
Copy link
Collaborator

@alinabuzachis alinabuzachis commented Aug 3, 2021

SUMMARY

ec2_instance - Support throughput parameter for GP3 volume types

Fixes #395

ISSUE TYPE
  • Feature Pull Request
COMPONENT NAME

ec2_instance

@ansibullbot
Copy link

@ansibullbot ansibullbot added community_review feature This issue/PR relates to a feature request integration tests/integration module module needs_triage plugins plugin (any type) tests tests labels Aug 3, 2021
Signed-off-by: Alina Buzachis <abuzachis@redhat.com>
@alinabuzachis
Copy link
Collaborator Author

recheck

1 similar comment
@alinabuzachis
Copy link
Collaborator Author

recheck

if not volume['ebs'].get('iops'):
volume['ebs']['iops'] = 3000
if 'throughput' in volume['ebs']:
volume['ebs']['throughput'] = int(volume['ebs']['throughput'])
Copy link
Member

@markuman markuman Aug 10, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe set throughput also to its default value 125 if not set?
what happens when the instance exist already? will it keeps the instance values (in case they were changed manually) or will it overwrite them (reset them)? I've no idea.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @markuman, Thank you for reviewing. I set the default value for throughput.

If my understanding is correct, you can specify different parameters for ebs like throughput and iops only when a new instance is created. In the case an EC2 instance is already present and you would like to modify throughput or iops or both you won’t be allowed because the API allows to modify only a specific subset of BlockDeviceMappings as shows here https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2.html#EC2.Client.modify_instance_attribute
I tried by myself to only change these params (throughput for example) and the task resulted in unchanged reflecting the documentation. Therefore, if you want to change throughput or iops values you would need to use the ec2_vol module.

Signed-off-by: Alina Buzachis <abuzachis@redhat.com>
@tremble tremble added the gate label Aug 25, 2021
Copy link
Contributor

@ansible-zuul ansible-zuul bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@ansible-zuul ansible-zuul bot merged commit cc94310 into ansible-collections:main Aug 25, 2021
abikouo pushed a commit to abikouo/amazon.aws that referenced this pull request Oct 24, 2023
aws_kms - stabilize integration tests

SUMMARY
Integration tests for this test suite were failing occasionally due to timing issues when waiting for < 45 seconds after updates.
Increased the wait times to 45 seconds and split into different tests to run in parallel.
Fixes ansible-collections#433
ISSUE TYPE

Bugfix Pull Request

COMPONENT NAME
aws_kms

Reviewed-by: Jill R <None>
Reviewed-by: Markus Bergholz <git@osuv.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community_review feature This issue/PR relates to a feature request integration tests/integration module module plugins plugin (any type) tests tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ec2_instance: Support throughtput parameter for GP3 volume types as part of volumes parameter
6 participants