Open Stack

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-request at 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