public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] applied: Re: [PATCH manager 2/3] pvereport: rework report contents
Date: Mon, 21 Dec 2020 17:06:29 +0100	[thread overview]
Message-ID: <a474f26f-7ed0-d988-5217-0a005afbf296@proxmox.com> (raw)
In-Reply-To: <20201221151351.30575-2-a.lauterer@proxmox.com>

On 21/12/2020 16:13, Aaron Lauterer wrote:
> 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@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.

yes, sure, that's what I said when proposing it - so yes, a filter is
required.
You could take a look at the web interface for relevant keys, there we
use that information already.

> 
> 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.

I mean you get at least the running versions, which is probably the most
important thing, so this is fine for me for now.

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

applied, thanks!




  reply	other threads:[~2020-12-21 16:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21 15:13 [pve-devel] [PATCH manager 1/3] pvereport: fix multipath inclusion Aaron Lauterer
2020-12-21 15:13 ` [pve-devel] [PATCH manager 2/3] pvereport: rework report contents Aaron Lauterer
2020-12-21 16:06   ` Thomas Lamprecht [this message]
2020-12-21 16:15   ` Thomas Lamprecht
2020-12-21 15:13 ` [pve-devel] [PATCH manager 3/3] pvereport: code cleanup, line length Aaron Lauterer
2020-12-21 16:08   ` [pve-devel] applied: " Thomas Lamprecht
2020-12-21 16:02 ` [pve-devel] applied: Re: [PATCH manager 1/3] pvereport: fix multipath inclusion 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=a474f26f-7ed0-d988-5217-0a005afbf296@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal