Configurable rescheduling when waking from suspend, or starting from shutdown
Bug #1791681 reported by
Tobias Rydberg
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Public Cloud WG |
Won't Fix
|
Undecided
|
Tobias Rydberg | ||
Bug Description
As a follow-on from the above, re-evaluate a node's CPU and RAM utilization when a guest starts (after stop) or resumes (after suspend), and have a configurable option for what to do if CPU and RAM thresholds are breached:
Start/resume the guest in place, ignoring the overcommit (this is the current behavior)
Kick the guest back to the scheduler, to find a better-suited (i.e. non-overcommitted) node
Presumably, operators would be more likely to use the second option if and only if guests run on shared storage, RBD, etc., but it could also be used with non-shared storage, equivalent to block migration.
Revision history for this message
| Matt Riedemann (mriedem) wrote | #1 |
Revision history for this message
| Matt Riedemann (mriedem) wrote | #2 |
| Changed in openstack-publiccloud-wg: | |
| status: | New → Won't Fix |
Revision history for this message
| Dan Smith (danms) wrote | #3 |
To post a comment you must log in.
> As a follow-on from the above
Please be specific.