John Ferlan b975afc725 storage: Allow inputvol to be encrypted ... https://bugzilla.redhat.com/show_bug.cgi?id=1613737 When processing the inputvol for encryption, we need to handle the case where the inputvol is encrypted. This then allows for the encrypted inputvol to be used either for an output encrypted volume or an output volume of some XML provided type. Add tests to show the various conversion options when either input or output is encrypted. This includes when both are encrypted. Signed-off-by: John Ferlan <jferlan@redhat.com> ACKed-by: Michal Privoznik <mprivozn@redhat.com>		2018-09-12 07:24:04 -04:00
..
vol-encrypt1.xml	storage: Allow inputvol to be encrypted	2018-09-12 07:24:04 -04:00
vol-encrypt2.xml	storage: Allow inputvol to be encrypted	2018-09-12 07:24:04 -04:00
vol-file-backing.xml
vol-file-iso.xml
vol-file-naming.xml
vol-file-qcow2.xml	storage: Allow for inputvol to have any format for encryption	2018-09-12 07:24:04 -04:00
vol-file.xml
vol-gluster-dir-neg-uid.xml
vol-gluster-dir.xml
vol-logical-backing.xml
vol-logical.xml
vol-luks-cipher.xml
vol-luks-convert.xml	storage: Add support for using inputvol for encryption	2018-06-26 14:02:43 -04:00
vol-luks.xml
vol-partition.xml
vol-qcow2-0.10-lazy.xml
vol-qcow2-1.1.xml
vol-qcow2-encryption.xml
vol-qcow2-lazy.xml
vol-qcow2-nobacking.xml
vol-qcow2-nocapacity-backing.xml
vol-qcow2-nocapacity.xml
vol-qcow2-nocow.xml
vol-qcow2-zerocapacity.xml
vol-qcow2.xml
vol-sheepdog.xml