Bug 978522
Summary: | [RFE] Shut down an instance, with potential to free up hypervisor reso... | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Russell Bryant <rbryant> |
Component: | openstack-nova | Assignee: | Russell Bryant <rbryant> |
Status: | CLOSED ERRATA | QA Contact: | Brent Eagles <beagles> |
Severity: | unspecified | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | ajeain, dallan, jkt, mlopes, ndipanov, sradvan |
Target Milestone: | Upstream M2 | Keywords: | FutureFeature, OtherQA |
Target Release: | 4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | https://blueprints.launchpad.net/nova/+spec/shelve-instance | ||
Whiteboard: | |||
Fixed In Version: | openstack-nova-2013.2-0.8.b2.el6ost | Doc Type: | Enhancement |
Doc Text: |
Feature:
Users may now stop servers they are not currently using but still retain them in their list of servers. This is referred to as shelving. A shelved server can be restarted using its same data, configuration, and identity at a point in the future. While a server is shelved, hypervisors are able to reclaim the resources that were used by that server and use it for running other servers if needed.
Reason:
Users would like the ability to stop servers when they do not need them, but retain it in their list of servers and retain all data and resources associated with it. If an instance is stopped for an extended period of time, an operator may wish to move that instance off of the hypervisor in order to minimize resource usage.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-12-20 00:11:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 988983 | ||
Bug Blocks: | 975499 |
Description
Russell Bryant
2013-06-26 18:09:09 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1859.html |