Bug 1041419 - [RFE][nova]: Instance-stop workflow reliable activation by using taskflow
Summary: [RFE][nova]: Instance-stop workflow reliable activation by using taskflow
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 16:03 UTC by RHOS Integration
Modified: 2015-03-19 17:19 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description RHOS Integration 2013-12-12 16:03:35 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/stop-instance-reliable-execution.

Description:

After moving the core logic of the stop_instance 'workflow' to the conductor (and leaving a lightweight task-receiver in the compute manager that still runs driver like logic) we need to be able to reliably ensure that that workflow is executed in a manner that can survive process failure by resuming (or can be reverted in this case); this will be useful for upgrades, crashes, and other general cases where reliability and consistency of your cloud is important (when is it not). Taskflow provides this type of core functionality so it seems like an ideal fit for this scenario.

Specification URL (additional information):

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