change-diskoffer: iops settings from new disk-offer should always used#6681
change-diskoffer: iops settings from new disk-offer should always used#6681yadvr merged 1 commit intoapache:mainfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## main #6681 +/- ##
============================================
+ Coverage 5.87% 10.42% +4.54%
- Complexity 3936 6696 +2760
============================================
Files 2454 2455 +1
Lines 242683 243143 +460
Branches 37978 38061 +83
============================================
+ Hits 14265 25339 +11074
+ Misses 226839 214635 -12204
- Partials 1579 3169 +1590
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
f29013f to
699bf69
Compare
the code smell is 200 lines away from the nearest change in this PR and warants its own PR #notetomyself. |
If you had an disk-offer which would compute-only == false, it wouldn't apply the iop settings of the new disk-offer and instead use null for the settings.
699bf69 to
7704947
Compare
|
Found UI changes, kicking a new UI QA build |
|
@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
UI build: ✔️ |
|
Kudos, SonarCloud Quality Gate passed! |
|
is this good enough now? |
|
@blueorangutan package |
|
@DaanHoogland a 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: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 4236 |
|
@blueorangutan test matrix |
|
@DaanHoogland a Trillian-Jenkins matrix job (centos7 mgmt + xs71, centos7 mgmt + vmware65, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests |
|
Trillian test result (tid-4954)
|
|
Trillian test result (tid-4955)
|
|
Trillian test result (tid-4963)
|
|
@blueorangutan test |
|
@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-4981)
|








Description
If you had an disk-offer which would compute-only == false,
it wouldn't apply the iop settings of the new disk-offer and instead
use null for the settings.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Manually switching between the default 5GB disk offer and a self created IOP limiting disk offer.