Rakesh H S 906a0ed6fd Convergence: Fix concurrent update resource delete ... In convergence, wherein concurrent updates are possible, if a resource is deleted (by previous traversal) after dependency graph is created for new traversal, the resource remains in graph but wouldn't be available in DB for processing. It is prerequisite to have resources in DB before any action can be taken on them. Hence during convergence resource delete action, the resource entry from DB is not deleted i.e soft deleted, so that the latest/new update can find the entry. All of these soft deleted resources will be deleted when the stack has completed its operation. Closes-Bug: #1528560 Change-Id: I0b36ce098022560d7fe01623ce7b66d1d5b38d55		2016-07-05 12:27:37 +05:30
..
sqlalchemy	Convergence: Fix concurrent update resource delete	2016-07-05 12:27:37 +05:30
__init__.py	Do not initialize anything during import phase	2013-04-24 10:03:06 -07:00
api.py	Convergence: Fix concurrent update resource delete	2016-07-05 12:27:37 +05:30
utils.py	Add --verbose-update-params option to heat-manage	2016-05-04 13:12:41 -05:00