-
Notifications
You must be signed in to change notification settings - Fork 339
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
vmware_guest_disk: Add iolimit modifications on an existing disk with… #1466
vmware_guest_disk: Add iolimit modifications on an existing disk with… #1466
Conversation
Build failed. ❌ ansible-tox-linters FAILURE in 4m 20s |
Build failed. ❌ ansible-tox-linters FAILURE in 4m 26s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 4m 20s |
@yo000 Your changes are buggy. The module fails our integration tests (see the last CI run) here:
It seems to work fine when changing Additionaly, I feel there are some more problems although I can't really put my finger on them. One thing is that there is a function to set community.vmware/plugins/modules/vmware_guest_disk.py Lines 601 to 619 in c660ecd
I think it might be worth (re-) using. Something like:
And then remove community.vmware/plugins/modules/vmware_guest_disk.py Lines 737 to 753 in fb5fd3e
But do it later when there has been a change detected for IO limits, shares or disk size:
This is still very crude and lacking some safety checks and similar, but what do you think? |
@mariolenz thank you for reviewing. I did not pay enough attention to get_ioandshares_diskconfig! |
Build failed. ✔️ ansible-tox-linters SUCCESS in 4m 39s |
recheck |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 4m 14s |
Could you please add a changelog fragment, like this one? Maybe something like:
or similar. Rest LGTM! |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 5m 07s |
Thanks @yo000! |
Build succeeded (gate pipeline). ✔️ ansible-tox-linters SUCCESS in 4m 09s |
SUMMARY
This commit add iolimit modifications on an existing disk without changing size.
ISSUE TYPE
Feature Pull Request
COMPONENT NAME
plugin community.vmware.vmware_guest_disk
ADDITIONAL INFORMATION
As of today, one can't change an existing disk iops limit and/or shares level without also changing the disk size.
Idempotency is only done on disk size, so task will "ok" whatever iolimit is set to.
This commit fix that