From: Christian Ebner <c.ebner@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [RFC v2 pve-container pve-manager 0/3] add partial restore
Date: Mon, 23 Oct 2023 15:03:11 +0200 (CEST) [thread overview]
Message-ID: <260764959.1312.1698066191830@webmail.proxmox.com> (raw)
In-Reply-To: <47924ea8-097e-4dbe-979d-021566e564f5@proxmox.com>
Oh, okay! I was not aware of these patches, thanks for letting me know.
Yes, being consistent with the UI/API for both VM and LXC restores is desired. I was planning on doing the VM part next, but since there already is a patch series for this I will definitely work on a common denominator for these.
Thanks also for the first comments, will include changes regarding this into an updated version. I will also take you up on the offer to pick-up a rebased version of these patches.
Cheers,
Chris
> On 23.10.2023 14:47 CEST Fiona Ebner <f.ebner@proxmox.com> wrote:
>
>
> Am 23.10.23 um 13:18 schrieb Christian Ebner:
> > This patch series adds functionality to partially restore containers
> > from backup, by allowing the user to selectively include/exclude
> > mountpoints for restore. Mountpoints not included in the backup will not
> > be deleted and recreated but rather attached to the container as unused
> > disk after the restore. The same is true for mountpoints selected by the
> > user to be excluded during restore.
> >
>
> FYI, there is an old series [0] adding a similar feature for VMs. It
> would be nice if we could have the API/UI be not too different between
> them. Of course, it's not set in stone how it's done there (since it
> didn't get applied ;)), but it would be great if we could come up with a
> solution that works for both cases. If you really want, you could even
> pick up those patches in your next version of the series (just tell me
> if you need a rebased version).
>
> Didn't have time to take a close look yet, just noting that
> 'exclude-mps' is not specific enough as a parameter name for the
> 'create' API call. The name really should include the word 'restore' or
> similar, and you can add a requires => 'restore' to the schema
> definition of the parameter.
>
> [0]: https://lists.proxmox.com/pipermail/pve-devel/2022-April/052720.html
prev parent reply other threads:[~2023-10-23 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 11:18 Christian Ebner
2023-10-23 11:18 ` [pve-devel] [RFC v2 pve-container pve-manager 1/3] backup: do not delete not backed-up mps on restore Christian Ebner
2023-10-23 11:18 ` [pve-devel] [RFC v2 pve-container pve-manager 2/3] api: allow to exclude mountpoins from restore Christian Ebner
2023-10-23 11:18 ` [pve-devel] [RFC v2 pve-container pve-manager 3/3] ui: lxc restore: add selective mountpoint restore Christian Ebner
2023-10-23 12:47 ` [pve-devel] [RFC v2 pve-container pve-manager 0/3] add partial restore Fiona Ebner
2023-10-23 13:03 ` Christian Ebner [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=260764959.1312.1698066191830@webmail.proxmox.com \
--to=c.ebner@proxmox.com \
--cc=f.ebner@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal