On Nov 1, 2010, at 10:51 AM, Robert Scheer wrote: > Hi, > > I have set up a puppetmaster test server where I can test new releases > of puppet before upgrading our puppetmaster production server. > It works, but there is one issue I'd like to solve: > > The puppet.conf for all nodes (except the puppetmasters) is managed by > puppet (in modules/puppet/files/puppet.conf) because it needs to contain > the fqdn of our puppetmaster server: puppetmaster.ourdomain.com. > But every time I export our puppet code repository from subversion to > the test server, I have to manually modify the server name in that file > to puppetmaster-test.ourdomain.com. If I don't, then a test-node connecting > to the test server, will receive a puppet.conf with the production server > name, and subsequent puppet runs will connect to that server instead of > my test server. > > As a solution I tried templating puppet.conf but cannot figure out what > variable to use to fill in the current puppet server name. > > I could solve that by making a custom fact, but besides the huge overhead > of "puppetd --configprint server" running every 30 minutes on every node, > it is just weird for a server to have to ask the client for its own name. > > So I'd really like to fix this in puppet code on the masters only. > Is there a way to access the local configuration parameter 'server' > within puppet? Or is there another, better solution I am missing?
This isn't a very good answer, but the variable "$servername" contains the name of the server the client think's it's connecting to. That may do what you want. -- 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.
