On Tue, Aug 30, 2011 at 9:28 AM, Dan White <y...@comcast.net> wrote: > The environment I work in has dev, QA, and production divisions. > New machines are built/loaded in dev and then moved, if necessary to QA or > production after they have been configured and verified. In moving, the > machine in question will change its IP address and hostname. > > I have set up a Cobbler server to shortcut this, and I am now tasked with > adding Puppet to the mixture. > > Can anyone suggest a maintainable way for Puppet to handle machines that > get moved and renamed as described ? > > My first thought is to remove all the files generated by making the machine > a puppet client and then just re-add it as a new client in the new location > with the new name, but that feels like a brute-force solution. >
Don't use hostnames for your certnames? I've used UUIDs for this sort of deployment in the past. > > “Sometimes I think the surest sign that intelligent life exists elsewhere > in the universe is that none of it has tried to contact us.” > Bill Waterson (Calvin & Hobbes) > > -- > 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. > > -- Nigel Kersten Product Manager, Puppet Labs *Join us for **PuppetConf * <http://www.bit.ly/puppetconfsig> Sept 22/23 Portland, Oregon, USA. * * -- 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.
