On 27.05.2014 11:06, Felipe Salum wrote:
I work around this by using a cloudinit script during the autoscale instance launch that gets the instance-id of the instance, rename the hostname and update /etc/hosts before running puppet.
Cloud-init helps but there are limitations. I use cloud-init to deploy a script that generates the extra attributes file prior to puppet being deployed to include the instance id in the CSR and this works if your master can then otherwise determine how to configure the host. If the master is deterministic on the client cert name (read: hostname) then you can override that with cloud-init but it fails to be useful when using the full power of the cloud architecture and use auto scaling groups.
-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/85960579c1c0eab21f9068aa33299130%40undergrid.net. For more options, visit https://groups.google.com/d/optout.
