On Wed, Mar 5, 2014 at 10:43 AM, Alexei Kornienko < alexei.kornie...@gmail.com> wrote:
> Hello Darren, > > This option is removed since oslo.db will no longer manage engine objects > on it's own. Since it will not store engines it cannot handle query > dispatching. > > Every project that wan't to use slave_connection will have to implement > this logic (creation of the slave engine and query dispatching) on it's own. > If we are going to have multiple projects using that feature, we will have to restore it to oslo.db. Just because the primary API won't manage global objects doesn't mean we can't have a secondary API that does. Doug > > Regards, > > > On 03/05/2014 05:18 PM, Darren Birkett wrote: > > Hi, > > I'm wondering why in this commit: > > > https://github.com/openstack/oslo-incubator/commit/630d3959b9d001ca18bd2ed1cf757f2eb44a336f > > ...the slave_connection option was removed. It seems like a useful > option to have, even if a lot of projects weren't yet using it. > > Darren > > > _______________________________________________ > OpenStack-dev mailing > listOpenStack-dev@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
