> -Original Message-
> From: GHANSHYAM MANN [mailto:ghanshyamm...@gmail.com]
> Sent: Wednesday, June 15, 2016 9:59 PM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [tempest][nova][defcore] Add option
I do think negative tests should live on, most likely in their own
tempest-plugin based repository. However, I'm not sure that I agree with the
reason being because they are functional tests rather than integration. If you
look at the current tests, one could argue that many non-Nova tests are
Hi folks,
While running Tempest I ran into a bit of interesting behavior. As part of the
Tempest auth client, checks are performed to assure the token in use is still
valid. When parsing the expiry timestamp from the auth response, a very
specific datetime format is expected for Keystone v2
This is still a partially formed idea, but one of the ways I've thought of
solving the timeout issue is by using aggregate data from previous results. Any
of the event systems (Ceilometer, StackTach) should allow you to create models
of what an inbounds server build (or any action) time per
@lists.openstack.org
Subject: Re: [openstack-dev] [qa] Selecting Compute tests by driver/hypervisor
On 04/21/2014 06:52 PM, Daryl Walleck wrote:
I nearly opened a spec for this, but I’d really like to get some
feedback first. One of the challenges I’ve seen lately for Nova teams
not using KVM or Xen
I nearly opened a spec for this, but I'd really like to get some feedback
first. One of the challenges I've seen lately for Nova teams not using KVM or
Xen (Ironic and LXC are just a few) is how to properly run the subset of
Compute tests that will run for their hypervisor or driver. Regexes
Hi David,
I'm actually starting to ramp up on Ironic, so once I have my dev environment
up and running, I'll be more than glad to have a look at any Tempest/Ironic
reviews.
Daryl
From: David Kranz [dkr...@redhat.com]
Sent: Monday, March 31, 2014 3:46 PM
To:
Hi Adam,
I think the steps you've completed so far are the foundation for testers like
myself to be able to really dive in and start kicking the tires of Ironic.
Having an easily repeatable way to generate test environments makes a huge
impact in where I spend my time (environments vs actual