From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 1/2] pveceph: also mention editing of pools
Date: Wed, 21 Apr 2021 12:52:13 +0200 [thread overview]
Message-ID: <20210421105214.22099-1-d.csapak@proxmox.com> (raw)
We can now edit them as well so write that.
Also mention that the 'add as storage' checkbox is only visible when
creating a pool.
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
pveceph.adoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/pveceph.adoc b/pveceph.adoc
index 9ef268b..e15028a 100644
--- a/pveceph.adoc
+++ b/pveceph.adoc
@@ -450,8 +450,8 @@ A pool is a logical group for storing objects. It holds **P**lacement
**G**roups (`PG`, `pg_num`), a collection of objects.
-Create Pools
-~~~~~~~~~~~~
+Create and edit Pools
+~~~~~~~~~~~~~~~~~~~~~
[thumbnail="screenshot/gui-ceph-pools.png"]
@@ -497,7 +497,7 @@ PG Autoscale Mode:: The automatic PG scaling mode footnoteref:[autoscaler] of
the pool. If set to `warn`, it produces a warning message when a pool
has a non-optimal PG count. Default: `warn`.
Add as Storage:: Configure a VM or container storage using the new pool.
-Default: `true`.
+Default: `true` (only visible on creation).
.Advanced Options
Min. Size:: The minimum number of replicas per object. Ceph will reject I/O on
--
2.20.1
next reply other threads:[~2021-04-21 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 10:52 Dominik Csapak [this message]
2021-04-21 10:52 ` [pve-devel] [PATCH docs 2/2] pveceph: order the fields according to gui Dominik Csapak
2021-04-21 12:14 ` [pve-devel] applied: " Thomas Lamprecht
2021-04-21 12:14 ` [pve-devel] applied: [PATCH docs 1/2] pveceph: also mention editing of pools Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210421105214.22099-1-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox