From 8c3986df81f1ba87cf9a2a36e8d4dfb168a619d9 Mon Sep 17 00:00:00 2001 From: Wido den Hollander Date: Mon, 2 Sep 2013 22:03:25 +0200 Subject: [PATCH] docs: Add more information about RBD cloning to the Release Notes --- docs/en-US/Release_Notes.xml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/en-US/Release_Notes.xml b/docs/en-US/Release_Notes.xml index d64d4909f85..9ee70119676 100644 --- a/docs/en-US/Release_Notes.xml +++ b/docs/en-US/Release_Notes.xml @@ -237,6 +237,10 @@ under the License. copied to Primary Storage once and using the cloning mechanism new disks will be cloned from this parent template. This saves space and decreases deployment time for Instances dramatically. + Cloning will however only work with new templates and when they are freshly downloaded + to primary storage. Templates currently stored on RBD Primary Storage are in RBD format 1 + which does not support cloning. Loglevel debug on the Agent will show if cloning is used + when deploying a template or not. Before this release a NFS Primary Storage was still required for running the System VMs from. The reason behind this was a so called 'patch disk' which was generated by the hypervisor which contained metadata for the System VM. The scripts generating this disk