Re: [openstack-dev] [oslo][nova][all] timeutils deprecation removals will break Nova

2015-12-22 Thread ChangBo Guo 
Just check we have removed deprecated methods in
https://review.openstack.org/#/c/241179/ for Nova.  So current there is no
work from Nova side now.


2015-12-22 13:53 GMT+08:00 ChangBo Guo :

>
>
> 2015-12-22 3:42 GMT+08:00 Matt Riedemann :
>
>>
>>
>> On 12/21/2015 1:22 PM, Davanum Srinivas wrote:
>>
>>> Rob,
>>>
>>> Can we set some goals for the server projects too?
>>>
>>> Say anything deprecated in liberty timeframe in oslo libs or any other
>>> libs we consume should be fixed by milestone2 in mitaka? At the moment
>>> the burden is entirely on oslo and hence unfair.
>>>
>>> Thanks,
>>> Dims
>>>
>>> On Mon, Dec 21, 2015 at 2:15 PM, Robert Collins
>>>  wrote:
>>>
 On 21 December 2015 at 04:57, Davanum Srinivas 
 wrote:

> Nova folks,
>
> We have this review in oslo.utils:
> https://review.openstack.org/#/c/252898/
>
> There were failed effort in the past to cleanup in Nova:
> https://review.openstack.org/#/c/164753/
> https://review.openstack.org/#/c/197601/
>
> What do we do? Suggestions please.
>

 We don't remove it yet. Not till liberty-eol at the earliest, or if we
 don't get users migrated early enough, mitaka-eol.

 We would benefit from an automated thing in place to tell projects
 like Nova that they are using deprecated things during CI (without
 bloating deployer logs) -  whether a keystone API, an oslo config
 option or function, or $whatever. We would also benefit from a thing
 to rollup such information from consuming projects back to the
 deprecating project, so we can tell whether we're ready to cleanup old
 things.

 I think in general that there needs to be a balance around effort on
 migrations: if oslo deprecates something - anything - we're creating
 work for consumers of oslo. Its unfair for us to do that unilaterally.
 Conversely, if projects don't migrate away from poor APIs onto newer
 better ones, they create long term maintenance work for oslo: so we
 all need to work together to coordinate such things.

 https://review.openstack.org/#/c/226157/12 is part of this - it is an
 effort to bring consistency in expectations and process/patterns here.

 -Rob

 --
 Robert Collins 
 Distinguished Technologist
 HP Converged Cloud


 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

>>>
>>>
>>>
>>>
>> Nova also needs an Oslo liaison [1]. That used to be Joe Gordon, but he's
>> gone now. That would really be the person in Nova driving the Oslo changes
>> and review priorities.
>>
>> [1] https://wiki.openstack.org/wiki/CrossProjectLiaisons#Oslo
>>
>> --
>>
>
>   Matt, I would like to take the liaison for Nova,  I worked on both Nova
> and Oslo,  as Oslo core reviewer I attend  Oslo weekly meeting and will
>   help Nova and Oslo team work together smoothly.   I would like to submit
> new commit to  removing  deprecated method for Nova.
>
>>
>> Thanks,
>>
>> Matt Riedemann
>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
> ChangBo Guo(gcb)
>



-- 
ChangBo Guo(gcb)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo][nova][all] timeutils deprecation removals will break Nova

2015-12-22 Thread Matt Riedemann 



On 12/21/2015 11:53 PM, ChangBo Guo wrote:



2015-12-22 3:42 GMT+08:00 Matt Riedemann >:



On 12/21/2015 1:22 PM, Davanum Srinivas wrote:

Rob,

Can we set some goals for the server projects too?

Say anything deprecated in liberty timeframe in oslo libs or any
other
libs we consume should be fixed by milestone2 in mitaka? At the
moment
the burden is entirely on oslo and hence unfair.

Thanks,
Dims

On Mon, Dec 21, 2015 at 2:15 PM, Robert Collins
>
wrote:

On 21 December 2015 at 04:57, Davanum Srinivas
> wrote:

Nova folks,

We have this review in oslo.utils:
https://review.openstack.org/#/c/252898/

There were failed effort in the past to cleanup in Nova:
https://review.openstack.org/#/c/164753/
https://review.openstack.org/#/c/197601/

What do we do? Suggestions please.


We don't remove it yet. Not till liberty-eol at the
earliest, or if we
don't get users migrated early enough, mitaka-eol.

