-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Resize volume: add pool capacity disablethreshold for resize and allow volume auto migration #9761
base: main
Are you sure you want to change the base?
Resize volume: add pool capacity disablethreshold for resize and allow volume auto migration #9761
Conversation
…e/ResizeVolumeCmd.java Co-authored-by: Suresh Kumar Anaparti <[email protected]>
@blueorangutan package |
@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9761 +/- ##
============================================
+ Coverage 15.78% 15.81% +0.02%
- Complexity 12551 12568 +17
============================================
Files 5625 5625
Lines 491972 492051 +79
Branches 63764 60723 -3041
============================================
+ Hits 77662 77821 +159
+ Misses 405850 405716 -134
- Partials 8460 8514 +54
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 11261 |
@blueorangutan test |
@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
@blueorangutan package |
@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
[SF] Trillian test result (tid-11602)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clgtm
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 11264 |
@blueorangutan test |
@sureshanaparti a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
@blueorangutan test |
@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
[SF] Trillian test result (tid-11607)
|
[SF] Trillian test result (tid-11603)
|
@blueorangutan package |
@sureshanaparti a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 11284 |
@blueorangutan test |
@rohityadavcloud a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I've tested it with both NFS and PF setups, manually checked the volume.resize.allowed.beyond.allocation and pool.storage.allocated.resize.capacity.disablethreshold are honoured and migration will be carried out if not enough storage at current pool. Also covered the negative cases where if a threshold is reached operation is being failed gracefully
Let's wait for tests to come out and I think we can merge this.
[SF] Trillian test result (tid-11643)
|
[SF] Trillian test result (tid-11645)
|
[SF] Trillian test result (tid-11646)
|
Description
Currently, when resize a volume, ACS checks if the current storage pool can accommodate the new size, and simply return true if pool has enough capacity, or false if there are not enough capacity.
This PR
when resize a volume
pool.storage.allocated.capacity.disablethreshold
volume.resize.allowed.beyond.allocation
isfalse
, go to migration stepvolume.resize.allowed.beyond.allocation
istrue
, it will check pool capacity for resize thresholdpool.storage.allocated.resize.capacity.disablethreshold
.prior to this change
With this change
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?