Re: [openstack-dev] [requirements][release][FFE] Request for netaddr>=0.7.13 bump in g-r
Excerpts from Matt Riedemann's message of 2016-09-15 09:09:48 -0500: > There was a change introduced to nova in newton which requires a minimum > of netaddr 0.7.13. We've been testing with 0.7.18 from upper-constraints > so bumping the minimum from 0.7.12 to 0.7.13 shouldn't cause any issues. > > The g-r change is here: > > https://review.openstack.org/#/c/370833/ > > We're not going to revert the nova change since that would be riskier at > this point in the cycle since it landed before n-2. > After much discussion on IRC in both #openstack-release and #openstack-requirements, the release team made the call to go ahead with this requirements update. We will merge the change to the global requirements, and update nova before its RC1. Other projects that believe they have an issue and have not already tagged RC1 may also update their requirements list in their trees. Projects that have already tagged RC1 and libraries that use netaddr *do not* need to be updated right now. When we branch the requirements repo, it will trigger updates to any projects that have not already updated the min version for netaddr. We will consider those changes as bugs in the requirements specifications for newton, and tag point releases when there is another reason to create a new release of the project or library. Doug __ 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] [requirements][release][FFE] Request for netaddr>=0.7.13 bump in g-r
On 09/15/2016 09:39 AM, Matt Riedemann wrote: > > As I pointed out in the review, I don't think we'd need to re-release > those things, however, I think this would cause a problem for > stable/newton because the requirements repo doesn't have a stable/newton > branch yet, so this min version bump would go into that, and since those > libs/clients have cut stable/newton already, on their next reqs sync > they'd get that min version bump, which we generally want to avoid on > stable branches as some distros have frozen their packages - although to > be fair they should have been shipping packages from the > upper-constraints versions for newton, not the minimums since we only > test the upper bound. > I don't think this will hurt us like has happened in the past, I just wanted to put the breaks on this so we can get all the interested parties (releases and requirements teams) involved. This would be breaking our process at the last minute which has caused badness in the past. We (requirements) are working on divergent requirements which would allow for this, but that was for the ocata cycle. Distros I've checked so far won't have a problem with this anyway as they are using newer netaddr anyway (0.7.18 for both debian and gentoo at least). In short, if the releases and requirements teams are both fine with this, ok :D (and tonyb is on both...) -- -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature __ 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] [requirements][release][FFE] Request for netaddr>=0.7.13 bump in g-r
On 09/15/2016 10:30 AM, Matthew Thode wrote: > On 09/15/2016 09:09 AM, Matt Riedemann wrote: >> There was a change introduced to nova in newton which requires a minimum >> of netaddr 0.7.13. We've been testing with 0.7.18 from upper-constraints >> so bumping the minimum from 0.7.12 to 0.7.13 shouldn't cause any issues. >> >> The g-r change is here: >> >> https://review.openstack.org/#/c/370833/ >> >> We're not going to revert the nova change since that would be riskier at >> this point in the cycle since it landed before n-2. >> > > This is a hard ask and I can't really support it, mainly because of all > the things it impacts this late in the cycle. Is there ANY way we can > not merge this? > > just some of the things that would need to be re-released > > > networking-ovn (just had their rc1) > os-net-config > os-vif > oslo.config > oslo.serialization > oslo.utils > oslo.versionedobjects > oslo.vmware > python-neutronclient > wsme Actually, there is very little this impacts. Basically no systems use the g-r minimum except as a code comment. Yes, it will produce a patch to be merged on those projects, however the only project that needs to merge in is Nova, it's the only project that uses the function that will actually explode at that level. Given this is the lowest risk way to address this issue, far less risky than a barely tested Nova workaround, this is really the way things should move forward. Nothing is harmed in the release if there is a mix of 0.7.12 / 0.7.13 minimums. Doug is even proposing that we explicitly allow situations like that for the next cycle. Projects can merge and catch up in stable/newton post release if we feel consistency is important. -Sean -- Sean Dague http://dague.net __ 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] [requirements][release][FFE] Request for netaddr>=0.7.13 bump in g-r
On 9/15/2016 9:30 AM, Matthew Thode wrote: On 09/15/2016 09:09 AM, Matt Riedemann wrote: There was a change introduced to nova in newton which requires a minimum of netaddr 0.7.13. We've been testing with 0.7.18 from upper-constraints so bumping the minimum from 0.7.12 to 0.7.13 shouldn't cause any issues. The g-r change is here: https://review.openstack.org/#/c/370833/ We're not going to revert the nova change since that would be riskier at this point in the cycle since it landed before n-2. This is a hard ask and I can't really support it, mainly because of all the things it impacts this late in the cycle. Is there ANY way we can not merge this? just some of the things that would need to be re-released networking-ovn (just had their rc1) os-net-config os-vif oslo.config oslo.serialization oslo.utils oslo.versionedobjects oslo.vmware python-neutronclient wsme __ 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 As I pointed out in the review, I don't think we'd need to re-release those things, however, I think this would cause a problem for stable/newton because the requirements repo doesn't have a stable/newton branch yet, so this min version bump would go into that, and since those libs/clients have cut stable/newton already, on their next reqs sync they'd get that min version bump, which we generally want to avoid on stable branches as some distros have frozen their packages - although to be fair they should have been shipping packages from the upper-constraints versions for newton, not the minimums since we only test the upper bound. -- 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] [requirements][release][FFE] Request for netaddr>=0.7.13 bump in g-r
On 09/15/2016 09:09 AM, Matt Riedemann wrote: > There was a change introduced to nova in newton which requires a minimum > of netaddr 0.7.13. We've been testing with 0.7.18 from upper-constraints > so bumping the minimum from 0.7.12 to 0.7.13 shouldn't cause any issues. > > The g-r change is here: > > https://review.openstack.org/#/c/370833/ > > We're not going to revert the nova change since that would be riskier at > this point in the cycle since it landed before n-2. > This is a hard ask and I can't really support it, mainly because of all the things it impacts this late in the cycle. Is there ANY way we can not merge this? just some of the things that would need to be re-released networking-ovn (just had their rc1) os-net-config os-vif oslo.config oslo.serialization oslo.utils oslo.versionedobjects oslo.vmware python-neutronclient wsme -- -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature __ 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] [requirements][release][FFE] Request for netaddr>=0.7.13 bump in g-r
There was a change introduced to nova in newton which requires a minimum of netaddr 0.7.13. We've been testing with 0.7.18 from upper-constraints so bumping the minimum from 0.7.12 to 0.7.13 shouldn't cause any issues. The g-r change is here: https://review.openstack.org/#/c/370833/ We're not going to revert the nova change since that would be riskier at this point in the cycle since it landed before n-2. -- 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