We would benefit from an automated thing in place to tell
projects
like Nova that they are using deprecated things during CI
(without
bloating deployer logs) -  whether a keystone API, an oslo
config
option or function, or $whatever. We would also benefit from
a thing
to rollup such information from consuming projects back to the
deprecating project, so we can tell whether we're ready to
cleanup old
things.

I think in general that there needs to be a balance around
effort on
migrations: if oslo deprecates something - anything - we're
creating
work for consumers of oslo. Its unfair for us to do that
unilaterally.
Conversely, if projects don't migrate away from poor APIs
onto newer
better ones, they create long term maintenance work for
oslo: so we
all need to work together to coordinate such things.

https://review.openstack.org/#/c/226157/12 is part of this -
it is an
effort to bring consistency in expectations and
process/patterns here.

-Rob

--
Robert Collins >
Distinguished Technologist
HP Converged Cloud


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





Nova also needs an Oslo liaison [1]. That used to be Joe Gordon, but
he's gone now. That would really be the person in Nova driving the
Oslo changes and review priorities.

[1] https://wiki.openstack.org/wiki/CrossProjectLiaisons#Oslo

--


   Matt, I would like to take the liaison for Nova,  I worked on both
Nova and Oslo,  as Oslo core reviewer I attend  Oslo weekly meeting and
will
   help Nova and Oslo team work together smoothly.   I would like to
submit new commit to  removing  deprecated method for Nova.


Thanks,

Matt Riedemann



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




--
ChangBo Guo(gcb)


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



OK, I put your name in the table for nova [1], thanks.

[1] https://wiki.openstack.org/wiki/CrossProjectLiaisons#Oslo

--

Thanks,

Matt Riedemann


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo][nova][all] timeutils deprecation removals will break Nova

2015-12-21 Thread Matt Riedemann 



On 12/21/2015 1:22 PM, Davanum Srinivas wrote:

Rob,

Can we set some goals for the server projects too?

Say anything deprecated in liberty timeframe in oslo libs or any other
libs we consume should be fixed by milestone2 in mitaka? At the moment
the burden is entirely on oslo and hence unfair.

Thanks,
Dims

On Mon, Dec 21, 2015 at 2:15 PM, Robert Collins
 wrote:

On 21 December 2015 at 04:57, Davanum Srinivas  wrote:

Nova folks,

We have this review in oslo.utils:
https://review.openstack.org/#/c/252898/

There were failed effort in the past to cleanup in Nova:
https://review.openstack.org/#/c/164753/
https://review.openstack.org/#/c/197601/

What do we do? Suggestions please.


We don't remove it yet. Not till liberty-eol at the earliest, or if we
don't get users migrated early enough, mitaka-eol.

We would benefit from an automated thing in place to tell projects
like Nova that they are using deprecated things during CI (without
bloating deployer logs) -  whether a keystone API, an oslo config
option or function, or $whatever. We would also benefit from a thing
to rollup such information from consuming projects back to the
deprecating project, so we can tell whether we're ready to cleanup old
things.

I think in general that there needs to be a balance around effort on
migrations: if oslo deprecates something - anything - we're creating
work for consumers of oslo. Its unfair for us to do that unilaterally.
Conversely, if projects don't migrate away from poor APIs onto newer
better ones, they create long term maintenance work for oslo: so we
all need to work together to coordinate such things.

https://review.openstack.org/#/c/226157/12 is part of this - it is an
effort to bring consistency in expectations and process/patterns here.

-Rob

--
Robert Collins 
Distinguished Technologist
HP Converged Cloud

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev






Nova also needs an Oslo liaison [1]. That used to be Joe Gordon, but 
he's gone now. That would really be the person in Nova driving the Oslo 
changes and review priorities.


[1] https://wiki.openstack.org/wiki/CrossProjectLiaisons#Oslo

--

Thanks,

Matt Riedemann


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo][nova][all] timeutils deprecation removals will break Nova

2015-12-21 Thread Robert Collins 
On 21 December 2015 at 04:57, Davanum Srinivas  wrote:
> Nova folks,
>
> We have this review in oslo.utils:
> https://review.openstack.org/#/c/252898/
>
> There were failed effort in the past to cleanup in Nova:
> https://review.openstack.org/#/c/164753/
> https://review.openstack.org/#/c/197601/
>
> What do we do? Suggestions please.

