[openstack-dev] [tripleo] pingtest vs tempest

Giulio Fidente gfidente at redhat.com
Wed Sep 6 06:35:57 UTC 2017

On 09/05/2017 09:26 PM, Emilien Macchi wrote:
> On Wed, Apr 5, 2017 at 1:49 PM, Emilien Macchi <emilien at redhat.com> wrote:
> [...]
>> == Solutions
>> 1) Switch pingtest to Tempest run on some specific tests, with feature
>> parity of what we had with pingtest.
>> For example, we could imagine to run the scenarios that deploys VM and
>> boot from volume. It would test the same thing as pingtest (details
>> can be discussed here).
>> Each scenario would run more tests depending on the service that they
>> run (scenario001 is telemetry, so it would run some tempest tests for
>> Ceilometer, Aodh, Gnocchi, etc).
>> We should work at making the tempest run as short as possible, and the
>> close as possible from what we have with a pingtest.
> [...]
> 4 months later :-)
> We enabled Tempest on the following jobs:
> gate-tripleo-ci-centos-7-scenario001-multinode-oooq-container
> gate-tripleo-ci-centos-7-scenario002-multinode-oooq-container
> gate-tripleo-ci-centos-7-scenario003-multinode-oooq-container
> gate-tripleo-ci-centos-7-scenario004-multinode-oooq-container
> gate-tripleo-ci-centos-7-scenario001-multinode-oooq
> gate-tripleo-ci-centos-7-scenario002-multinode-oooq
> gate-tripleo-ci-centos-7-scenario003-multinode-oooq
> gate-tripleo-ci-centos-7-scenario004-multinode-oooq
> gate-tripleo-ci-centos-7-nonha-multinode-oooq
> gate-tripleo-ci-centos-7-containers-multinode
> It has a feature parity with what pingtest did.
> For example, scenario001 (focused on Telemetry) test boot from volume
> and the whole autoscsaling scenario from Telemetry services, so we can
> test end-to-end that our users can deploy autocsaling apps using
> OpenStack.

slightly OT but notable mention, scenario001/container is also the one
gating Ceph via ceph-ansible currently :D

... soon to convert scenario004/container as well
Giulio Fidente

More information about the OpenStack-dev mailing list