From 6414296b3acb0bbd69ae80b7acafb46679c82baf Mon Sep 17 00:00:00 2001 From: Helga Velroyen <helgav@google.com> Date: Wed, 20 Mar 2013 15:25:33 +0100 Subject: [PATCH] Fixing some mistakes in design doc for space reporting - Use entities as examples for storage types that are actually storage types. - Fix mixing up 'external_storage' and 'exclusive_storage'. Signed-off-by: Helga Velroyen <helgav@google.com> Reviewed-by: Guido Trotter <ultrotter@google.com> --- doc/design-storagespace.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/design-storagespace.rst b/doc/design-storagespace.rst index 2d798a98d..f22546a5c 100644 --- a/doc/design-storagespace.rst +++ b/doc/design-storagespace.rst @@ -21,7 +21,7 @@ Configuration changes --------------------- Add a new attribute "enabled_storage_types" (type: list of strings) to the -cluster config which holds the types of storages, for example, "plain", "drbd", +cluster config which holds the types of storages, for example, "file", "rados", or "ext". We consider the first one of the list as the default type. For file storage, we'll report the storage space on the file storage dir, @@ -156,7 +156,7 @@ is set. That doesn't interact directly with this design, as the specific of how the free space is computed is not in the scope of this design. But the ``node info`` call contains the value of the ``exclusive_storage`` flag, which is currently only meaningful for the -LVM back-end. Additional flags like the ``external_storage`` flag +LVM back-end. Additional flags like the ``exclusive_storage`` flag for lvm might be useful for other storage types as well. We therefore extend the RPC call with <type>,<key> to <type>,<key>,<params> to include any storage-type specific parameters in the RPC call. -- GitLab