History

xing-yang 18744ba199 Tiramisu: replication group support This patch adds support for replication group. It is built upon the generic volume groups. It supports enable replication, disable replication, failover replication, and list replication targets. Client side patch is here: https://review.openstack.org/#/c/352229/ To test this server side patch using the client side patch: export OS_VOLUME_API_VERSION=3.38 Make sure the group type has group_replication_enabled or consistent_group_replication_enabled set in group specs, and the volume types have replication_enabled set in extra specs (to be compatible with Cheesecake). cinder group-type-show my_group_type +-------------+---------------------------------------+ \| Property \| Value \| +-------------+---------------------------------------+ \| description \| None \| \| group_specs \| group_replication_enabled : <is> True \| \| id \| 66462b5c-38e5-4a1a-88d6-7a7889ffec55 \| \| is_public \| True \| \| name \| my_group_type \| +-------------+---------------------------------------+ cinder type-show my_volume_type +---------------------------------+--------------------------------------+ \| Property \| Value \| +---------------------------------+--------------------------------------+ \| description \| None \| \| extra_specs \| replication_enabled : <is> True \| \| id \| 09c1ce01-87d5-489e-82c6-9f084107dc5c \| \| is_public \| True \| \| name \| my_volume_type \| \| os-volume-type-access:is_public \| True \| \| qos_specs_id \| None \| +---------------------------------+--------------------------------------+ Create a group: cinder group-create --name my_group my_group_type my_volume_type cinder group-show my_group Enable replication group on the primary storage: cinder group-enable-replication my_group Expected results: replication_status becomes “enabled”. Failover replication group to the secondary storage. If secondary-backend-id is not specified, it will go to the secondary-backend-id configured in cinder.conf: cinder group-failover-replication my_group If secondary-backend-id is specified (not “default”), it will go to the specified backend id: cinder group-failover-replication my_group --secondary-backend-id <backend_id> Expected results: replication_status becomes “failed-over”. Run failover replication group again to fail the group back to the primary storage: cinder group-failover-replication my_group --secondary-backend-id default Expected results: replication_status becomes “enabled”. Disable replication group: cinder group-disable-replication my_group Expected results: replication_status becomes “disabled”. APIImpact DocImpact Implements: blueprint replication-cg Change-Id: I4d488252bd670b3ebabbcc9f5e29e0e4e913765a		2017-04-30 22:49:13 -04:00
..
compliance	Use assertEqual/Less/Greater/In/IsNone	2016-07-04 17:58:16 +02:00
functional	Trivial fix typos	2017-05-17 10:57:40 +07:00
tempest	Merge "cleanup: remove DEVSTACK_CINDER_SECURE_DELETE"	2017-06-05 14:04:48 +00:00
unit	Tiramisu: replication group support	2017-04-30 22:49:13 -04:00
README.rst	Add a README in tests dir linked to devref html	2017-03-11 10:47:49 -07:00
__init__.py	Move unit tests into dedicated directory	2015-04-21 18:40:40 -06:00
fake_driver.py	Tiramisu: replication group support	2017-04-30 22:49:13 -04:00
fixtures.py	Copy StandardLogging fixture from Nova	2016-02-29 17:46:31 -05:00

README.rst

IMPORTANT DEFINITION OF TESTS IN CINDER

Cinder has a number of different test types, PLEASE be sure to refer to the Cinder Testing Docs to familiarize yourself with the various options before creating any new tests.

Please check Cinder-Testing <https://docs.openstack.org/developer/cinder/devref/testing.html>