From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs v2 4/5] cephx-migration: Introduce the helper
Date: Tue, 8 Sep 2026 17:39:30 +0200 [thread overview]
Message-ID: <20260908153932.577051-5-m.sandoval@proxmox.com> (raw)
In-Reply-To: <20260908153932.577051-1-m.sandoval@proxmox.com>
At this point the helper has not yet been introduced.
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
pveceph.adoc | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/pveceph.adoc b/pveceph.adoc
index 40ca16b..9eba9b3 100644
--- a/pveceph.adoc
+++ b/pveceph.adoc
@@ -1355,9 +1355,8 @@ to `aes256k` and, when all clients support it, disable the vulnerable method.
Migration Steps
^^^^^^^^^^^^^^^
-The migration helper checks the cluster, rotates keys, and resumes interrupted
-work. Review each dry run before applying its plan; add `--verbose` for full
-node, keyring, and device inventories.
+{pve} offers a helper which can handle the migration. The following steps can be
+performed on a single node.
Reruns do not rotate completed keys again. After each run, invoke the helper
without options to check the current state and follow the next steps it prints.
--
2.47.3
next prev parent reply other threads:[~2026-09-08 15:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 15:39 [PATCH docs v2 0/5] cephx-migration: Simplify docs Maximiliano Sandoval
2026-09-08 15:39 ` [PATCH docs v2 1/5] cephx-migration: Replace consumer with client Maximiliano Sandoval
2026-09-08 18:42 ` Thomas Lamprecht
2026-09-08 15:39 ` [PATCH docs v2 2/5] cephx-migration: Add link to CVE-2025-30156 Maximiliano Sandoval
2026-09-08 15:39 ` [PATCH docs v2 3/5] cephx-migration: Move all requirements into prelude Maximiliano Sandoval
2026-09-08 16:21 ` Jonas Theisen
2026-09-08 18:16 ` Thomas Lamprecht
2026-09-08 15:39 ` Maximiliano Sandoval [this message]
2026-09-08 15:39 ` [PATCH docs v2 5/5] cephx-migration: Simplify docs Maximiliano Sandoval
2026-09-08 18:33 ` 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=20260908153932.577051-5-m.sandoval@proxmox.com \
--to=m.sandoval@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.