[Openstack-operators] Identifying upgrade impacts and giving feedback

Syed Armani syed.armani at hastexo.com
Thu Jan 9 16:12:52 UTC 2014



On Thu, Jan 9, 2014 at 7:06 PM, Tim Bell <Tim.Bell at cern.ch> 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 ?
> Tim
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20140109/0d94a834/attachment.html>

More information about the OpenStack-operators mailing list