Bug#907672: Rebasing cloud-init to the latest one
On 09/07/2018 08:34 AM, Yanhui He wrote:
> Hi Thomas,
>
> Thanks for your reply!
>
> On Tue, 4 Sep 2018 09:28:55 +0200 Thomas Goirand <zigo@debian.org
> <mailto:zigo@debian.org>> wrote:
>> On 09/04/2018 05:29 AM, Yanhui He wrote:
>> > If you have any concern for v18.3 stability we could do some regression
>> > test together if needed.
>>
>> Not only us, but also the release team. If we sufficiently show it has
>> been tested, it may help.
>>
>> Cheers,
>>
>> Thomas Goirand (zigo)
>>
>> P.S: Is it really necessary to have 15 people CC-ed on each message?
>>
>>
> Based on Debian9.5.0-64 and cloud-init 18.3-35, the following can be
> customized successfully.
> * static/DHCP IP address, Gateway, Netmask
> * Hostname
> * Timezone
>
> The following is not customized successfully, but most are known
> issue/limit for cloud-init
> * DNS. It was set in 50-cloud-init.cfg but not updated to resolv.conf
> file (Known cloud-init issue)
> * Domain name was not updated to /etc/hosts (Known cloud-init issue)
While these may be cloud-init problems in Stretch, it's kind of easy to
do this in a user metadata script.
> * Hardware clock setting is not supported by cloud-init, default is UTC(
> Known cloud-init issue and it is not suggested to set hardware clock to
> local time on *NIX system)
Here, I don't see any issue at all. You'll get hardware clock as UTC,
and configure your VM with local timezone if you like. That's the normal
behavior, and I don't see any reason why you would like a different setup.
> From the results above, the 18.3 version of cloud-init can achieve most
> our customization goals, but with the version 0.7.9, our customization
> can not work at all.
Why don't you do all of this in a user-data script?
Note that all of what I'm telling/asking here is probably what the
release team will ask if we request for a new version to get into
Stretch. If we don't have the answers, then probably we shouldn't even
attempt to ask the release team.
Cheers,
Thomas Goirand (zigo)
Reply to: