From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH manager, docs 0/7] Ceph: add RBD Namespace management
Date: Mon, 23 Dec 2024 17:02:46 +0100 [thread overview]
Message-ID: <40cef2bf-bf9d-49b2-afd5-d13980f73cce@proxmox.com> (raw)
In-Reply-To: <20241206135514.170226-1-a.lauterer@proxmox.com>
sent a v2:
https://lore.proxmox.com/pve-devel/20241223160008.218710-1-a.lauterer@proxmox.com/T/#m4cf1056451d93fffbb9e427db5c4e459b342df07
On 2024-12-06 14:55, Aaron Lauterer wrote:
> The first patch in this series is not related, but adds a new column to
> the ceph pool panel to also display the application data of the pool.
>
> The rest of the series adds the necessary API endpoints and GUI to
> manage RBD namespaces in a HCI cluster. The Ceph Pool panel in the UI
> needed a bit more work to fit in a new grid for the namespaces. More in
> the actual patch (4/7).
>
> Additional future work can be made, for example to add a new scan option
> for the RBD storage backend that scans for namespaces. But that only has
> a tangential relationship to this series.
>
> manager: Aaron Lauterer (6):
> ui: ceph pool: add columns for application
> api: ceph: add rbd namespace management endpoints
> pveceph: add pool namespace subcommands
> ui: ceph pool: add rbd namespace panel
> ui: utils: add ceph rbd namespace task names
> ui: storage rbd: remove hint for manual rbd namespace creation
>
> PVE/API2/Ceph/Pool.pm | 182 ++++++++++++++++++++++++-
> PVE/CLI/pveceph.pm | 9 ++
> www/manager6/Utils.js | 2 +
> www/manager6/ceph/Pool.js | 230 +++++++++++++++++++++++++++++++-
> www/manager6/node/Config.js | 3 +-
> www/manager6/storage/RBDEdit.js | 21 ---
> 6 files changed, 422 insertions(+), 25 deletions(-)
>
> docs: Aaron Lauterer (1):
> pveceph: add section for rbd namespaces
>
> pveceph.adoc | 41 +++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 41 insertions(+)
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-12-23 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 13:55 Aaron Lauterer
2024-12-06 13:55 ` [pve-devel] [PATCH manager 1/7] ui: ceph pool: add columns for application Aaron Lauterer
2024-12-10 18:56 ` [pve-devel] applied: " Thomas Lamprecht
2024-12-06 13:55 ` [pve-devel] [PATCH manager 2/7] api: ceph: add rbd namespace management endpoints Aaron Lauterer
2024-12-10 18:52 ` Thomas Lamprecht
2024-12-23 12:09 ` Aaron Lauterer
2024-12-06 13:55 ` [pve-devel] [PATCH manager 3/7] pveceph: add pool namespace subcommands Aaron Lauterer
2024-12-06 13:55 ` [pve-devel] [PATCH manager 4/7] ui: ceph pool: add rbd namespace panel Aaron Lauterer
2024-12-06 13:55 ` [pve-devel] [PATCH manager 5/7] ui: utils: add ceph rbd namespace task names Aaron Lauterer
2024-12-06 13:55 ` [pve-devel] [PATCH manager 6/7] ui: storage rbd: remove hint for manual rbd namespace creation Aaron Lauterer
2024-12-06 13:55 ` [pve-devel] [PATCH docs 7/7] pveceph: add section for rbd namespaces Aaron Lauterer
2024-12-23 16:02 ` Aaron Lauterer [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=40cef2bf-bf9d-49b2-afd5-d13980f73cce@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox