[Pkg-puppet-devel] [release-notes] Any known issues with Puppet 2.7 -> 3.7 upgrade?

[Stig Sandbeck Mathisen]

Russ Allbery <rra at debian.org> writes:

> micah <micah at debian.org> writes:
>
>> Hmm, this means that we are potentially making a difficult situation
>> for people. If a 2.7 master doesn't work with 3.7 and Jessie has
>> puppet 3.7.2, and a master must be upgraded before the clients, then
>> that means that the puppetmaster needs to be upgraded before any
>> clients, and you cannot do that upgrade until you "fix" all your
>> puppet code.
>
> Sadly, I believe that's correct. All the teams I know who are
> migrating to Puppet 3.x are bringing up a completely separate parallel
> 3.x infrastructure and fixing all the manifests, and then cutting over
> clients to the new Puppet master one by one.

That is my experience as well. We leave the 2.7 masters as they are, and
add new 3.x masters for new projects, and do a gradual migration of old
projects.

To ease migration of existing nodes between masters, you _can_ share the
puppet Certificate Authority between the old and the new masters.

-- 
Stig Sandbeck Mathisen