From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH librados2-perl manager 0/6] Add Ceph safety checks
Date: Fri, 18 Feb 2022 12:38:21 +0100 [thread overview]
Message-ID: <20220218113827.1415641-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.
For this to work, the librados2-perl needs to be adapted as the Ceph API
will return a non-zero return value and will also present a human readable
explanation in the status message.
Therefore, when querying such data, we do not want to die when we
receive a non-zero return value but return everything we got, return
value, status message and data to then present that to the user.
librados2-perl: Aaron Lauterer (2):
mon_command: free outs buffer
mon_command: optionally ignore errors and return hashmap
PVE/RADOS.pm | 37 ++++++++++++++++++++++---------------
RADOS.xs | 30 ++++++++++++++++++++++++------
2 files changed, 46 insertions(+), 21 deletions(-)
manager: Aaron Lauterer (4):
api: osd: force mon_command to scalar context
api: mon: mds: osd: add safety check endpoints
ui: osd: warn if removal could be problematic
ui: osd: mon: mds: warn if stop/destroy actions are problematic
PVE/API2/Ceph/MDS.pm | 50 ++++++++++++
PVE/API2/Ceph/MON.pm | 100 +++++++++++++++++++++++
PVE/API2/Ceph/OSD.pm | 102 +++++++++++++++++++++++-
www/manager6/ceph/OSD.js | 132 ++++++++++++++++++++++++++-----
www/manager6/ceph/ServiceList.js | 94 +++++++++++++++++++---
5 files changed, 446 insertions(+), 32 deletions(-)
--
2.30.2
next reply other threads:[~2022-02-18 11:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 11:38 Aaron Lauterer [this message]
2022-02-18 11:38 ` [pve-devel] [PATCH librados2-perl 1/6] mon_command: free outs buffer Aaron Lauterer
2022-02-21 15:35 ` Thomas Lamprecht
2022-02-18 11:38 ` [pve-devel] [PATCH librados2-perl 2/6] mon_command: optionally ignore errors and return hashmap Aaron Lauterer
2022-02-21 15:44 ` Thomas Lamprecht
2022-02-22 12:42 ` Aaron Lauterer
2022-02-18 11:38 ` [pve-devel] [PATCH manager 3/6] api: osd: force mon_command to scalar context Aaron Lauterer
2022-02-18 11:38 ` [pve-devel] [PATCH manager 4/6] api: mon: mds: osd: add safety check endpoints Aaron Lauterer
2022-02-22 8:44 ` Thomas Lamprecht
2022-03-14 16:49 ` Aaron Lauterer
2022-03-14 17:02 ` Thomas Lamprecht
2022-02-18 11:38 ` [pve-devel] [PATCH manager 5/6] ui: osd: warn if removal could be problematic Aaron Lauterer
2022-02-24 12:46 ` Thomas Lamprecht
2022-02-18 11:38 ` [pve-devel] [PATCH manager 6/6] ui: osd: mon: mds: warn if stop/destroy actions are problematic Aaron Lauterer
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=20220218113827.1415641-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