I inherited a 0.2.5 puppet installation. I''m totally new to puppet. No clue. I have managed clusters with ROCKS before. The big ideas translate readily. So maybe just half a clue. Out of curiosity, why the big version numbering jump for Puppet? The releases go from 0.x straight to 2.x. Puppet looks great so far. But documentation is sprawling. It looks like 0.2.5 has been abandoned. Any idea where I can find dedicated 0.2.5 docs? Preferably online? I''m guessing the 0.2.5 -> 2.x migration must be common. Can I expect this to be a slam dunk? Thanks much! Brian -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
genkuro wrote:> Out of curiosity, why the big version numbering jump for Puppet? The > releases go from 0.x straight to 2.x.The big jump was because our release numbering was wrong - major feature-heavy releases occurred within minor release numbering. So when we had a chance we changed the numbering up to properly reflect feature/maintenance releases.> > Puppet looks great so far. But documentation is sprawling. It looks > like 0.2.5 has been abandoned. Any idea where I can find dedicated > 0.2.5 docs? Preferably online?We have stopped issuing maintenance for 0.25.5 except for potential security issues because more recent releases provide better performance and features. The reference docs for 0.25.5 are available at: http://docs.puppetlabs.com/references/0.25.5/ Generally speaking (where possible) the rest of the Docs site calls out versions of specific features.> > I''m guessing the 0.2.5 -> 2.x migration must be common. Can I expect > this to be a slam dunk?There are no major issues but testing is obviously recommended. The Puppet model is to upgrade the master first and then the clients. We guarantee backwards compatibility with older clients talking to newer masters but not vice versa. Hope that helps! James -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf <http://www.bit.ly/puppetconfsig>, September 22nd and 23rd in Portland, Oregon, USA. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Sat, Sep 3, 2011 at 1:00 AM, genkuro <genkuro@gmail.com> wrote:> I''m guessing the 0.2.5 -> 2.x migration must be common. Can I expect > this to be a slam dunk?We recently did a large (100 nodes) migration from 0.25 to 2.6. The biggest issue was ensuring all our modules worked without any unexpected changes. Standard testing will pick up anything like this and we only had a couple of very minor issues. A good tip if you plan to ''upgrade puppet with puppet'' like we did on a debian platform remember to set ''hasrestart => true'' on your puppet service ''init'' provider. 40 nodes had updated themselves before we realised puppet didn''t know how to start itself back up, without that switch, after being upgraded. This may apply to other platforms so test for it. Regards, Edward -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.