<p dir="ltr">In EC2, there is a dependency on the host ip as well. If the ip is modified, then the internal hostname is also different. <br>
If the hostname is not updated in the os there will be a difference in the instance hostname presented by the ec2 host management and the instance hostname on any stop/start, much like the EBS snapshot scenario described previously. </p>
<div class="gmail_quote">On Sep 11, 2013 5:44 AM, "Matthew Miller" <<a href="mailto:mattdm@fedoraproject.org">mattdm@fedoraproject.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, Sep 10, 2013 at 11:47:52PM -0400, Sam Kottler wrote:<br>
> Hi! Sorry about two emails in a row :-)<br>
<br>
More activity = good. :)<br>
<br>
<br>
> I think the update_hostname module causes some confusion on EBS-backed<br>
> instances. Users expect the hostname of their instance to remain<br>
> consistent across reboots and the update_hostname module causes it to be<br>
> reset on boot.<br>
> What do you all think about removing it from the cloud-init configuration?<br>
<br>
I don't have a strong opinion here, but in general anything which makes our<br>
cloud-init usage less heavyweight is good with me.<br>
<br>
--<br>
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <<a href="mailto:mattdm@fedoraproject.org">mattdm@fedoraproject.org</a>><br>
_______________________________________________<br>
cloud mailing list<br>
<a href="mailto:cloud@lists.fedoraproject.org">cloud@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/cloud" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/cloud</a><br>
Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" target="_blank">http://fedoraproject.org/code-of-conduct</a><br>
</blockquote></div>