public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
	"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [pve-devel] [RFC storage 0/3] rbd: use image-/snap-spec instead of --pool/..
Date: Wed, 30 Apr 2025 17:51:45 +0200	[thread overview]
Message-ID: <b5aa6f38-9dcb-40ed-8ec5-83c52941f7e3@proxmox.com> (raw)
In-Reply-To: <20250423135904.716443-1-f.gruenbichler@proxmox.com>

Tested this patch series by:

* create a new VM on ceph RBD
* took & removed snapshot (with memory)
* cloned VM
* converted to template (rename from vm-… to base-… worked)
* created linked clone
* destroy template -> fail due to linked clone
* destroy linked clone
* destroy template

namespace tests:
* create rbd namespace
* move-disk of VM to namespace (main disk, EFI, tpm)
* remote migrate from rbd namespace to other node with local-lvm
* remote migrate back from local-lvm to rbd namespace storage


The code changes look good and I didn't notice anything there.

So with this, consider this series

Reviewed-By: Aaron Lauterer <a.lauterer@proxmox.com>
Tested-By: Aaron Lauterer <a.lauterer@proxmox.com>

On  2025-04-23  15:59, Fabian Grünbichler wrote:
> the 'rbd' CLI tool has two ways of specifying which images/snapshots to
> operate on:
> - the deprecated --(dest-)pool, --namespace, --image and --snap parameters
> - the new style 'spec'-based variant, passing [pool/[namespace/]]image[@snapshot]
> 
> we are currently using a mix of both (passing pool, namespace and snap
> as needed via parameters, and the image-name as argument). this patch
> series switches everything to use image or snap specs, except for `ls`,
> which can't be switched over, because it doesn't operate on images at
> all.
> 
> `unmap` doesn't support `--namespace` (but doesn't need it, since it
> takes the kernel dev as argument). `import` doesn't either, but does
> require it when a namespace is used as import target (this bug prompted
> the whole excursion resulting in this patch series).
> 
> I smoke-tested the changes, but it's possible I missed some operation or
> corner case when converting, so additional testing is highly
> appreciated.
> 
> Fabian Grünbichler (3):
>    rbd: extend get_rbd_(dev_)path helpers with $snap parameter
>    fix #6338: rbd: use image-/snap-spec consistently
>    rbd: add protect/unprotect helpers
> 
>   src/PVE/Storage/RBDPlugin.pm | 167 ++++++++++++++++++-----------------
>   1 file changed, 86 insertions(+), 81 deletions(-)
> 



_______________________________________________
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-30 15:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23 13:59 Fabian Grünbichler
2025-04-23 13:59 ` [pve-devel] [PATCH storage 1/3] rbd: extend get_rbd_(dev_)path helpers with $snap parameter Fabian Grünbichler
2025-04-23 13:59 ` [pve-devel] [PATCH storage 2/3] fix #6338: rbd: use image-/snap-spec consistently Fabian Grünbichler
2025-05-05 14:24   ` Fiona Ebner
2025-04-23 13:59 ` [pve-devel] [PATCH storage 3/3] rbd: add protect/unprotect helpers Fabian Grünbichler
2025-05-05 14:24   ` Fiona Ebner
2025-05-06 11:07     ` Fabian Grünbichler
2025-05-06 11:40       ` Fiona Ebner
2025-04-30 15:51 ` 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=b5aa6f38-9dcb-40ed-8ec5-83c52941f7e3@proxmox.com \
    --to=a.lauterer@proxmox.com \
    --cc=f.gruenbichler@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal