conflict with rabbitmq exchange between ceilometer notification agent and magnetodb task executor

[Andrii Ostapenko]

Ceilometer notification agent on startup creates rabbitmq exchanges for each service using stevedore, including 'magnetodb' exchange. These exchanges are created with disabled durability by default. However magnetodb uses 'magnetodb' control exchange with enabled durability, so services can not redeclare 'magnetodb' exchange with different durability. Because of ceilometer notification agent is started before magnetodb-async-task executor, 'magnetodb' exchange is created by ceilometer with false durability, and magnetodb-task-executor has no chance to redeclare it.
Proposed fix: use another control exchange for magnetodb-api - magnetodb-async-task-executor messaging

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/146681

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/146681
Committed: https://git.openstack.org/cgit/stackforge/magnetodb/commit/?id=24b4284aaeac519e5b6f5d8c785753c50e86e90d
Submitter: Jenkins
Branch: master

commit 24b4284aaeac519e5b6f5d8c785753c50e86e90d
Author: Andrei V. Ostapenko <email address hidden>
Date: Tue Jan 13 01:26:00 2015 +0200

    Using another control exchange instead of using not durable exchange

    Closes-bug: #1409945
    Change-Id: Ia8928980453613a191802449749184f76dd70b95