From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v2 storage 0/3] ceph: add namespace support
Date: Wed, 7 Apr 2021 16:22:15 +0200 [thread overview]
Message-ID: <20210407142218.29156-1-a.lauterer@proxmox.com> (raw)
This series introduces namespace support for Ceph RBD on the PVE side.
The first patch reworks the RBD storage plugin to use one central sub to
create the RBD paths for <pool>/<image>. With this patch applied, adding
support for namespaces involves very little changes to the RBD plugin.
v1 -> v2:
* new patch (centralize rbd path concatenation) has been
introduced
* namespace checks now avoid matching the contents of the
$scfg->{namespace} but check if it is defined. This is done to avoid
evaluating a namespace called '0' for example, to evaluate to false.
* integration test has been reworked according to feedback
Aaron Lauterer (3):
rbd: centralize rbd path concatenation
rbd: fix #3286 add namespace support
rbd: add integration test for namespace handling
PVE/Storage/RBDPlugin.pm | 63 +++++--
test/rbd_namespace.pl | 370 +++++++++++++++++++++++++++++++++++++++
2 files changed, 415 insertions(+), 18 deletions(-)
create mode 100755 test/rbd_namespace.pl
--
2.20.1
next reply other threads:[~2021-04-07 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 14:22 Aaron Lauterer [this message]
2021-04-07 14:22 ` [pve-devel] [PATCH v2 storage 1/3] rbd: centralize rbd path concatenation Aaron Lauterer
2021-04-12 12:39 ` [pve-devel] applied: " Thomas Lamprecht
2021-04-07 14:22 ` [pve-devel] [PATCH v2 storage 2/3] rbd: fix #3286 add namespace support Aaron Lauterer
2021-04-12 12:41 ` [pve-devel] applied: " Thomas Lamprecht
2021-04-07 14:22 ` [pve-devel] [PATCH v2 storage 3/3] rbd: add integration test for namespace handling Aaron Lauterer
2021-04-12 12:48 ` [pve-devel] applied: " Thomas Lamprecht
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=20210407142218.29156-1-a.lauterer@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