From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexander Zeidler <a.zeidler@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs v2 6/6] pveceph: add section for rbd namespaces
Date: Fri, 10 Jan 2025 15:26:24 +0100 [thread overview]
Message-ID: <f030fd6b-59f1-454e-8b8a-ab1dda56d175@proxmox.com> (raw)
In-Reply-To: <D6RMT5M4VJBF.36IBT7SXPRGDJ@proxmox.com>
thanks. I can send a follow-up if the rest of the series does not
require a v3
On 2025-01-02 14:46, Alexander Zeidler wrote:
> On Mon Dec 23, 2024 at 5:00 PM CET, Aaron Lauterer wrote:
>> and a few basic examples on how to manage them.
>>
>> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
>> ---
>> changes since v1: none
>>
>> pveceph.adoc | 41 +++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 41 insertions(+)
>>
>> diff --git a/pveceph.adoc b/pveceph.adoc
>> index da39e7f..a90a6e1 100644
>> --- a/pveceph.adoc
>> +++ b/pveceph.adoc
>> @@ -760,6 +760,47 @@ You can find a more in-depth introduction to the PG autoscaler on Ceph's Blog -
>> https://ceph.io/rados/new-in-nautilus-pg-merging-and-autotuning/[New in
>> Nautilus: PG merging and autotuning].
>>
>> +[[pve_ceph_rbd_namespaces]]
>> +RBD Namespaces
>> +~~~~~~~~~~~~~~
>> +
>> +Namespaces in the rados block device (RBD) layer can be used to have multiple
>> +Proxmox VE clusters using the same pool, but still be logically separated.
> {pve}
>
>> +Namespaces can be managed in the web UI in the 'Node -> Ceph -> Pools' panel.
>> +
>> +Alternatively, the `pveceph` or Ceph's `rbd` footnote:[https://docs.ceph.com/en/latest/man/8/rbd/]
>> +utility can be used too. To list all RBD namespaces of the pool `vmstore`, run the
>> +following command:
>> +[source, bash]
>> +----
>> +pveceph pool namespace ls vmstore
>> +----
>> +The result will be for example:
>> +[source, bash]
>> +----
>> +┌───────────┐
>> +│ Namespace │
>> +╞═══════════╡
>> +│ bar │
>> +├───────────┤
>> +│ foo │
>> +└───────────┘
>> +----
>> +
>> +To create a new RBD namespace `baz` in the pool `vmstore`, run:
>> +[source, bash]
>> +----
>> +pveceph pool namespace create vmstore baz --add-storage 1
>> +----
>> +The `--add-storage` parameter is optional an when set, will create a new
> s/an/and/
>
>> +storage configuration with the new namespace.
>> +
>> +To delete the `baz` RBD namespace in pool `vmstore`:
> Maybe:
> To delete the empty `baz` RBD namespace in pool `vmstore`, run:
>
>> +[source, bash]
>> +----
>> +pveceph pool namespace destroy vmstore baz
>> +----
>> +
>>
>> [[pve_ceph_device_classes]]
>> Ceph CRUSH & device classes
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-01-10 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 16:00 [pve-devel] [PATCH manager, docs v2 0/6] Ceph: add RBD Namespace management Aaron Lauterer
2024-12-23 16:00 ` [pve-devel] [PATCH manager v2 1/6] api: ceph: add rbd namespace management endpoints Aaron Lauterer
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 [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=f030fd6b-59f1-454e-8b8a-ab1dda56d175@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=a.zeidler@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