From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager v3 0/3] Add Ceph safety checks
Date: Thu, 17 Nov 2022 15:09:59 +0100 [thread overview]
Message-ID: <20221117141002.1653119-1-a.lauterer@proxmox.com> (raw)
The main motivation behind this series is to leverage several safety
checks that Ceph has to make sure it is ok to stop or destroy a service.
A new cmd-safety endpoint is added which is called from the GUI wherever
possible to show a warning.
This series needs commit 80deebd or newer from the librados2-perl
repo/package to work properly. Therefore we need to make sure to update
the min version in the dependencies.
changes:
- drop applied patches (librados2-perl)
- drop patches that adapt mon_command usage since with 80deebd
mon_command is a compat wrapper to provide the old behavior
- adapt api endpoint to the new mon_cmd
Aaron Lauterer (3):
api: ceph: add cmd-safety endpoint
ui: osd: warn if removal could be problematic
ui: osd: mon: mds: warn if stop/destroy actions are problematic
PVE/API2/Ceph.pm | 96 +++++++++++++++++++++
www/manager6/ceph/OSD.js | 140 ++++++++++++++++++++++++++-----
www/manager6/ceph/ServiceList.js | 104 ++++++++++++++++++++---
3 files changed, 308 insertions(+), 32 deletions(-)
--
2.30.2
next reply other threads:[~2022-11-17 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 14:09 Aaron Lauterer [this message]
2022-11-17 14:10 ` [pve-devel] [PATCH manager v3 1/3] api: ceph: add cmd-safety endpoint Aaron Lauterer
2022-11-17 14:10 ` [pve-devel] [PATCH manager v3 2/3] ui: osd: warn if removal could be problematic Aaron Lauterer
2022-11-17 14:10 ` [pve-devel] [PATCH manager v3 3/3] ui: osd: mon: mds: warn if stop/destroy actions are problematic Aaron Lauterer
2022-11-17 17:44 ` [pve-devel] applied: [PATCH manager v3 0/3] Add Ceph safety checks 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=20221117141002.1653119-1-a.lauterer@proxmox.com \
--to=a.lauterer@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