Re: [openstack-dev] Moving neutron to oslo.db

2014-07-04 Thread Roman Podoliaka
Ben, Neutron was updated to the latest version of db code from oslo-incubator. That's probably all. Thanks, Roman On Thu, Jul 3, 2014 at 8:10 PM, Ben Nemec wrote: > +27, -2401 > > Wow, that's pretty painless. Were there earlier patches to Neutron to > prepare for the transition or was it reall

Re: [openstack-dev] Moving neutron to oslo.db

2014-07-03 Thread Boris Pavlovic
Ben, As I know the API of oslo.db and oslo-incubator/db are almost the same. So why it should be complicated? Best regards, Boris Pavlovic On Thu, Jul 3, 2014 at 9:10 PM, Ben Nemec wrote: > +27, -2401 > > Wow, that's pretty painless. Were there earlier patches to Neutron to > prepare for t

Re: [openstack-dev] Moving neutron to oslo.db

2014-07-03 Thread Ben Nemec
+27, -2401 Wow, that's pretty painless. Were there earlier patches to Neutron to prepare for the transition or was it really that easy? On 07/03/2014 07:34 AM, Salvatore Orlando wrote: > No I was missing everything and kept wasting time because of alembic. > > This will teach me to keep my mout

Re: [openstack-dev] Moving neutron to oslo.db

2014-07-03 Thread Salvatore Orlando
No I was missing everything and kept wasting time because of alembic. This will teach me to keep my mouth shut and don't distract people who are actually doing good work. Thanks for doings this work. Salvatore On 3 July 2014 14:15, Roman Podoliaka wrote: > Hi Salvatore, > > I must be missing

Re: [openstack-dev] Moving neutron to oslo.db

2014-07-03 Thread Roman Podoliaka
Hi Salvatore, I must be missing something. Hasn't it been done in https://review.openstack.org/#/c/103519/? :) Thanks, Roman On Thu, Jul 3, 2014 at 2:51 PM, Salvatore Orlando wrote: > Hi, > > As you surely now, in Juno oslo.db will graduate [1] > I am currently working on the port. It's been al

[openstack-dev] Moving neutron to oslo.db

2014-07-03 Thread Salvatore Orlando
Hi, As you surely now, in Juno oslo.db will graduate [1] I am currently working on the port. It's been already cleared that making alembic migrations "idempotent" and healing the DB schema is a requirement for this task. These two activities are tracked by the blueprints [2] and [3]. I think we've