[openstack-dev] [Nova] Hypervisor CI requirement and deprecation plan

Bob Ball bob.ball at citrix.com
Tue Nov 26 09:48:06 UTC 2013

> -----Original Message-----
> From: Russell Bryant [mailto:rbryant at redhat.com]
> Sent: 25 November 2013 22:37
> To: openstack-dev at lists.openstack.org
> Subject: Re: [openstack-dev] [Nova] Hypervisor CI requirement and
> deprecation plan
> On 11/25/2013 05:19 PM, Matt Riedemann wrote:
> > I'll play devil's advocate here and ask this question before someone
> > else does.  I'm assuming that the requirement of a 'full' tempest run
> > means running this [1].  Is that correct?  It's just confusing sometimes
> > because there are other things in Tempest that aren't in the 'full' run,
> > like stress tests.
> >
> > [1] https://github.com/openstack/tempest/blob/master/tox.ini#L33
> >
> I think the short answer is, "whatever we're running against all Nova
> changes in the gate".

Can we strip this down a bit?  I don't see any benefit in running tests that verify Swift's behaviour other than where it interacts with Nova.

I hope we can safely say that we should run against all "gating" tests which require Nova?  Currently we run quite a number of tests in the gate that succeed even when Nova is not running as the gate isn't just for Nova but for all projects.

It would be trivial to kill Nova, run the full tempest and only enable those jobs for a new flavour which we must run.



More information about the OpenStack-dev mailing list