I tested this in a 4-node Squid cluster, one thing I noticed:

- after selecting a pool in the GUI and creating a namespace, the
namespace panel is greyed out and I get a spinning wheel with the error
message

> rbd error: Ensure that the default pool has been created or specify an
alternate pool name. (500)

I only see the new namespace (and the error disappears) after navigating
to a different pool and back.

Same after destroying a namespace.

On 23/12/2024 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

Reply via email to