Pluggable conductor manager

I'd like to propose the ability to support a pluggable trove conductor manager. Currently the trove conductor manager is hard-coded [1][2] and thus is always 'trove.conductor.manager.Manager'. I'd like to see this conductor manager class be pluggable like nova does [3].

I'm thinking the same approach nova took:
(a) Add a conductor section to the trove-conductor.conf with a property to specify the conductor manager class... e.g.
[conductor]
manager = package.of.conductor.manager.Manager

(b) Default trove's CONF value for conductor.manager to the existing manager trove.conductor.manager.Manager which ensures backwards compat.

(c) In trove.cmd.conductor.py create the RpcService using the conf value. e.g.
server = rpc_service.RpcService(manager=CONF.conductor.manager, topic=topic)

The above will allow consumers to extend / plug into the conductor manager without upstream changes.

See email list: http://lists.openstack.org/pipermail/openstack-dev/2014-April/033897.html