On Fri, Aug 29, 2014 at 7:24 AM, thehailo <theha...@gmail.com> wrote: > > I'm taking over a Puppet setup which was built on 2.7 and broken during a > huge migration a few months back (before my time, so I don't have much info > to go off). I figure since I'm basicaly starting from scratch (literally > the only thing anyone can tell me the old setup did was manage sudoers), > I'd start with a newer version, 3.6. I want to play it safe just in case an > ensure putting this new box up doesn't break anything checking into it. I'm > waiting on the old manifest files to see exactly what the old setup was > doing, so my big question is what's a safe way to deploy and test this > setup? I've been given a fresh VM but it uses the same IP/DNS as the old > box. I could just block traffic at the firewall but production systems are > checking in, so I just want to cover my bases. If a system from the old 2.7 > checks in and I have no manifests in the new setup, will it have any effect > or just keep the old setup until I push something newer? >
Really not much of a concern for multiple reasons. If you don't have the old CA certs, the agents will not connect to the new master. If the manifest is blank, you will overwrite the old catalog on the agents, but it won't be changing anything on the agent. If you are interested what the old system was managing, see if the cached catalog still exists on the agent. The catalog will contain all the resources the old puppet master was managing. Nan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CACqVBqBMKq2P7hTM%3DXpOFAfpgScmEJJ89Wn-%2BbxRE5Gdc%2BAbuQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
