From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH storage/widget-toolkit 0/2] List all OSDs on disk
Date: Tue, 22 Aug 2023 11:04:54 +0200 [thread overview]
Message-ID: <20230822090456.929773-1-a.lauterer@proxmox.com> (raw)
It is possible to have multiple OSD daemons on a single disk. This is
useful if fast NVME drives are used to utilize their full potential.
For these situations we want to list all OSD daemons that are located on
the disk in the disk panel of the node.
I added a new 'osdid-list' parameter to the Disks GET API endpoint for
this.
We can probably deprecate/remove the 'osdid' the next time we can
introduce breaking API changes.
storage: Aaron Lauterer (1):
disks: get: add osdid-list return parameter
src/PVE/API2/Disks.pm | 6 +++-
src/PVE/Diskmanage.pm | 10 ++++++
.../disk_tests/cciss/disklist_expected.json | 1 +
.../hdd_smart/disklist_expected.json | 2 ++
.../nvme_smart/disklist_expected.json | 1 +
.../disk_tests/sas/disklist_expected.json | 1 +
.../disk_tests/sas_ssd/disklist_expected.json | 1 +
.../ssd_smart/disklist_expected.json | 5 +++
.../disk_tests/usages/disklist_expected.json | 32 +++++++++++++------
9 files changed, 49 insertions(+), 10 deletions(-)
widget-toolkit: Aaron Lauterer (1):
DiskList: render osdid-list if present
src/panel/DiskList.js | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
--
2.39.2
next reply other threads:[~2023-08-22 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 9:04 Aaron Lauterer [this message]
2023-08-22 9:04 ` [pve-devel] [PATCH storage 1/2] disks: get: add osdid-list return parameter Aaron Lauterer
2023-08-22 9:04 ` [pve-devel] [PATCH widget-toolkit 2/2] DiskList: render osdid-list if present Aaron Lauterer
2023-09-28 13:21 ` [pve-devel] [PATCH storage/widget-toolkit 0/2] List all OSDs on disk Aaron Lauterer
2023-11-13 16:01 ` [pve-devel] applied.series: " 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=20230822090456.929773-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal