@@ -221,6 +221,28 @@ under the License.
221221 check policies in the cloud. You can override this value for an individual health check
222222 policy.</para >
223223 </section >
224+ <section id =" rbd-primary-storage" >
225+ <title >Snaphotting, backups, cloning and System VMs for RBD Primary Storage</title >
226+ <note >
227+ <para >These new RBD features require at least librbd 0.61.7 (Cuttlefish) and libvirt 0.9.14
228+ on the KVM hypervisors.</para >
229+ </note >
230+ <para >With this release &PRODUCT; will leverage the features of RBD format 2. This allows
231+ snapshotting and backing up those snapshots.</para >
232+ <para >Backups of snapshots to Secondary Storage are full copies of the RBD snapshot,
233+ they are not RBD diffs. This because when restoring a backup of a snapshot it is not mandatory
234+ that this backup is deployed on RBD again, it could also be a NFS Primary Storage.</para >
235+ <para >Another key feature of RBD format 2 is cloning and with this release templates will
236+ be copied to Primary Storage once and using the cloning mechanism new disks will be cloned
237+ from this parent template. This saves space and decreases deployment time for Instances
238+ dramatically.</para >
239+ <para >Before this release a NFS Primary Storage was still required for running the System VMs
240+ from. The reason behind this was a so called 'patch disk' which was generated by the hypervisor
241+ which contained metadata for the System VM. The scripts generating this disk didn't support
242+ RBD and thus System VMs had to be deployed from NFS. With 4.2 instead of the patch disk a
243+ VirtIO serial console is used to pass meta information to System VMs. This enabled the deployment
244+ of System VMs on RBD Primary Storage.</para >
245+ </section >
224246 </section >
225247 <section id =" issues-fixed-4.2" >
226248 <title >Issues Fixed in 4.2.0</title >
0 commit comments