On Thursday, 20 September 2018 04:47:20 CEST Matthew Treinish wrote: > On Thu, Sep 20, 2018 at 11:11:12AM +0900, Ghanshyam Mann wrote: > > ---- On Wed, 19 Sep 2018 23:29:46 +0900 Monty Taylor > > <mord...@inaugust.com> wrote ----> > > > On 09/19/2018 09:23 AM, Monty Taylor wrote: > > > > On 09/19/2018 08:25 AM, Chris Dent wrote: > > > >> I have a patch in progress to add some simple integration tests to > > > >> > > > >> placement: > > > >> https://review.openstack.org/#/c/601614/ > > > >> > > > >> They use https://github.com/cdent/gabbi-tempest . The idea is that > > > >> the method for adding more tests is to simply add more yaml in > > > >> gate/gabbits, without needing to worry about adding to or think > > > >> about tempest. > > > >> > > > >> What I have at that patch works; there are two yaml files, one of > > > >> which goes through the process of confirming the existence of a > > > >> resource provider and inventory, booting a server, seeing a change > > > >> in allocations, resizing the server, seeing a change in allocations. > > > >> > > > >> But this is kludgy in a variety of ways and I'm hoping to get some > > > >> help or pointers to the right way. I'm posting here instead of > > > >> asking in IRC as I assume other people confront these same > > > >> confusions. The issues: > > > >> > > > >> * The associated playbooks are cargo-culted from stuff labelled > > > >> > > > >> "legacy" that I was able to find in nova's jobs. I get the > > > >> impression that these are more verbose and duplicative than they > > > >> need to be and are not aligned with modern zuul v3 coolness. > > > > > > > > Yes. Your life will be much better if you do not make more legacy > > > > jobs. > > > > They are brittle and hard to work with. > > > > > > > > New jobs should either use the devstack base job, the > > > > devstack-tempest > > > > base job or the devstack-tox-functional base job - depending on what > > > > things are intended. > > > > +1. All the base job from Tempest and Devstack (except grenade which is in > > progress) are available to use as base for legacy jobs. Using > > devstack-temepst in your patch is right things. In addition, you need to > > mention the tox_envlist as all-plugins to make tempest_test_regex work. I > > commented on review. > No, all-plugins is incorrect and should never be used. It's only there for > legacy support, it is deprecated and I thought we pushed a patch to > indicating that (but I can't find it).
This one? https://review.openstack.org/#/c/543974/ Ciao -- Luigi __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
