Open Stack

On 21/02/2017 15:25, Andrea Frittoli wrote:
> Hi Graham,
>
> sorry about that, and good catch.
> You are right, that's a stable interface so that change should not have
> landed.
>
> andrea
>
> On Tue, Feb 21, 2017 at 2:51 PM Hayes, Graham <graham.hayes at hpe.com
> <mailto:graham.hayes at hpe.com>> wrote:
>
>     Hi.
>
>     https://review.openstack.org/#/c/434304/ landed yesterday, which was a
>     change to the stable interface for tempest plugins.
>
>     It also took out the designate gate.
>
>     Is this interface stable? - If so, there should have been at least some
>     deprecation cycle, notification, or something.
>
>     Revert has been proposed - https://review.openstack.org/#/c/436612/
>
>     Can someone clarify what the "stable" in "Stable APIs" listed here [1]
>     means?
>
>     - Graham
>
>     1 -
>     https://docs.openstack.org/developer/tempest/plugin.html#stable-tempest-apis-plugins-may-use
>
>     __________________________________________________________________________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe:
>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

The revert above still hasn't merged.

The QA team blocked a change that updated HTTP status code, but removed
a stable interface with no deprecation.

The revert needs to land, now, and then the QA team can debate
deprecation / removal.

To stop this happening in the future, can we get tempest to gate on some
tempest plugins?

Just a gate job that runs when any code in the designated stable
sections of tempest change would be incredibly useful.

Thanks,

Graham