Commit 6414296b authored by Helga Velroyen's avatar Helga Velroyen
Browse files

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: default avatarHelga Velroyen <helgav@google.com>
Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
parent 94309823
......@@ -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.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment