oVirt includes an option to wipe a disk after it is deleted to securely erase the disk image. To perform this we do a simple overwrite, however we may need to perform a more secure erasure for security and compliance reasons. (eg. PCI compliance etc) We should mirror the work performed by the libvirt team in which they provide a number of algorithms to use when wiping an image. http://www.redhat.com/archives/libvir-list/2012-January/msg00070.html
*** Bug 1014324 has been marked as a duplicate of this bug. ***
The customer requested a status as this is dependent on a VDI implementation.
*** Bug 981626 has been marked as a duplicate of this bug. ***
This is an RFE targeted for 4.1. Idan is working on it, but the work is being done on the code, not on bugzilla, so there aren't too many updates here. Reducing priority to HIGH to avoid nagging emails from nagging whines.
Moving to MODIFIED as BZ #1367806 upstream is already being tested.
Yaniv, please note that Bug 1367806 only adds blkdiscard as an option to wipe volumes, but it is not the default option. BZ 1475780 is responsible for making it the default wiping method.
Yaniv - please see comment 27 (was missing a needinfo, probably). I think this should be moved back to ASSIGNED.
ATM, this is an available via optional configuration. Setting it to the default is pending the scale's team help on verifying it's usefulness/safety.
https://bugzilla.redhat.com/show_bug.cgi?id=1475780 - VERIFIED Used the XtremIO storage provider: XtremIO Storage Management Application © Copyright 2009-2016 XtremIO. All rights reserved. Version: 4.2.1 build 7 Moving to VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:1488
BZ<2>Jira Resync