On Mon, May 16, 2011 at 3:14 PM, Jonathan Gazeley
<jonathan.gaze...@bristol.ac.uk> wrote:
> The hostname of the puppetmaster is hard-coded, in our case. Can anyone
> think of a better way of identifying the puppetmaster, so our manifests will
> run anywhere, if we decide to make a different machine the puppetmaster?
I just refer to the puppetmaster as 'puppet' everywhere and drop an
entry in /etc/hosts for it. Then if I wanted to migrate off a server,
I would just hardcode away $servername and $serverip on the old
puppetmaster to point to the new one, and copy the certs over.
node default {
case $fqdn {
/puppetmaster/: {
host { puppet:
host_aliases => [ "localhost.localdomain", "puppet" ],
ip => "127.0.0.1",
name => "localhost",
}
}
default: {
host { puppet:
host_aliases => $servername,
ip => $serverip,
name => "puppet",
}
}
}
}
--
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.
