[pve-devel] [PATCH manager 2/3] pvereport: rework report contents

[Aaron Lauterer]

add:
* HA status
* ceph osd df tree
* ceph conf file and conf db
* ceph versions

removed:
* ceph status, as pveceph status is now printing the same information

Signed-off-by: Aaron Lauterer <a.lauterer at proxmox.com>
---

@Thomas, we did discuss using the cluster/ceph/metadata endpoint off
list for more information about running services and other stuff like
needed restarts after updates.

Since it returns a lot of JSON that needs to be filtered to be useful
and not littering the report, I will need a bit more time to see what
would be needed and how to filter for that.

For now with the changed pveceph status (ceph -s) output we already get
an overview if any expected services are not running and with `ceph
versions` we get an idea which versions and if multiple versions are
present in the cluster.

I think this is okay for now to get a good impression and quite a lot
more hints where to investigate further.

 PVE/Report.pm | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/PVE/Report.pm b/PVE/Report.pm
index 5ee3453d..f8d5e663 100644
--- a/PVE/Report.pm
+++ b/PVE/Report.pm
@@ -51,7 +51,8 @@ my $init_report_cmds = sub {
 	cluster => [
 	    'pvecm nodes',
 	    'pvecm status',
-	    'cat /etc/pve/corosync.conf 2>/dev/null'
+	    'cat /etc/pve/corosync.conf 2>/dev/null',
+	    'ha-manager status',
 	],
 	bios => [
 	    'dmidecode -t bios',
@@ -76,7 +77,9 @@ my $init_report_cmds = sub {
 
     if (-e '/etc/ceph/ceph.conf') {
 	# TODO: add (now working) rdb ls over all pools? really needed?
-	push @{$report_def->{volumes}}, 'ceph status', 'ceph osd status', 'ceph df', 'pveceph status', 'pveceph pool ls';
+	push @{$report_def->{volumes}}, 'pveceph status', 'ceph osd status',
+		'ceph df', 'ceph osd df tree', 'cat /etc/ceph/ceph.conf',
+		'ceph config dump', 'pveceph pool ls', 'ceph versions';
     }
 
     push @{$report_def->{disks}}, 'multipath -ll', 'multipath -v3'
-- 
2.20.1