Eric Young 2dc5215321 ScaleIO: Prevent usage of unsafe volumes ... It is possible for volumes, created from storage pools which have zero-padding disabled, to contain previous data. This change prevents these volumes from being created by default. A user can override this behavior by acknowleding the possibility with a configuration option. This is a squash of the four commits that led to the final state in rocky to not allow the creation of any type of non-zero-padded volumes to be created. This adds a config option that defaults to the safe behavior. It is backporting a new config option, and a change in default behavior, but it should be acceptable in this case so that the security vulnerability can be addressed. Closes-Bug: #1784871 Change-Id: I62f8f48b1624fc9abb7427bd4ca51f7873d35b96 Closes-bug: #1699573 (cherry picked from commit f0cef07bef) (cherry picked from commit 6309c097e6)		2018-09-20 09:31:36 -05:00
..
drivers	ScaleIO: Prevent usage of unsafe volumes	2018-09-20 09:31:36 -05:00
flows	Move disk space check to run when needed	2018-06-07 17:00:28 +02:00
__init__.py	Fix volume retype with migration as non-admin	2017-02-16 15:12:08 -02:00
test_driver.py	Make Replication support Active-Active	2017-01-19 10:42:18 +01:00
test_manage_volume.py	Simplify calls to mock_object	2016-12-13 18:37:26 +01:00
test_replication_manager.py	Move service and cluster creation in test to utils	2017-01-19 10:42:23 +01:00
test_rpcapi.py	Switch ManageableSnaphots & ManageableVolumes list to OVO	2017-01-25 00:41:30 +00:00