From: Oguz Bektas <o.bektas@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v4 container 0/2] post_clone hook for containers
Date: Wed, 16 Jun 2021 16:04:29 +0200 [thread overview]
Message-ID: <20210616140429.GA14060@gaia.proxmox.com> (raw)
In-Reply-To: <5d74bd92-63b0-5525-a7e1-7a561e92d54d@proxmox.com>
On Wed, Jun 16, 2021 at 03:48:42PM +0200, Thomas Lamprecht wrote:
> On 16.06.21 15:24, Oguz Bektas wrote:
> > fixes #3443 by implementing post_clone_hook for containers (which at the
> > moment only generates a unique /etc/machine-id for the cloned
> > container). this can be reused later for other things we want to do post
> > clone.
> >
>
> what are the changes since v3? I did not found any note here nor in the actual
> patches.
oops. sorry!
v3->v4:
* call generic post_clone_hook in setup code instead of directly calling
clear_machine_id in clone_vm API
* improve config locking in clone_vm API (don't write to config file
without checking/obtaining lock on it)
* clone firewall config _inside_ worker instead of _before_ worker
* fixed minor typo in error message for bind mounts
>
> >
> >
> > Oguz Bektas (2):
> > setup: add post_clone_hook for containers
> > run post_clone_hook in clone_vm
> >
> > src/PVE/API2/LXC.pm | 37 ++++++++++++++++++++++++++++++-------
> > src/PVE/LXC/Setup.pm | 12 ++++++++++++
> > src/PVE/LXC/Setup/Base.pm | 31 +++++++++++++++++++++++++++++++
> > 3 files changed, 73 insertions(+), 7 deletions(-)
> >
>
prev parent reply other threads:[~2021-06-16 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 13:24 Oguz Bektas
2021-06-16 13:24 ` [pve-devel] [PATCH v4 container 1/2] setup: add post_clone_hook " Oguz Bektas
2021-06-16 13:24 ` [pve-devel] [PATCH v4 container 2/2] run post_clone_hook in clone_vm Oguz Bektas
2021-06-16 13:48 ` [pve-devel] [PATCH v4 container 0/2] post_clone hook for containers Thomas Lamprecht
2021-06-16 14:04 ` Oguz Bektas [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=20210616140429.GA14060@gaia.proxmox.com \
--to=o.bektas@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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