From 513da36a163be267295c18e701b716cffc5a0d38 Mon Sep 17 00:00:00 2001
From: James Page <james.page@ubuntu.com>
Date: Thu, 27 Aug 2020 11:15:41 +0100
Subject: [PATCH] Tidy configuration options

Update descriptions and align metadata-pool configuration option
with codebase. Metadata pools are used by CephFS for both replicated
and erasure-coded data pools.

Change-Id: Iee6ee64e7bd672f9932037bf91670d8f59083aa4
---
 src/config.yaml | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/src/config.yaml b/src/config.yaml
index c875baa..f6f48d9 100644
--- a/src/config.yaml
+++ b/src/config.yaml
@@ -76,7 +76,15 @@ options:
     default:
     type: string
     description: |
-      Optionally specify an existing rbd pool that cinder should map to.
+      Name of the data pool to be created/used. If not defined a data pool name
+      will be generated based on the name of the application.
+  metadata-pool:
+    type: string
+    default:
+    description: |
+      Name of the metadata pool to be created/used. If not defined a metadata
+      pool name will be generated based on the name of the application.
+      The metadata pool is always replicated, not erasure coded.
   pool-type:
     type: string
     default: replicated
@@ -90,14 +98,6 @@ options:
       Name for the EC profile to be created for the EC pools. If not defined
       a profile name will be generated based on the name of the pool used by
       the application.
-  ec-rbd-metadata-pool:
-    type: string
-    default:
-    description: |
-      Name of the metadata pool to be created (for RBD use-cases). If not
-      defined a metadata pool name will be generated based on the name of
-      the data pool used by the application.  The metadata pool is always
-      replicated, not erasure coded.
   ec-profile-k:
     type: int
     default: 1