[Openstack-operators] Identifying upgrade impacts and giving feedback

David Kranz dkranz at redhat.com
Thu Jan 9 16:10:21 UTC 2014

On 01/09/2014 11:03 AM, Álvaro López García wrote:
> On Thu 09 Jan 2014 (13:36), Tim Bell wrote:
>> There has been some discussion on the openstack-dev list recently (http://lists.openstack.org/pipermail/openstack-dev/2014-January/023254.html) on how we can identify changes that could impact upgrades (such as incompatibilities or difficult migrations). The proposal that has come out of that is that developers posting changes where suspect potential issues can be tagged with UpgradeImpact and this would send a mail to the operators list.
>> Giving feedback from operators at review time gives the opportunity to catch some of these items early. Reverting a patch or modifying it at this stage is much cheaper. Since some sites are not seeing the code until the next major release, a revert at this point is a very disruptive option.
>> The proposal in https://review.openstack.org/#/c/65685 is that this could be sent to openstack-operators.
>> There is a risk of some additional mail traffic but there is also an opportunity to contribute to smooth operations of OpenStack clouds by giving feedback during the review process.
>> If the volume becomes too high, an alternative list could be proposed.
>> Any thoughts ?
> I'd totally +1 this. If traffic becomes too heavy we can always switch
> to another mailing list (I think this was the approach with the
> DocImpact flag).
> Regards,
I can't see volume being a problem. If we are being overwhelmed by mail 
about incompatible changes that have to be dealt with, the mail will be 
the least of our problems :-) .


More information about the OpenStack-operators mailing list