Removing the update_hostname cloud-init module from AMI's

[Sam Kottler]

Hi! Sorry about two emails in a row :-)

I think the update_hostname module causes some confusion on EBS-backed instances. Users
expect the hostname of their instance to remain consistent across reboots and the
update_hostname module causes it to be reset on boot.

What do you all think about removing it from the cloud-init configuration?

-Sam

[Collins, Robert (Converged Cloud)]

What happens if you snapshot the EBS volume and spawn a clone?

-Rob

Robert Collins <rbtcollins(a)hp.com&gt;
Distinguished Technologist
HP Converged Cloud

________________________________________
From: cloud-bounces(a)lists.fedoraproject.org [cloud-bounces(a)lists.fedoraproject.org] on
behalf of Sam Kottler [skottler(a)redhat.com]
Sent: Wednesday, 11 September 2013 15:47
To: Fedora Cloud SIG
Subject: Removing the update_hostname cloud-init module from AMI's

Hi! Sorry about two emails in a row :-)

I think the update_hostname module causes some confusion on EBS-backed instances. Users
expect the hostname of their instance to remain consistent across reboots and the
update_hostname module causes it to be reset on boot.

What do you all think about removing it from the cloud-init configuration?

-Sam
_______________________________________________
cloud mailing list
cloud(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Sam Kottler]

----- Original Message -----
>  From: "Robert Collins (HPCS)" <rbtcollins(a)hp.com&gt;
>  To: "Fedora Cloud SIG" <cloud(a)lists.fedoraproject.org&gt;
>  Sent: Wednesday, September 11, 2013 6:38:33 AM
>  Subject: RE: Removing the update_hostname cloud-init module from AMI's
>  
>  What happens if you snapshot the EBS volume and spawn a clone? 
Then you change the hostname on the new instance, which could be the expected behavior
anyhow.

>  
>  -Rob
>  
>  Robert Collins <rbtcollins(a)hp.com&gt;
>  Distinguished Technologist
>  HP Converged Cloud
>  
>  ________________________________________
>  From: cloud-bounces(a)lists.fedoraproject.org
>  [cloud-bounces(a)lists.fedoraproject.org] on behalf of Sam Kottler
>  [skottler(a)redhat.com]
>  Sent: Wednesday, 11 September 2013 15:47
>  To: Fedora Cloud SIG
>  Subject: Removing the update_hostname cloud-init module from AMI's
>  
>  Hi! Sorry about two emails in a row :-)
>  
>  I think the update_hostname module causes some confusion on EBS-backed
>  instances. Users expect the hostname of their instance to remain consistent
>  across reboots and the update_hostname module causes it to be reset on boot.
>  
>  What do you all think about removing it from the cloud-init configuration?
>  
>  -Sam
>  _______________________________________________
>  cloud mailing list
>  cloud(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/cloud
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>  _______________________________________________
>  cloud mailing list
>  cloud(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/cloud
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>

[Matthew Miller]

On Tue, Sep 10, 2013 at 11:47:52PM -0400, Sam Kottler wrote:
>  Hi! Sorry about two emails in a row :-) 
More activity = good. :)


>  I think the update_hostname module causes some confusion on
> EBS-backed
>  instances. Users expect the hostname of their instance to remain
>  consistent across reboots and the update_hostname module causes it to be
>  reset on boot.
>  What do you all think about removing it from the cloud-init configuration? 
I don't have a strong opinion here, but in general anything which makes our
cloud-init usage less heavyweight is good with me.

-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  <mattdm(a)fedoraproject.org&gt;

[David Duncan]

In EC2, there is a dependency on the host ip as well. If the ip is
modified, then the internal hostname is also different.
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.
On Sep 11, 2013 5:44 AM, "Matthew Miller" <mattdm(a)fedoraproject.org&gt;
wrote:

>  On Tue, Sep 10, 2013 at 11:47:52PM -0400, Sam Kottler wrote:
>  > Hi! Sorry about two emails in a row :-)
>
>  More activity = good. :)
>
>
>  > I think the update_hostname module causes some confusion on EBS-backed
>  > instances. Users expect the hostname of their instance to remain
>  > consistent across reboots and the update_hostname module causes it to be
>  > reset on boot.
>  > What do you all think about removing it from the cloud-init
>  configuration?
>
>  I don't have a strong opinion here, but in general anything which makes our
>  cloud-init usage less heavyweight is good with me.
>
>  --
>  Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  <
>  mattdm(a)fedoraproject.org&gt;
>  _______________________________________________
>  cloud mailing list
>  cloud(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/cloud
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>