Comment 5 for bug 1539527

<<<To fix it, we need to allow m-api to access data base, I am not sure this is really what we want.

Yes, i also think this is the only way to do this.

@Eli, then how admin would know conductor is down using service-list api, because it will not respond because conductor is down.
service-list api would make no sense in this case.Following are the output when conductor is up and down:-

ubuntu@ubuntubase:/opt/stack/magnum$ magnum service-list
+----+-----------+------------------+-------+
| id | host | binary | state |
+----+-----------+------------------+-------+
| 1 | localhost | magnum-conductor | up |
+----+-----------+------------------+-------+

When conductor is down:-
ubuntu@ubuntubase:/opt/stack/magnum$ magnum service-list
ERROR: Timed out waiting for a reply to message ID 01d6cdbb802142bda1c33cd28f6a2d35 (HTTP 500) (Request-ID: req-248f2ee3-4633-4768-819a-21c9f1d6ec8b)