[openstack-dev] [neutron][oslo] plan till end-of-Kilo

Kyle Mestery mestery at mestery.com
Tue Jan 20 14:17:02 UTC 2015

On Mon, Jan 19, 2015 at 10:54 AM, Ihar Hrachyshka <ihrachys at redhat.com>

> Hi Kyle/all,
> (we were going to walk thru that on Mon, but since US is on vacation
> today, sending it via email to openstack-dev at .)
> Great, thanks Ihar!

> So I've talked to Doug Hellmann from oslo, and here is what we have in our
> oslo queue to consider:
> 1. minor oslo.concurrency cleanup for *aas repos (we need to drop
> lockutils-wrapper usage now that base test class sets lockutils fixture);
> 2. migration to namespace-less oslo libraries (this is blocked by pending
> oslo.messaging release scheduled this week, will revive patches for all
> four branches the end of the week) [1];
> 3. oslo/kilo-2: graduation of oslo.policy;
> 4. oslo/kilo-3: graduation of oslo.cache, oslo.versionedobjects.
> I believe 1. and 2. should be handled in Kilo-2 neutron side. The 2. part
> will introduce some potential friction in gate due to merge conflicts and
> new hacking rule applied, so we may want to synchronize it with other
> refactoring activities.
> This looks good to me.

> For 3., I'm not sure we want to go with such a change this cycle. On the
> other side, while that is potentially unsafe, it may free us from later
> patching our local policy module copy due to security issues that could be
> revealed later in the incubator module. Taking into account that we claim
> support for 15 months for all stable branches, and who knows where it will
> lead later, earlier reducing our area of responsibility can be a good thing.
> Given the state of our policy code, we may want to look into this one for
Kilo yet. It would be good to get Salv's opinion here as well.

> For 4., this will definitely need to wait for L. The oslo.cache migration
> can easily go with in L-1 (the module is used in single place only -
> metadata agent); as for oslo.versionedobjects, this will need to follow a
> proper spec process (we had someone willing to post a spec for that, but I
> don't remember his/her name).
> Does the plan sound ok?
> This all looks good to me! I'd like to explore the oslo.policy stuff a bit
more before declaring it out of Kilo at this point though, but lets see
what comes of that.


> [1]: https://review.openstack.org/#/q/If0dce29a0980206ace9866112be52
> 9436194d47e,n,z
> /Ihar
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> 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/20150120/72cdbd2f/attachment.html>

More information about the OpenStack-dev mailing list