Our DNS naming scheme works like this:
servername.<data center>.host-name.net
I'd like to be able to create a single server image with puppet configured
that can work with multiple data centers. Right now, my image is tied to
a single data center, so /etc/resolv.conf looks like this:
nameserver 1.2.3.4
nameserver 1.2.3.5
search iad01.host-name.net
The issue there is if I decide to use this image in a different data
center, which would have its own puppet instance setup.
So just to standardize, what I've been thinking of doing instead is
creating a "fake" data center, where CNAMEs live for other data centers,
such as:
launch.host-name.net
So we'd have:
nameserver 1.2.3.4
nameserver 1.2.3.5
search launch.host-name.net
That way, when puppet searches for "puppet" as a shortname (which it does
by default), it will try to connect to puppet.launch.host-name.net, which
is a central host. After it receives it's appropriate /etc/resolv.conf,
which will include data center specific things in it, I'll have that
puppetmaster instance restart puppet, which will then point it to its
local puppet instance....
Would this work? Assuming the same certificate was on both puppetmaster
servers?
Or is this asking for trouble?
-Matt
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@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.
