> 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].
Note that most of us don't like this and we're generally trying to get rid of these sorts of things. I actually didn't realize that conductor.manager was exposed in the CONF, and was probably just done to mirror other similar settings. Making arbitrary classes pluggable like this without a structured and stable API is really just asking for trouble when people think it's a pluggable interface. So, you might not want to use "because nova does it" as a reason to add it to trove like this :) --Dan _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
