Hi all,
Scenario tests feature service dependency decorators in tests – so that a test
will run only if all required components are available.
I think we should extend them to all tests, including the API ones. For
instance Nova image tests depend on Glance, cinder attach/detach tests depend
+1 for decoupling Tempest from devstack
Openstack deployment tool is TripleO / Heat -so it would be good to have an
Heat template to deploy and configure Tempest
andrea
From: David Kranz [mailto:dkr...@redhat.com]
Sent: 12 February 2014 23:23
To: OpenStack Development Mailing List (not
Hi,
I’m working on a tempest blueprint to make tempest able to run 100% on keystone
v3 (or later versions) – the auth version to be used will be available via a
configuration switch.
The rationale is that Keystone V2 is deprecated in icehouse, V3 being the
primary version. Thus it would
Actually another point which needs fixing is in test_utils, the scenario_images
method should honour the glance_available configuration flag, it doesn't know.
I'll submit a fix for that.
andrea
-Original Message-----
From: Frittoli, Andrea (Cloud Services)
Sent: 07 February 201
Two days ago a patch I submitted introduced lazy load of glance httpin the api
section... That already may help.
I'm also working on a patch for lazy load of all clients in the manager
classes, but that may take some more time before it's available
Andrea
Sent from my tiny device
Jay
(not for usage questions)
Subject: Re: [openstack-dev] [qa][python-bindings] Reries on HTTP error in
python bindings
On Wed, Jan 15, 2014 at 5:28 AM, Frittoli, Andrea (Cloud Services)
wrote:
Hi all,
I've been working on a patch to ensure that all tempest tests are able to
Hi all,
I've been working on a patch to ensure that all tempest tests are able to
handle rate limiting errors with automatic retries [0].
API tests already implement retries, however scenario tests don't, the main
reason being that scenario tests rely on the official python bindings, most
of w
Hi,
I'm working on multi-keystone-api-version-tests which aims to provide the
ability to run tests using a configurable list of keystone API versions for
authentication.
If two versions of the API are configured, each test would be run using the
two versions.
In the gate, where we're sho
My 2 cents:
In the test the floating IP is created via neutron API and later checked via
nova API.
So the test is relying here (or trying to verify?) the network cache refresh
mechanism in nova.
This is something that we should test, but in a test dedicated to this.
The primary objective of tes
Hi folks,
While reviewing nova v3 tests, I realized that there is no nova V3 endpoint
defined in the catalog in devstack.
Test have to get the v2 URL, parse it, strip the "v2" string out and replace
it with a "v3" one.
Because of this I filed https://bugs.launchpad.net/devstack/+bug/1191798.
10 matches
Mail list logo