[openstack-dev] Proposal oslo.db lib

Gary Kotton gkotton at vmware.com
Mon Aug 19 11:33:11 UTC 2013



From: Boris Pavlovic [mailto:boris at pavlovic.me]
Sent: Monday, August 19, 2013 2:20 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] Proposal oslo.db lib

Flavio,

I'm sorry if I'm being paranoid, I just think we should first focus on
migrating all projects - those that will / should migrate -
successfully and then pulling oslo.db out.

Absolutely agree


Pulling it out during Icehouse won't slow Oslo's db development down.

So the only problem is that is too late for such big changes. Here I am absolutely agree. end of H-3 is not the best time =)


So are you agree with next points?
1) In Havana focus on migrating in all projects to oslo.db code

[Gary Kotton] It is worth going for.

2) in IceHouse create and move to oslo.db lib

[Gary Kotton] I am in favor of this pending the stability of the oslo db code (which is on the right track)

And are you agree that we should start working around olso.db lib now.

[Gary Kotton] I am not sure what the effort for this is, but if this is just a matter of preparing it all for the start of Icehouse then cool, go for it. I nonetheless suggest speaking with Mark McLoughlinto try and learn lessons from the process with the common config module :)

To be able to start switching to it at begin of IceHouse?

And what about Glance patches ?;)
Еheir are ready since Aug 6, 2013 2:41 PM and there is no reviews at all.


Best regards,
Boris Pavlovic
---
Mirantis Inc.



On Mon, Aug 19, 2013 at 2:52 PM, Flavio Percoco <flavio at redhat.com<mailto:flavio at redhat.com>> wrote:
On 19/08/13 14:17 +0400, Boris Pavlovic wrote:
Flavio,

Agreed. I'd also like to see other project migrated before pulling
oslo.db out from oslo-incubator


as I wrote before oslo.db code is used by:  Nova, Neutron, Cinder, Ironic,
Ceilometer use oslo.db. And we have already patches to switch in Glance to id.
And we are woking in Keystone and Heat.
Why (nova, neutron, cinder, ironic and ceilometer) is not enough to say that
the code is OK?

Because we're talking about the database code here. All projects
depend / will depend on it. I wouldn't consider the whole API stable
until all projects have successfully migrated to it. There are corner
cases that could have been missed and that would require a new oslo.db
release - assuming it has been pulled out - for them to be applied to
projects using it.

I'm sorry if I'm being paranoid, I just think we should first focus on
migrating all projects - those that will / should migrate -
successfully and then pulling oslo.db out.

Hm, I really don't see big problems with migrating to oslo.db lib even in this
moment, because in oslo-incubator and in oslo.db is the same code.. Could you
explain what problem you see in process of migartion? (For me it is add one
more requirments, remove openstack/db/.. folder, switch imports)..

AFAIK, doing this will require to:

1) Set up a new repository
2) Make a release / tarball that you could use in the requirements
file.
3) Change imports on all projects using oslo-incubator db code.

All the steps above require people to review patches and step 3 needs
to be done on 5 projects. In the meantime, you're also submitting
patches to the not-yet migrated projects that are based on Oslo's code
and those patches, if not yet merged - will also have to be updated.

My concern is that there's a lot of work yet to be done on this area
and I don't think it is ready to be pulled out yet. I'd prefer a
migration process similar to oslo.config. All project were using it
before it was pulled out and that was done when the API was considered
stable.

Pulling it out during Icehouse won't slow Oslo's db development down.
Remaining projects can still be migrated and released during Havanna.

Cheers,

FF

--
@flaper87
Flavio Percoco

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130819/553bf204/attachment.html>


More information about the OpenStack-dev mailing list