On Sun, Jun 6, 2010 at 3:53 AM, Douglas Garstang <doug.garst...@gmail.com>wrote:
> > I was just doing a little research on the best way to switch over to > external nodes. It seems like you can't use a combination of the two > systems. Apparently if the external node tool can't find an external > node (because it hasn't been cut over yet), then that's a failure. > This makes moving from 'internal' nodes to external nodes BLOODY > difficult. This is currently killing me too. I also heavily used definitions in nodes for things that didn't really seem to belong in modules (one offs, mount points for admins to rummage around on the command line, the odd tweak here and there) and the inability to slowly migrate into an external node tool is infuriating because of how hard things are to test. I suppose my best bet is to back everything up, switch over and try it but that's an awkward situation. I plan to shut puppetd down on all nodes and then retest each of them by hand to ensure that things work as expected (because I've had to revamp various modules to account for how things are done with no definitions on the nodes and to change my networking too.) It's definitely an ugly solution and I can honestly see this being unfeasible for someone with a larger network than me. If I had double the hosts I simply wouldn't move to an external node classifer, no matter the benefits. -- 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.
