| Summary: | [RFE] Support for moving hosts to sleep when using Power Saving policy | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Martin Sivák <msivak> |
| Component: | ovirt-engine-core | Assignee: | Martin Sivák <msivak> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Artyom <alukiano> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.4 | CC: | acathrow, dfediuck, iheim, lhornyak, mavital, msivak, pablo.iranzo, sbonazzo, yeylon |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | 3.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | sla | ||
| Fixed In Version: | ovirt-3.4.0-beta1 | Doc Type: | Enhancement |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-03-31 15:04:55 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Martin Sivák
2013-11-27 11:08:05 UTC
sleep sounds like S3 state, do we really intend to S3 and not S5 (shutdown)? will this be based on WOL or power management? We will use S5 in the first version and we will use ssh and power management to get there. Sleep is something that would make the host start up quickly when we need it, but it is also a bit problematic when we talk about server machines. The current design is described on the feature page: http://www.ovirt.org/Features/HostPowerManagementPolicy *** Bug 865794 has been marked as a duplicate of this bug. *** Martin, for recent HP machines, boot can take ~ 15 minutes, so ruling out already 'starting' hosts for that period of time could be useful for avoiding starting hosts. When working with different hosts, using bogomips as a rule could be helpful but will bring another RFE: tune the hosts up/down to be more power efficient: Having the biggest host to just run 1 small VM will not be the best option, so having some kind of 'measure' of how big a VM is and how powerful the host is, could help to leverage them. Thanks! Verified on av2 Verified on tcms plan This is an automated message: moving to Closed CURRENT_RELEASE since oVirt 3.4.0 has been released. |