Re: [openstack-dev] [oslo] [nova] [all] potential enginefacade adjustment - can everyone live with this?

2015-01-26 Thread Doug Hellmann
On Mon, Jan 26, 2015, at 08:55 AM, Matthew Booth wrote: > On 23/01/15 19:47, Mike Bayer wrote: > > > > > > Doug Hellmann wrote: > > > >> > >> > >> On Fri, Jan 23, 2015, at 12:49 PM, Mike Bayer wrote: > >>> Mike Bayer wrote: > >>> > Ihar Hrachyshka wrote: > > > On 01/23/2015 05

Re: [openstack-dev] [oslo] [nova] [all] potential enginefacade adjustment - can everyone live with this?

2015-01-26 Thread Matthew Booth
On 23/01/15 19:47, Mike Bayer wrote: > > > Doug Hellmann wrote: > >> >> >> On Fri, Jan 23, 2015, at 12:49 PM, Mike Bayer wrote: >>> Mike Bayer wrote: >>> Ihar Hrachyshka wrote: > On 01/23/2015 05:38 PM, Mike Bayer wrote: >> Doug Hellmann wrote: >> >>> We put the new

Re: [openstack-dev] [oslo] [nova] [all] potential enginefacade adjustment - can everyone live with this?

2015-01-23 Thread Mike Bayer
Doug Hellmann wrote: > > > On Fri, Jan 23, 2015, at 12:49 PM, Mike Bayer wrote: >> Mike Bayer wrote: >> >>> Ihar Hrachyshka wrote: >>> On 01/23/2015 05:38 PM, Mike Bayer wrote: > Doug Hellmann wrote: > >> We put the new base class for RequestContext in its own library b

Re: [openstack-dev] [oslo] [nova] [all] potential enginefacade adjustment - can everyone live with this?

2015-01-23 Thread Doug Hellmann
On Fri, Jan 23, 2015, at 12:49 PM, Mike Bayer wrote: > > > Mike Bayer wrote: > > > > > > > Ihar Hrachyshka wrote: > > > >> On 01/23/2015 05:38 PM, Mike Bayer wrote: > >>> Doug Hellmann wrote: > >>> > We put the new base class for RequestContext in its own library because > bot

Re: [openstack-dev] [oslo] [nova] [all] potential enginefacade adjustment - can everyone live with this?

2015-01-23 Thread Mike Bayer
Mike Bayer wrote: > > > Ihar Hrachyshka wrote: > >> On 01/23/2015 05:38 PM, Mike Bayer wrote: >>> Doug Hellmann wrote: >>> We put the new base class for RequestContext in its own library because both the logging and messaging code wanted to influence it's API. Would it make

Re: [openstack-dev] [oslo] [nova] [all] potential enginefacade adjustment - can everyone live with this?

2015-01-23 Thread Mike Bayer
Ihar Hrachyshka wrote: > On 01/23/2015 05:38 PM, Mike Bayer wrote: >> Doug Hellmann wrote: >> >>> We put the new base class for RequestContext in its own library because >>> both the logging and messaging code wanted to influence it's API. Would >>> it make sense to do this database setup the

Re: [openstack-dev] [oslo] [nova] [all] potential enginefacade adjustment - can everyone live with this?

2015-01-23 Thread Ihar Hrachyshka
On 01/23/2015 05:38 PM, Mike Bayer wrote: Doug Hellmann wrote: We put the new base class for RequestContext in its own library because both the logging and messaging code wanted to influence it's API. Would it make sense to do this database setup there, too? whoa, where’s that? is this an os

Re: [openstack-dev] [oslo] [nova] [all] potential enginefacade adjustment - can everyone live with this?

2015-01-23 Thread Mike Bayer
Doug Hellmann wrote: > We put the new base class for RequestContext in its own library because > both the logging and messaging code wanted to influence it's API. Would > it make sense to do this database setup there, too? whoa, where’s that? is this an oslo-wide RequestContext class ? that wo

Re: [openstack-dev] [oslo] [nova] [all] potential enginefacade adjustment - can everyone live with this?

2015-01-23 Thread Doug Hellmann
On Thu, Jan 22, 2015, at 10:36 AM, Mike Bayer wrote: > Hey all - > > Concerning the enginefacade system, approved blueprint: > > https://review.openstack.org/#/c/125181/ > > which will replace the use of oslo_db.sqlalchemy.EngineFacade ultimately > across all projects that use it (which is, al

[openstack-dev] [oslo] [nova] [all] potential enginefacade adjustment - can everyone live with this?

2015-01-22 Thread Mike Bayer
Hey all - Concerning the enginefacade system, approved blueprint: https://review.openstack.org/#/c/125181/ which will replace the use of oslo_db.sqlalchemy.EngineFacade ultimately across all projects that use it (which is, all of them that use a database). We are struggling to find a solution