-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Consider Instance in Starting state as well for allocation algorithm #11751
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
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## 4.20 #11751 +/- ##
============================================
- Coverage 16.17% 16.17% -0.01%
Complexity 13296 13296
============================================
Files 5656 5656
Lines 498223 498240 +17
Branches 60454 60457 +3
============================================
Hits 80577 80577
- Misses 408676 408693 +17
Partials 8970 8970
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
weizhouapache
left a comment
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.
code lgtm
|
@blueorangutan package |
|
@sudo87 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 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 15222 |
|
@blueorangutan test |
|
@sudo87 a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
shwstppr
left a comment
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.
code lgtm
|
[SF] Trillian test result (tid-14477)
|
engine/schema/src/main/java/com/cloud/vm/dao/VMInstanceDaoImpl.java
Outdated
Show resolved
Hide resolved
|
@blueorangutan package |
|
@sudo87 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. |
weizhouapache
left a comment
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.
code lgtm
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 15240 |
|
@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-14489)
|
|
@blueorangutan test |
|
@sudo87 a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
this PR makes sense to me, however it is difficult to validate |
|
@weizhouapache, agreed. It needs testing with larger env. That said, I did a basic validation (suggested in the issue) by spinning off 4 instances in 2 different envs running 4.20, one with this change and other without. Both were configured with userdispersing vm allocation algo. Results:
|
@sudo87 |
End result is same for both envs, each host has 10 instances running. Transition from Initialize -> Starting -> Running is small for a lean image. |
ok, so it may happen only if starting vms take a bit long time than usual |
|
[SF] Trillian test result (tid-14491)
|
…gorithm (apache#11751) * Consider Instance in Starting state as well for allocation algorithm * use IN instead of OR statement
…gorithm (apache#11751) * Consider Instance in Starting state as well for allocation algorithm * use IN instead of OR statement
Description
This PR fixes #11606
With this change, allocation algorithm will take Instance in starting state as well for allocation.
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?