From: MAbeeTT via pve-devel <pve-devel@lists.proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: MAbeeTT <mabeett@gmail.com>
Subject: Re: [pve-devel] cloudinit: RFC proposal for unwanted and unexpected regeneration of instance-id
Date: Tue, 16 Jul 2024 17:19:35 +0200 [thread overview]
Message-ID: <mailman.498.1721143229.331.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <30768a19-ddc4-49dc-b22d-1b47e5cceea8@proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 7194 bytes --]
From: MAbeeTT <mabeett@gmail.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] cloudinit: RFC proposal for unwanted and unexpected regeneration of instance-id
Date: Tue, 16 Jul 2024 17:19:35 +0200
Message-ID: <CAKmboB+5hNmqbECax5cAeFcoKJqoBPJ6HATXL0OB1EowZ6H2sA@mail.gmail.com>
On Tue, Jul 16, 2024 at 4:49 PM Mira Limbeck <m.limbeck@proxmox.com> wrote:
>
> Hi Matias,
>
> Thank you for providing this detailed description of the issue!
Hello Mira
thanks for your quick response!
From my side I offer all my available energy in order to help.
> We have an open issue in our bug tracker [0]. If it's alright with you
> I'd add your text as-is to the bug tracker as a comment for additional
> information/reasoning on why that change would be needed.
Sure, feel free to edit in order to clarify.
Just one clarification:
Current cloud-init documentation from my first message determines[0] clearly
> > Alternatively, the filesystem has been attached to a new instance, and this is the instance’s first boot.
> > The most obvious case where this happens is when an instance is launched from an image captured from a launched instance.
> > By default, cloud-init attempts to determine which case it is running in by checking the instance ID in the cache against the instance ID it determines at runtime.
> > If they do not match, then this is an instance’s first boot;
So It is not a matter of a particular Distro/OS version/release. It is
a «a feature» from upstream cloud-init implementation.
My corner case is just a bit different, let say "Do not update
instance-id without user new VM config [subset cinit-related]"
Anyway your work could be an answer for my scenario.
Let me know if this is clear enough.
>
> Feel free to add yourself to the CC list if you want to be notified on
> updates.
Done, thanks
>
> > I am far away from being a Perl developer, but I can put my best
> > effort during my spare time.
> > Anyway I would like to know what you think since what I am proposing
> > changes the current behaviour of PVE cloudinit, maybe these changes
> > could be part of PVE 9?
>
> I already started working on an implementation for a fixed instance-id.
> I can't give an ETA when the first draft will be sent to the pve-devel
> list though.
Great, ping me if you need feedback.
kind regards,
mts
[0] https://cloudinit.readthedocs.io/en/latest/explanation/boot.html#first-boot-determination
--
.::MAbeeTT::.
mabeett [at] gmail [ dot] com
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-07-16 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 14:41 MAbeeTT via pve-devel
2024-07-16 14:49 ` Mira Limbeck
2024-07-16 15:19 ` MAbeeTT via pve-devel [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=mailman.498.1721143229.331.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=mabeett@gmail.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