Bug 1041108 - [RFE][nova]: Allow the user to decide whether an instance should be resumed on host reboot
Summary: [RFE][nova]: Allow the user to decide whether an instance should be resumed o...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 13:39 UTC by RHOS Integration
Modified: 2015-03-19 16:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 16:59:04 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 13:39:11 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/user-defined-resume.

Description:

The configuration option resume_guests_state_on_host_boot defines
a global policy on whether or not to restart instances when a host
reboots.  Because a host may be down for a significant period of
time many cloud applications monitor their own instances and launch
replacements restarting all instances is rarely the required behavior

This blueprint provides the user with a mechanism to specify at create
time which of their instances should be restarted on a host reboot.

Initially  three values will be accepted:
    RESUME_DEFAULT -   Follow the resume policy configured in the system
    RESUME_NEVER      -  Don't resume the instance
    RESUME_ALWAYS    -  Always resume the instance

Ideally we would allow the user to specify max_downtime policy where instances
are only resumed is the host has been stopped for less that the user specified
duration (i.e  "Only resume if the host is  down for less than 5 minutes") - but not
all ServiceGroup Drivers can support this model   

Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.