Open Stack

One final status update on this.
We will proceed now with refactoring the tempest scenario base class.

- 17 patches merged
- 3 patches ready (on master)
- 3 patches ready (on stable branches)
- 3 extra patches for data_utils

Details: https://etherpad.openstack.org/p/tempest-manager-plugins

andrea

On Fri, Mar 24, 2017 at 2:55 PM Andrea Frittoli <andrea.frittoli at gmail.com>
wrote:

> Status update on the scenario manager base class:
>
> - 13 patches merged
> - 6 patches ready (on master)
> - 2 patches ready (on stable branches)
>
> Details: https://etherpad.openstack.org/p/tempest-manager-plugins
>
> I changed the subject to include only the projects that have outstanding
> patches related to this.
>
> thank you
>
> andrea
>
> On Sat, Mar 18, 2017 at 12:04 PM Andrea Frittoli <
> andrea.frittoli at gmail.com> wrote:
>
> Status update.
>
> Thanks to all your work, we are getting close to finishing this work!
>
> - 12 patches merged
> - 7 patches ready, pending approval
> - 2 patches (on stable branches) with a pep8 failure to be fixed
>
> Details: https://etherpad.openstack.org/p/tempest-manager-plugins
>
> There are still a few patches that need a review, any help
> would be much appreciated!
>
> Thank you
>
> andrea
>
> On Wed, Mar 15, 2017 at 3:56 PM Andrea Frittoli <andrea.frittoli at gmail.com>
> wrote:
>
> On Wed, Mar 15, 2017 at 11:38 AM Dmitry Tantsur <dtantsur at redhat.com>
> wrote:
>
> On 02/27/2017 12:34 PM, Andrea Frittoli wrote:
> > Hello folks,
> >
> > TL;DR: if today you import manager,py from tempest.scenario please
> maintain a
> > copy of [0] in tree until further notice.
>
> Hi!
>
> I hope it is pretty obvious, but just to be clear. Anything that this
> copied
> file uses should be treated more or less as a stable API by the QA team
> during
> the whole transition period. The last thing we want to happen is for this
> file
> to break all the time because its dependencies (imports, functions,
> classes it
> uses) are not stable.
>
> If it's not the case, please update it, and let us know the git hash to
> use to
> grab the final version of the file.
>
>
> Your code depends on manager.py and its dependencies today,
> and copying that in-tree removes at least one of the dependencies.
>
> The only case were you're in a worse situation is if one of the imports is
> removed / renamed,
> and we'll do our best to avoid that.
>
> My recommendation would be to trim down your copy of manager.py to the
> bare minimum you
> need, which is likely to be much smaller than the whole module.
>
>
> Thanks for understanding!
>
> __________________________________________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170406/d1f9ec8c/attachment.html>