cloud-init-dev team mailing list archive

Thread
Date

Re: [Merge] ~chad.smith/cloud-init:set-hostname-before-network into cloud-init:master

To: mp+339720@xxxxxxxxxxxxxxxxxx
From: Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>
Date: Tue, 27 Feb 2018 14:26:40 -0000
In-reply-to: <151967883490.4411.3051777816070383952.launchpad@ackee.canonical.com>
Reply-to: mp+339720@xxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

My only comment at this point is wheter or not we should bother with calling the config module and writing the marker file and such at that point.

the other option is to just set it.

The other thoughts (i guess i did have more than one)
a.) we have had issues with setting hostname not being possible early in boot due to that being a systemd service (hostnamectl) .  
b.) we want to somehow make sure that we only set this hostname on first instance boot.  We don't want to overwrite what a user configured manually. 

I think that your use of config module probably handles that, but just want to write those thoughts down.

-- 
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/339720
Your team cloud-init commiters is requested to review the proposed merge of ~chad.smith/cloud-init:set-hostname-before-network into cloud-init:master.

References

[Merge] ~chad.smith/cloud-init:set-hostname-before-network into cloud-init:master
From: Chad Smith, 2018-02-26