We don't remove it yet. Not till liberty-eol at the earliest, or if we
don't get users migrated early enough, mitaka-eol.

We would benefit from an automated thing in place to tell projects
like Nova that they are using deprecated things during CI (without
bloating deployer logs) -  whether a keystone API, an oslo config
option or function, or $whatever. We would also benefit from a thing
to rollup such information from consuming projects back to the
deprecating project, so we can tell whether we're ready to cleanup old
things.

I think in general that there needs to be a balance around effort on
migrations: if oslo deprecates something - anything - we're creating
work for consumers of oslo. Its unfair for us to do that unilaterally.
Conversely, if projects don't migrate away from poor APIs onto newer
better ones, they create long term maintenance work for oslo: so we
all need to work together to coordinate such things.

https://review.openstack.org/#/c/226157/12 is part of this - it is an
effort to bring consistency in expectations and process/patterns here.

-Rob

-- 
Robert Collins 
Distinguished Technologist
HP Converged Cloud

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo][nova][all] timeutils deprecation removals will break Nova

2015-12-21 Thread Davanum Srinivas 
Rob,

Can we set some goals for the server projects too?

Say anything deprecated in liberty timeframe in oslo libs or any other
libs we consume should be fixed by milestone2 in mitaka? At the moment
the burden is entirely on oslo and hence unfair.

Thanks,
Dims

On Mon, Dec 21, 2015 at 2:15 PM, Robert Collins
 wrote:
> On 21 December 2015 at 04:57, Davanum Srinivas  wrote:
>> Nova folks,
>>
>> We have this review in oslo.utils:
>> https://review.openstack.org/#/c/252898/
>>
>> There were failed effort in the past to cleanup in Nova:
>> https://review.openstack.org/#/c/164753/
>> https://review.openstack.org/#/c/197601/
>>
>> What do we do? Suggestions please.
>
> We don't remove it yet. Not till liberty-eol at the earliest, or if we
> don't get users migrated early enough, mitaka-eol.
>
> We would benefit from an automated thing in place to tell projects
> like Nova that they are using deprecated things during CI (without
> bloating deployer logs) -  whether a keystone API, an oslo config
> option or function, or $whatever. We would also benefit from a thing
> to rollup such information from consuming projects back to the
> deprecating project, so we can tell whether we're ready to cleanup old
> things.
>
> I think in general that there needs to be a balance around effort on
> migrations: if oslo deprecates something - anything - we're creating
> work for consumers of oslo. Its unfair for us to do that unilaterally.
> Conversely, if projects don't migrate away from poor APIs onto newer
> better ones, they create long term maintenance work for oslo: so we
> all need to work together to coordinate such things.
>
> https://review.openstack.org/#/c/226157/12 is part of this - it is an
> effort to bring consistency in expectations and process/patterns here.
>
> -Rob
>
> --
> Robert Collins 
> Distinguished Technologist
> HP Converged Cloud
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Davanum Srinivas :: https://twitter.com/dims

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo][nova][all] timeutils deprecation removals will break Nova

2015-12-21 Thread ChangBo Guo 
2015-12-22 3:42 GMT+08:00 Matt Riedemann :

>
>
> On 12/21/2015 1:22 PM, Davanum Srinivas wrote:
>
>> Rob,
>>
>> Can we set some goals for the server projects too?
>>
>> Say anything deprecated in liberty timeframe in oslo libs or any other
>> libs we consume should be fixed by milestone2 in mitaka? At the moment
>> the burden is entirely on oslo and hence unfair.
>>
>> Thanks,
>> Dims
>>
>> On Mon, Dec 21, 2015 at 2:15 PM, Robert Collins
>>  wrote:
>>
>>> On 21 December 2015 at 04:57, Davanum Srinivas 
>>> wrote:
>>>
 Nova folks,

 We have this review in oslo.utils:
 https://review.openstack.org/#/c/252898/

 There were failed effort in the past to cleanup in Nova:
 https://review.openstack.org/#/c/164753/
 https://review.openstack.org/#/c/197601/

 What do we do? Suggestions please.

