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
..
api	Merge "Enable SSL for EC2Tokens."	2015-03-26 12:18:50 +00:00
cloudinit	Enable H305 and H307 style checks	2015-01-20 09:47:25 +02:00
cmd	Use Service objects instead of db_api	2015-03-23 06:38:21 -04:00
common	Change the default num_engine_workers to get_worker_count()	2015-03-31 07:55:18 +10:00
db	Set stack status to FAILED when engine is down	2015-04-02 11:54:05 +08:00
engine	Set stack status to FAILED when engine is down	2015-04-02 11:54:05 +08:00
locale	Imported Translations from Transifex	2015-03-26 06:00:40 +00:00
objects	Set stack status to FAILED when engine is down	2015-04-02 11:54:05 +08:00
openstack	oslo-incubator sync	2015-03-27 11:04:24 +05:30
rpc	Remove return for rpc casts in rpc worker client	2015-03-24 23:17:19 +05:30
scaling	Pass the environment into the Template class and not Stack	2015-03-18 10:29:55 +10:00
tests	Set stack status to FAILED when engine is down	2015-04-02 11:54:05 +08:00
__init__.py	Make import of oslo libraries namespaceless	2015-02-18 22:54:10 +01:00
version.py	Make the first line of every file consistent.	2014-03-04 09:03:04 -06:00