Ethan Lynn 6bc753582b Set stack status to FAILED when engine is down ... When stack is in status IN_PROGRESS and engine service went down, the status of stack will forever remain in IN_PROGRESS. This patch add a db apid to get engine_id from stacklock and try to reset the stack status to FAILED when engine is back. Closes-Bug: #1382320 Change-Id: Ica856bb0d56c23a4423fb9476c1986aaacf24108		2015-04-02 11:54:05 +08:00
..
__init__.py	First objects - stack and raw template	2015-03-11 13:56:38 +01:00
event.py	Versioned objects - Event	2015-03-16 09:26:41 +00:00
fields.py	Add extra columns for resource table	2015-03-17 06:09:26 -04:00
raw_template.py	First objects - stack and raw template	2015-03-11 13:56:38 +01:00
resource.py	Correct confusing "cls" argument on non-static method	2015-03-20 09:10:02 +10:00
resource_data.py	Versioned objects - ResourceData	2015-03-12 13:44:12 +01:00
service.py	Versioned object Service	2015-03-17 10:35:57 +05:30
snapshot.py	Versioned objects - Snapshot	2015-03-16 10:26:22 +01:00
software_config.py	Versioned object - SoftwareConfig	2015-03-13 00:50:31 +08:00
software_deployment.py	Make the status_reason field Text instead of String(255)	2015-03-25 13:47:17 +10:00
stack.py	Call db refresh in Stack object refresh	2015-03-20 11:33:03 +13:00
stack_lock.py	Set stack status to FAILED when engine is down	2015-04-02 11:54:05 +08:00
stack_tag.py	StackTag versioned-object	2015-03-16 14:54:58 +05:30
sync_point.py	Versioned-object SyncPoint	2015-03-17 17:32:03 +00:00
user_creds.py	Versioned objects - UserCreds	2015-03-13 10:37:21 +00:00
watch_data.py	Versioned object - WatchRule and WatchData	2015-03-18 14:40:19 +08:00
watch_rule.py	Versioned object - WatchRule and WatchData	2015-03-18 14:40:19 +08:00