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: [PATCH manager v5 0/3] Ceph OSD: add detail infos
Date: Wed, 15 Mar 2023 18:26:49 +0100 [thread overview]
Message-ID: <7f102774-b375-7d8a-e01c-c5eb75b7312a@proxmox.com> (raw)
In-Reply-To: <20221212121451.877054-1-a.lauterer@proxmox.com>
Am 12/12/2022 um 13:14 schrieb Aaron Lauterer:
> This patch series adds 2 new API endpoints for OSDs to fetch more
> detailed information about a single OSD. One for overall information and
> one for a single volume (block, db, wal).
>
> More in the actual patches.
>
> Series got [0]:
> Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>
> Tested-by: Dominik Csapak <d.csapak@proxmox.com>
with above..
> Aaron Lauterer (3):
> api ceph osd: add OSD index, metadata and lv-info
> ui utils: add renderer for ceph osd addresses
> ui: osd: add details window
>
> PVE/API2/Ceph/OSD.pm | 324 ++++++++++++++++++++++++++++++++
> www/manager6/Makefile | 1 +
> www/manager6/Utils.js | 15 ++
> www/manager6/ceph/OSD.js | 26 +++
> www/manager6/ceph/OSDDetails.js | 280 +++++++++++++++++++++++++++
> 5 files changed, 646 insertions(+)
> create mode 100644 www/manager6/ceph/OSDDetails.js
>
..applied, thanks!
prev parent reply other threads:[~2023-03-15 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 12:14 [pve-devel] " Aaron Lauterer
2022-12-12 12:14 ` [pve-devel] [PATCH manager v5 1/3] api ceph osd: add OSD index, metadata and lv-info Aaron Lauterer
2022-12-12 12:14 ` [pve-devel] [PATCH manager v5 2/3] ui utils: add renderer for ceph osd addresses Aaron Lauterer
2022-12-12 12:14 ` [pve-devel] [PATCH manager v5 3/3] ui: osd: add details window Aaron Lauterer
2023-02-08 10:00 ` [pve-devel] [PATCH manager v5 0/3] Ceph OSD: add detail infos Aaron Lauterer
2023-03-15 17:26 ` Thomas Lamprecht [this message]
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=7f102774-b375-7d8a-e01c-c5eb75b7312a@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