Quoting Scott Moser (smo...@ubuntu.com):
> prior to my enabling of the clone hook, the setting of the hostname
> was being done by writing to /etc/hostname. Instead of relying on that
> we're now writing 'local-hostname' into the metadata for the instance.
>
> cloud-init then reads this and sets
prior to my enabling of the clone hook, the setting of the hostname
was being done by writing to /etc/hostname. Instead of relying on that
we're now writing 'local-hostname' into the metadata for the instance.
cloud-init then reads this and sets the hostname properly.
We are also writing /etc/ho
On Thu, 22 Aug 2013, Serge Hallyn wrote:
> Quoting Scott Moser (smo...@ubuntu.com):
> > prior to my enabling of the clone hook, the setting of the hostname
> > was being done by writing to /etc/hostname. Instead of relying on that
> > we're now writing 'local-hostname' into the metadata for the i
Quoting Scott Moser (smo...@ubuntu.com):
> prior to my enabling of the clone hook, the setting of the hostname
> was being done by writing to /etc/hostname. Instead of relying on that
> we're now writing 'local-hostname' into the metadata for the instance.
>
> cloud-init then reads this and sets
prior to my enabling of the clone hook, the setting of the hostname
was being done by writing to /etc/hostname. Instead of relying on that
we're now writing 'local-hostname' into the metadata for the instance.
cloud-init then reads this and sets the hostname properly.
The one caveat is that sett
