71eb23f046
* Update tempest from branch 'master'
to 0e17064987bb58c42bc0d9b226d2124ceeed1d49
- Merge "[Cinder] Preparation for supporting Cinder replication testing"
- [Cinder] Preparation for supporting Cinder replication testing
This patch introduces a new configuration option `replication`
under the [volume-feature-enabled] group in Tempest. It enables
toggling of replication-related test execution.
It also adds support for the `failover_host` admin action in the
volume v3 services client, allowing tests to trigger failover
operations on Cinder backend hosts.
A waiter utility was added to wait for a volume to reach a specific
replication status. This will be used to validate replication state
transitions such as enabled and failed-over.
Unit tests have been added for both the new waiter function
and the service client method.
Release notes are included to document the new configuration option
and the service client/waiter additions.
This change is a preparatory step toward implementing volume
replication tests in the cinder-tempest-plugin repository.
This enables the Tempest framework to support upcoming Cinder
replication tests.
Change-Id: I0727e89a0f90d10d19e0e9ea16ebea3a3a90bc43
Signed-off-by: lkuchlan <lkuchlan@redhat.com>
OpenStack
OpenStack is a collection of interoperable components that can be deployed to provide computing, networking and storage resources. Those infrastructure resources can then be accessed by end users through programmable APIs.
This repository just represents OpenStack as a collection of git submodules. You can find the repositories for individual components at: https://opendev.org/openstack
You can learn more about the various components in OpenStack at: https://openstack.org/software
To learn more about how to contribute to OpenStack, please head to our Contributor portal: https://www.openstack.org/community/
To learn more about how OpenStack is governed, you can visit: https://governance.openstack.org/
Why this repository ?
Our continuous integration system, Zuul, gates all of the contained projects in an effective single timeline. This means that OpenStack, across all of the projects, does already have a sequence of combinations that have been explicitly tested, but it's non-trivial to go from a single commit of a particular project to the commits that were tested with it.
Gerrit's submodule tracking feature will update a super project every time a subproject is updated, so the specific sequence created by zuul will be captured by the super project commits.
This repo is intended to be used in a read-only manner. Any commit in this repo will get a collection of commits in the other repos that have explicitly been tested with each other, if that sort of thing is important to you.