From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <a.lauterer@proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 3509A612F7 for <pve-devel@lists.proxmox.com>; Fri, 18 Feb 2022 12:39:00 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 24B9E2938C for <pve-devel@lists.proxmox.com>; Fri, 18 Feb 2022 12:38:30 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 1BC952934F for <pve-devel@lists.proxmox.com>; Fri, 18 Feb 2022 12:38:29 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id E038E45FF7 for <pve-devel@lists.proxmox.com>; Fri, 18 Feb 2022 12:38:28 +0100 (CET) From: Aaron Lauterer <a.lauterer@proxmox.com> To: pve-devel@lists.proxmox.com Date: Fri, 18 Feb 2022 12:38:21 +0100 Message-Id: <20220218113827.1415641-1-a.lauterer@proxmox.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.012 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pve-devel] [PATCH librados2-perl manager 0/6] Add Ceph safety checks X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Fri, 18 Feb 2022 11:39:00 -0000 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