magnum/magnum/conductor
Danil Golov 9cbb142c2e Add cluster record to db right after API request
This commit changes the incorrect behavior of cluster create workflow.
Now db record with status CREATE_IN_PROGRESS is created right after
related API request.

Change-Id: I11692c4126823d49672ba5172fa45774bf0ce544
Closes-bug: #1640729
2016-12-27 13:19:13 +03:00
..
handlers Add cluster record to db right after API request 2016-12-27 13:19:13 +03:00
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 Centralize config option: conductor section 2016-09-22 01:00:16 +00: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 Centralize config option: docker section 2016-09-22 05:57:31 +00:00
scale_manager.py Fix magnum cluster-update error 2016-10-24 13:35:59 +08: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