----- Original Message -----
From: "Robert Collins (HPCS)" <rbtcollins(a)hp.com>
To: "Fedora Cloud SIG" <cloud(a)lists.fedoraproject.org>
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>
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