magnum/magnum/conductor
Madhuri Kumari 9f7295475d Add exceptions to cluster db to show failures
After changing create to async operation, all the exceptions goes hidden
and no db entry is created to show the actual failure. One has to go through
the logs to find the actual error. This patch creates a db entry in cluster
table to show the actual error in column 'status_reason'.

Change-Id: Iad6e8bfce7326b34dea04914e4552f87d2796e86
Closes-bug: #1623387
2016-09-14 20:27:10 +05:30
..
handlers Add exceptions to cluster db to show failures 2016-09-14 20:27:10 +05:30
tasks Add Heat tasks 2015-03-09 08:14:17 +09:00
__init__.py Add initial conductor API and service 2014-11-21 06:24:46 -05:00
api.py Rename Bay DB, Object, and internal usage to Cluster 2016-09-08 13:01:12 -07:00
config.py Clean up miscellaneous help strings 2015-07-24 00:46:34 -05:00
k8s_api.py Rename Bay DB, Object, and internal usage to Cluster 2016-09-08 13:01:12 -07:00
k8s_monitor.py Rename Bay DB, Object, and internal usage to Cluster 2016-09-08 13:01:12 -07:00
mesos_monitor.py Rename Bay DB, Object, and internal usage to Cluster 2016-09-08 13:01:12 -07:00
monitors.py Rename Bay DB, Object, and internal usage to Cluster 2016-09-08 13:01:12 -07:00
scale_manager.py Rename Bay DB, Object, and internal usage to Cluster 2016-09-08 13:01:12 -07:00
swarm_monitor.py Rename Bay DB, Object, and internal usage to Cluster 2016-09-08 13:01:12 -07:00
utils.py Rename Bay DB, Object, and internal usage to Cluster 2016-09-08 13:01:12 -07:00