From: "Alwin Antreich" <alwin@antreich.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH storage] rbd: add support for erasure coded ec pools
Date: Wed, 26 Jan 2022 18:30:13 +0000 [thread overview]
Message-ID: <3dbb90bb8bfec2db7a08965c0301480f@antreich.com> (raw)
In-Reply-To: <20220126160734.2868618-1-a.lauterer@proxmox.com>
Hello Aaron,
nice to see EC pools are coming. ;)
January 26, 2022 5:07 PM, "Aaron Lauterer" <a.lauterer@proxmox.com> wrote:
> The first step is to allocate rbd images correctly.
>
> The metadata objects still need to be stored in a replicated pool, but
> by providing the --data-pool parameter on image creation, we can place
> the data objects on the erasure coded (EC) pool.
AFAICR, there is an undocumented location for a ceph.conf,
`/etc/pve/priv/ceph/<storage-name>.conf`.
The config should have the following content.
```
[client.admin_ec]
rbd default data pool = ceph_pool_ec
````
Then rbd will use the data pool. This should probably work for all storage operations.
Newer ceph versions should also work with the config db option.
```
ceph config set client.xxx rbd_default_data_pool ceph_pool_ec
```
Cheers,
Alwin
next prev parent reply other threads:[~2022-01-26 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 16:07 Aaron Lauterer
2022-01-26 18:30 ` Alwin Antreich [this message]
2022-01-27 11:27 ` Aaron Lauterer
2022-01-27 15:41 ` Alwin Antreich
2022-01-27 16:28 ` Aaron Lauterer
2022-01-28 5:50 ` Thomas Lamprecht
2022-01-28 9:22 ` Alwin Antreich
2022-01-28 9:50 ` Aaron Lauterer
2022-01-28 10:54 ` Alwin Antreich
2022-01-28 11:21 ` Aaron Lauterer
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=3dbb90bb8bfec2db7a08965c0301480f@antreich.com \
--to=alwin@antreich.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