Code review comment for ~chad.smith/cloud-init:set-hostname-before-network
Revision history for this message
| Ryan Harper (raharper) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
I've a bit of a quibble with the description. Mostly because cloud-init has _no_ control over how DNS or DHCP servers react to dhcp client requests coming from an instance.
What we (cloud-init) can do is set instance specified hostnames as _soon_ as we know it, which may be of help to some situations where Dynamic DNS via dhcp client hostname value.
This is an environment specific issue and having cloud-init set hostname as soon as possible does not ensure that there won't be issues with DNS, DHCP outside of cloud-init control.
Some inline comments too.