On 21 July 2011 16:41, John Fieber <j...@ursamaris.org> wrote: > I use instance userdata to configure puppet (via ubuntu cloudinit) and set > an explicit certname, in the form: > > <instance_id>-<puppetclass>-<environment> > > The server uses a a node classifier that fabricates the node spec from > that. >
Similarly I've used a port of cloud-init baked into a minimal CentOS AMI. Vanity hostname (under our own zone), location of the Puppet master, environment and some misc stuff are defined as YAML in the instance's user-data. The stock cloud-init modules set the machine's hostname and populate "puppet.conf" from user-data on boot, amongst other things. A custom route53 module registers a CNAME for the instance's vanity hostname, pointing to Amazon's split horizon record. If the instance reboots then it updates DNS with it's new dynamic address. Those vanity hostnames then serve as static records which can be used for Puppet certs and nodes in manifests. Not ideal, but seems to work pretty well. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
