From: Oguz Bektas <o.bektas@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v3 container 1/2] setup: clear /etc/machine-id for newly created containers
Date: Thu, 10 Jun 2021 14:04:33 +0200 [thread overview]
Message-ID: <20210610120433.GA13807@gaia.proxmox.com> (raw)
In-Reply-To: <1623325310.d7m8o7zpwa.astroid@nora.none>
hi,
> +sub clear_machine_id {
> > + my ($self, $conf, $clone) = @_;
> > +
> > + my $code = sub {
> > + $self->{plugin}->clear_machine_id($self->{conf}, $clone);
> > + };
> > + $self->protected_call($code);
> > +
> > +}
>
> maybe it would make more sense to call this "post_clone_hook", so it is
> re-usable for other, similar changes (like optionally regenerating SSH
> keys, or ...) in the future without polluting the entry-point namespace
> too much?
yes i was also thinking why we don't have a post_clone_hook :D
i'll change that accordingly :)
>
> > +
> > sub post_create_hook {
> > my ($self, $root_password, $ssh_keys) = @_;
> >
> > diff --git a/src/PVE/LXC/Setup/Base.pm b/src/PVE/LXC/Setup/Base.pm
> > index d73335b..21074b7 100644
> > --- a/src/PVE/LXC/Setup/Base.pm
> > +++ b/src/PVE/LXC/Setup/Base.pm
> > @@ -476,6 +476,30 @@ sub set_timezone {
> > }
> > }
next prev parent reply other threads:[~2021-06-10 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 9:25 [pve-devel] [PATCH v3 container 0/2] fix #3443: unique machine-id for containers Oguz Bektas
2021-05-27 9:26 ` [pve-devel] [PATCH v3 container 1/2] setup: clear /etc/machine-id for newly created containers Oguz Bektas
2021-06-10 11:47 ` Fabian Grünbichler
2021-06-10 12:04 ` Oguz Bektas [this message]
2021-05-27 9:26 ` [pve-devel] [PATCH v3 container 2/2] clear machine-id also after container clone Oguz Bektas
2021-06-10 11:51 ` Fabian Grünbichler
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=20210610120433.GA13807@gaia.proxmox.com \
--to=o.bektas@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