Hi Chris, in addition to all the practical advice for moving through the upgrade cycles that you have gotten already, I would suggest taking a step back and analyzing your existing code-base to understand what the actual business function of the existing code is for the nodes. You can spend a ton of time doing things like adjusting syntax and eliminating deprecation warnings on a module, only to find out that the only host that is using that module was turned off a year ago and nobody noticed!
So it might help to just draw out with a whiteboard or sticky notes what the existing mapping of puppet code to groups of machines looks like, what you think it SHOULD look like, and talk it over with your management/team to make sure the new setup is going the right direction. It's possible that you can save yourself a ton of work, plus be able to build a really good plan of the most valuable places to spend time. --eric0 On Monday, May 9, 2016 at 4:12:43 AM UTC-7, christg76 wrote: > > Thanks to everyone for the comments! I think I first need to do some > preliminary testing in order to assess the quality of the code and to see > what the real challenges are, and to ultimately decide on a strategy, ie > upgrade vs transition/migration. > Ramin K: OS of the Master is Debian Wheezy. Have you actually done the > upgrade? > Andrew Grimberg: This approach in fact sounds as if its the best way, > considering also what Henrik says below about new > versions/modules/tooling/practices. But it sounds like a massive amount of > work, particularly since we do not have any unit tests or similar in place. > Did you have any unit tests in place with the old code, or if not are you > implementing them with the new code? > > Chris > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5bde60c1-2f44-45f3-b659-6d9bb3b0de93%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
