History

wangxiyuan d304f621c2 Don't change volume's status when create backups from snapshots when users try to create a backup from a snapshot, the volume related to the snapshot is set to backing-up during the action and can't be used for other actions. When create a backup from a large snapshot, such as larger than 1 TB, it will cost few hours generally. It's really a problem that the volume is not available for such a long time. If the snapshot is provided, we change the status of the snapshot; otherwise, we change the status of the volume as usual. This patch added "backing-up" status for snapshot as well DocImpact Change-Id: I86d34c470fabbf4132b5e004d9f368e751c893a5 Closes-bug: #1670541		2017-03-21 09:46:33 +08:00
..
compliance	Use assertEqual/Less/Greater/In/IsNone	2016-07-04 17:58:16 +02:00
functional	[1/4]Reset generic volume group status	2016-12-23 22:58:48 +08:00
tempest	Switch to use stable data_utils	2017-03-07 12:24:30 -08:00
unit	Don't change volume's status when create backups from snapshots	2017-03-21 09:46:33 +08:00
README.rst	Add a README in tests dir linked to devref html	2017-03-11 10:47:49 -07:00
__init__.py	…
fake_driver.py	Rename AddFCZone and RemoveFCZone according to PEP 8	2017-01-09 11:22:19 +02: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>