docs: Add news article for volume encryption modifications

Include both the domain and storage modifications in a "Removed
features" section as well as describing the improvement to allow
using a raw input volume to create the luks encrypted volume.

Signed-off-by: John Ferlan <jferlan@redhat.com>
ACKed-by: Michal Privoznik <mprivozn@redhat.com>

diff --git a/docs/news.xml b/docs/news.xml
index a32d2b88a5b0a5ff8eba1b09143b727563414e3b..468d34093acf990ad895129806038cdc9124c48f 100644 (file)
--- a/docs/news.xml
+++ b/docs/news.xml
@@ -62,6 +62,21 @@
         </description>
       </change>
     </section>
+    <section title="Removed features">
+      <change>
+        <summary>
+          Remove support for qcow/default encrypted volumes
+        </summary>
+        <description>
+          Disallow using a qcow encrypted volume for the guest and
+          disallow creation of the qcow or default encrypted volume
+          from the storage driver. Support for qcow encrypted volumes
+          has been phasing out since QEMU 2.3 and by QEMU 2.9 creation
+          of a qcow encrypted volume via qemu-img required usage of
+          secret objects, but that support was never added to libvirt.
+        </description>
+      </change>
+    </section>
     <section title="Improvements">
       <change>
         <summary>
@@ -105,6 +120,16 @@
           guest.
         </description>
       </change>
+      <change>
+        <summary>
+          Add support to use an raw input volume for encryption
+        </summary>
+        <description>
+          It is now possible to provide a raw input volume as input for
+          to generate a luks encrypted volume via either virsh vol-create-from
+          or virStorageVolCreateXMLFrom.
+        </description>
+      </change>
     </section>
     <section title="Bug fixes">
       <change>