On Fri, Nov 14, 2014 at 4:02 PM, Erik Dalén <[email protected]> wrote:
> > > On Fri Nov 14 2014 at 7:16:07 PM Felix Frank < > [email protected]> wrote: > >> On 11/14/2014 07:09 PM, Henrik Lindberg wrote: >> > >> > Please note that some changes in puppet 4 mean that puppet 3 agents >> > won’t be able to talk to puppet 4 masters (or vice-versa). This probably >> > means you don’t want to be updating puppet itself with “ensure => >> latest” :) >> > >> Or should they try making all their agents update themselves until each >> last one won't talk to the master again, which can then be "safely" >> updated. > > > I would probably install a Puppet 4 master in parallell with my 3.x master > and test Puppet 4.x agents against that. And then when ready to migrate I'd > upgrade the agents and point them to use that master. And then decommission > the old master when there's no 3.x agents left. > > That's the pattern that I was hoping would work for people. I was even thinking about hacking up a module that would do the agent upgrade and switch the server host config over as part of one agent run, just to see how that'd work. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev/CAMx1QfKUztpkoa-_99j%3DYJ9QV8p4S_RaD08bUZ2SaZ02Z0VsBQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
