all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com,
	Friedrich Weber <f.weber@proxmox.com>,
	Alexander Zeidler <a.zeidler@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager, docs v2 0/6] Ceph: add RBD Namespace management
Date: Fri, 4 Apr 2025 16:54:29 +0200	[thread overview]
Message-ID: <2ea00414-7c26-4269-9f66-691d364f946b@proxmox.com> (raw)
In-Reply-To: <20241223160008.218710-1-a.lauterer@proxmox.com>

sent a v3 with your recommendations and feedback. thanks!

https://lore.proxmox.com/pve-devel/20250404145339.1067261-1-a.lauterer@proxmox.com/T/#u

On  2024-12-23  17:00, Aaron Lauterer wrote:
> 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 (3/6).
> 
> 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.
> 
> changes since v1:
> Only on patch 1/6, integrating the feedback received. More details in
> the patch itself.
> 
> manager: Aaron Lauterer (5):
>    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           | 205 ++++++++++++++++++++++++++++-
>   PVE/CLI/pveceph.pm              |   9 ++
>   www/manager6/Utils.js           |   2 +
>   www/manager6/ceph/Pool.js       | 222 +++++++++++++++++++++++++++++++-
>   www/manager6/node/Config.js     |   3 +-
>   www/manager6/storage/RBDEdit.js |  21 ---
>   6 files changed, 437 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


      parent reply	other threads:[~2025-04-04 14:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-23 16:00 Aaron Lauterer
2024-12-23 16:00 ` [pve-devel] [PATCH manager v2 1/6] api: ceph: add rbd namespace management endpoints Aaron Lauterer
2025-04-02 14:14   ` Friedrich Weber
2024-12-23 16:00 ` [pve-devel] [PATCH manager v2 2/6] pveceph: add pool namespace subcommands Aaron Lauterer
2024-12-23 16:00 ` [pve-devel] [PATCH manager v2 3/6] ui: ceph pool: add rbd namespace panel Aaron Lauterer
2024-12-23 16:00 ` [pve-devel] [PATCH manager v2 4/6] ui: utils: add ceph rbd namespace task names Aaron Lauterer
2024-12-23 16:00 ` [pve-devel] [PATCH manager v2 5/6] ui: storage rbd: remove hint for manual rbd namespace creation Aaron Lauterer
2024-12-23 16:00 ` [pve-devel] [PATCH docs v2 6/6] pveceph: add section for rbd namespaces Aaron Lauterer
2025-01-02 13:46   ` Alexander Zeidler
2025-01-10 14:26     ` Aaron Lauterer
2025-04-02 14:14 ` [pve-devel] [PATCH manager, docs v2 0/6] Ceph: add RBD Namespace management Friedrich Weber
2025-04-04 14:54 ` 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=2ea00414-7c26-4269-9f66-691d364f946b@proxmox.com \
    --to=a.lauterer@proxmox.com \
    --cc=a.zeidler@proxmox.com \
    --cc=f.weber@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