From 87c7621abb22a72af631dd62cb278efdaf469be5 Mon Sep 17 00:00:00 2001 From: Helga Velroyen <helgav@google.com> Date: Wed, 17 Apr 2013 19:56:47 +0200 Subject: [PATCH] Storage type design doc: ipolicy vs. enabled disk templates Adding the design decision regarding the consistency of the enabled disk templates in the ipolicy and in the cluster config. Signed-off-by: Helga Velroyen <helgav@google.com> Reviewed-by: Klaus Aehlig <aehlig@google.com> --- doc/design-storagetypes.rst | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/doc/design-storagetypes.rst b/doc/design-storagetypes.rst index ee03aebf7..471c8195e 100644 --- a/doc/design-storagetypes.rst +++ b/doc/design-storagetypes.rst @@ -49,8 +49,11 @@ this design doc. Note that it is possible to force an instance to use a disk template that is not allowed by the ipolicy. This is not possible if the template is not enabled by the cluster. -FIXME: In what way should verification between the enabled disk templates in -the cluster and in the ipolicy take place? +The ipolicy also contains a list of enabled disk templates. Since the cluster- +wide enabled disk templates should be a stronger constraint, the list of +enabled disk templates in the ipolicy should be a subset of those. In case the +user tries to create an inconsistent situation here, gnt-cluster should emit +a warning. We consider the first disk template in the list to be the default template for instance creation and storage reporting. This will remove the need to specify -- GitLab