If you follow the mailing list it seems that there were a larger number of deliberate syntax changes from the move from 2.6 to 2.7 than there were from 0.25 to 2.6. IE: Syntax that changes behavior, not just breaks.
The rule of thumb has always been to support one major version backwards, so a 2.7 server should in theory support 2.6 clients, and 0.25 clients less so. YMMV, as there really isn't a strict guarantee of backwards compatibility in any case. Check out: http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notesand you'll see the 2.7 release had a lot more changes than the 2.6 branch. You are likely to have fewer issues migrating from 0.25 to 2.6 vs 2.7. Two things to consider when you are making this migration. 1) 2.6.9 is a more "stable" code base. (Stable meaning mature and vetted). 1) 2.7.4 is a more featureful, faster-moving code base. (Faster moving because it's the active branch and is newer). We are just now feeling that it is ready for new deployments, so if the features are compelling, maybe the risk and pain of a two major version upgrade might be worth it. I still think skipping major puppet versions when upgrading is somewhat risky, and I would probably move my environment to 2.6.9 and then plan on a later move to 2.7. I guess for me the deciding factors would be, a) how large is my code base (the smaller it is, the easier it will be to debug any issues that come up), and b) what is my pain tolerance if there are incompatibilities that come up. -Brian On Fri, Sep 23, 2011 at 6:06 PM, brokenpipe <yvo.vando...@gmail.com> wrote: > I've been tasked at my workplace to upgrade our puppet installation to > a more modern version. Currently all the environments run a RubyGem > version of puppet 0.25.4 on mostly RHEL/Centos 5.3 - 5.5 (there are, > like most environments, a few laggards running RHEL4 or new machines > running CentOS 6). > > The plan is to upgrade these to the most stable version of Puppet, > which at the time of writing is 2.7.3. > > I plan on building RPMs on RHEL5.3 for Puppet 2.7.3 against the Ruby > version that RHEL5 shipped with which is 1.8.5 I believe. > > Are there are any significant gotaches. My plan was to upgrade the > server first and then do a few roll outs to some QA machines and see > how it goes. However there is some concern in the group that 0.25.4 > agents are unable to talk to a 2.7.3 server. Are these unfounded or > true? > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@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. > > -- <http://aws.amazon.com/solutions/solution-providers/brandorr/> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
