Open Stack

On 21 December 2015 at 04:57, Davanum Srinivas <davanum at gmail.com> 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 <rbtcollins at hpe.com>
Distinguished Technologist
HP Converged Cloud