Bug 1041419

Summary:	[RFE][nova]: Instance-stop workflow reliable activation by using taskflow
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/stop-instance-reliable-execution
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_new
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:19:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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