>>>
>>> We don't remove it yet. Not till liberty-eol at the earliest, or if we
>>> don't get users migrated early enough, mitaka-eol.
>>>
>>> We would benefit from an automated thing in place to tell projects
>>> like Nova that they are using deprecated things during CI (without
>>> bloating deployer logs) -  whether a keystone API, an oslo config
>>> option or function, or $whatever. We would also benefit from a thing
>>> to rollup such information from consuming projects back to the
>>> deprecating project, so we can tell whether we're ready to cleanup old
>>> things.
>>>
>>> I think in general that there needs to be a balance around effort on
>>> migrations: if oslo deprecates something - anything - we're creating
>>> work for consumers of oslo. Its unfair for us to do that unilaterally.
>>> Conversely, if projects don't migrate away from poor APIs onto newer
>>> better ones, they create long term maintenance work for oslo: so we
>>> all need to work together to coordinate such things.
>>>
>>> https://review.openstack.org/#/c/226157/12 is part of this - it is an
>>> effort to bring consistency in expectations and process/patterns here.
>>>
>>> -Rob
>>>
>>> --
>>> Robert Collins 
>>> Distinguished Technologist
>>> HP Converged Cloud
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>>
>>
> Nova also needs an Oslo liaison [1]. That used to be Joe Gordon, but he's
> gone now. That would really be the person in Nova driving the Oslo changes
> and review priorities.
>
> [1] https://wiki.openstack.org/wiki/CrossProjectLiaisons#Oslo
>
> --
>

  Matt, I would like to take the liaison for Nova,  I worked on both Nova
and Oslo,  as Oslo core reviewer I attend  Oslo weekly meeting and will
  help Nova and Oslo team work together smoothly.   I would like to submit
new commit to  removing  deprecated method for Nova.

>
> Thanks,
>
> Matt Riedemann
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
ChangBo Guo(gcb)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo][nova][all] timeutils deprecation removals will break Nova

2015-12-21 Thread ChangBo Guo 
Thanks Dims for raising  this up,  It seems the two commits got negative
scores due to Nova release schedule.
So can we restore abandoned commits, before that still would like to get
feedback from Nova guys.

2015-12-20 23:57 GMT+08:00 Davanum Srinivas :

> Nova folks,
>
> We have this review in oslo.utils:
> https://review.openstack.org/#/c/252898/
>
> There were failed effort in the past to cleanup in Nova:
> https://review.openstack.org/#/c/164753/
> https://review.openstack.org/#/c/197601/
>
> What do we do? Suggestions please.
>
> Thanks,
> Dims
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
ChangBo Guo(gcb)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo][nova][all] timeutils deprecation removals will break Nova

2015-12-21 Thread Matt Riedemann 



On 12/20/2015 9:57 AM, Davanum Srinivas wrote:

Nova folks,

We have this review in oslo.utils:
https://review.openstack.org/#/c/252898/

There were failed effort in the past to cleanup in Nova:
https://review.openstack.org/#/c/164753/
https://review.openstack.org/#/c/197601/

What do we do? Suggestions please.

Thanks,
Dims



I have a -1 on the change, will state the same reason here. Without a 
cap on oslo.utils in stable/liberty g-r, this will break at least nova 
in stable/liberty since it's a backward incompatible change.


As with most things now, I think the path forward is getting nova onto 
the new code, raise the min required version of oslo.utils in mitaka to 
where the new methods were added (that's probably already the case if 
the deprecation happened awhile ago), and then the deprecated functions 
can't be removed until liberty-eol.


--

Thanks,

Matt Riedemann


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo][nova][all] timeutils deprecation removals will break Nova

2015-12-20 Thread Dolph Mathews 
On Sunday, December 20, 2015, Davanum Srinivas  wrote:

> Nova folks,
>
> We have this review in oslo.utils:
> https://review.openstack.org/#/c/252898/
>
> There were failed effort in the past to cleanup in Nova:
> https://review.openstack.org/#/c/164753/
> https://review.openstack.org/#/c/197601/
>
> What do we do? Suggestions please.


Propose an effort to cleanup nova without inexplicably abandoning it
shortly thereafter?


>
> Thanks,
> Dims
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [oslo][nova][all] timeutils deprecation removals will break Nova

2015-12-20 Thread Davanum Srinivas 
Nova folks,

We have this review in oslo.utils:
https://review.openstack.org/#/c/252898/

There were failed effort in the past to cleanup in Nova:
https://review.openstack.org/#/c/164753/
https://review.openstack.org/#/c/197601/

What do we do? Suggestions please.

Thanks,
Dims

-- 
Davanum Srinivas :: https://twitter.com/dims

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev