Open Stack

Looking back at the meeting eavesdrop, the primary reasons why we
deferred this work to Liberty was twofold:

- It wasn't a set plan based on information available to us at the time.
This being the case, we decided to wait until we had more information
regarding the requirements around this from oslo.

- We wanted to ensure that we had a corresponding hacking rule in
place to prevent future patch-sets from using the deprecated module
names.

We specifically didn't consider the impact of logging statements with
deprecation warnings at the meeting.

We now have a better picture of the actual status -- with the oslo
decision that these namespace packages are definitely going away.
I've added an agenda item to bring this up again at the next Trove
weekly meeting [1] so that we can address this.

[1] https://wiki.openstack.org/wiki/Meetings/TroveMeeting

Thanks,
Nikhil



On Thu, Mar 12, 2015 at 4:05 PM, Robert Collins <robertc at robertcollins.net>
wrote:

> On 13 March 2015 at 09:43, Ihar Hrachyshka <ihrachys at redhat.com> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On 03/12/2015 09:35 PM, Robert Collins wrote:
> >> On 13 March 2015 at 08:09, Ihar Hrachyshka <ihrachys at redhat.com>
> >> wrote:
> >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> >>>
> >>> On 03/12/2015 11:38 AM, Boris Bobrov wrote:
> >>>> On Thursday 12 March 2015 12:59:10 Duncan Thomas wrote:
> >>>>> So, assuming that all of the oslo depreciations aren't going
> >>>>> to be fixed before release
> >>>>
> >>>> What makes you think that?
> >>>>
> >>>> In my opinion it's just one component's problem. These
> >>>> particular deprecation warnings are a result of still on-going
> >>>> migration from oslo.<package> to oslo_<package>. Ironically,
> >>>> all components except oslo have already moved to the new naming
> >>>> scheme.
> >>>
> >>> It's actually wrong. For example, Trove decided to stay on using
> >>> the old namespace for Kilo.
> >>
> >> Why?
> >>
> >> -Rob
> >>
> >
> >
> http://eavesdrop.openstack.org/irclogs/%23openstack-meeting-alt/%23openstack-meeting-alt.2015-02-11.log
> >
> > starting from "2015-02-11T18:03:11". I guess the assumption was that
> > there is immediate benefit, and they can just wait. Though I don't
> > think the fact that it means deprecation warnings in their logs was
> > appreciated at the time of decision.
>
> Thanks, reading that it looks like the actual status (oslo decided
> most definitely that namespace packages are going away, its just a
> matter of when) wasn't understood in that meeting.
>
> Is it possible to put it back on the agenda for the next Trove meeting?
>
> Cheers,
> Rob
>
> --
> Robert Collins <rbtcollins at hp.com>
> Distinguished Technologist
> HP Converged Cloud
>
> __________________________________________________________________________
> 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/20150312/4fa92a2a/attachment.html>