From: aderumier@odiso.com
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Wolfgang Bumiller <w.bumiller@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] cloudinit: question about cloudinit pending values && hostname/mac address changes
Date: Tue, 23 Feb 2021 16:29:08 +0100 [thread overview]
Message-ID: <fd209e94cfe995f61bd9e0eea8a1c7950f319e61.camel@odiso.com> (raw)
In-Reply-To: <75c9dea4-4e42-3882-2e83-348ea1c15fe4@proxmox.com>
>>normally the CI service reads this only once at startup and then
>>should
>>wait on events?
>>Anything basing on a CD ROM device should be able to handle ejects or
>>inject at any time...
>>@Alexandre, did you test how good the Cloudinit clients handle this?
I'm able to change the cdrom with new file, with the /dev/cdrom
mounted, without any problem.
About cloud-init, currently, it don't do nothing on config change,
until you restart the service. (so manually, or through an custom udev
rule detecting cdrom change).
So I think it's pretty safe, until maybe you restart cloudinit service
manually and at same time change the cdrom.
with opennebula opencontext daemon, the udev rule correctly manage
cdrom change, and apply the change.
Maybe could we add a "hotplug: cloudinit" option to enable auto
regeneration ?
I still don't known how to display currently applying state of nic mac
address change. Currently we have only "pending state" (aka pending vm
hardware configuration), but with cloud-init, we have some kind of
"pending cloudnit" state. (aka pending vm guest ok configuration)
It's not really a problem currently, but It's difficult to known if
cloud-init drive need to be regenerated or not.
Le mardi 23 février 2021 à 10:29 +0100, Thomas Lamprecht a écrit :
>
> normally the CI service reads this only once at startup and then should
> wait on events?
>
> Anything basing on a CD ROM device should be able to handle ejects or
> inject at any time...
>
> @Alexandre, did you test how good the Cloudinit clients handle this?
next prev parent reply other threads:[~2021-02-23 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 17:47 aderumier
2021-02-23 8:27 ` Thomas Lamprecht
2021-02-23 9:06 ` Wolfgang Bumiller
2021-02-23 9:29 ` Thomas Lamprecht
2021-02-23 15:29 ` aderumier [this message]
2021-03-06 7:31 ` aderumier
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=fd209e94cfe995f61bd9e0eea8a1c7950f319e61.camel@odiso.com \
--to=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
--cc=w.bumiller@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