[Puppet Users] Open Source to Enterprise migration?

[Shawn Knight]

Hi,

Can any users of Puppet tell me about experiences in upgrading a Puppet 
Open Source environment to Enterprise?  We're evaluating what our options 
are in getting started with our new infrastructure deployment and we'd love 
a sense of how painful will it be if we start with OS and later decide to 
spring for commercial.

Obviously experiences with more recent versions are good, but I'm all 
ears.  Things like You know, the PE upgrade tool basically just works or 
Turned out to be 2 days of downtime with a lot of tears and editing config 
files are things I want to hear, either way. :D

Cheers,
--Shawn

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/rjGuyNHLSNEJ.
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.

Re: [Puppet Users] Open Source to Enterprise migration?

[Aaron Grewell]

On Wed, Oct 10, 2012 at 9:01 AM, Shawn Knight shawnkni...@gmail.com wrote:
 Hi,

 Can any users of Puppet tell me about experiences in upgrading a Puppet Open
 Source environment to Enterprise?

Hi Shawn,
We went through this with Puppet 2.6 and PE 2.0.  It wasn't
particularly painful, though we did have Puppet Labs PS on site to
help.  For a standalone installation of Puppet I wouldn't consider
that necessary, but if you want to add HA, multiple masters, or other
complex configs you may want to consider it.  It depends on whether
you've already done those things in your existing Puppet install.

At a basic level we configured our CA's, had our old Puppet Masters
configure the clients to use the PE Masters, then had the PE Masters
install the PE Agent.  It was easier than running the PE Installer
everywhere.  If your existing Puppet infrastructure is too new you may
not be able to go this route since the agents can't be newer than the
master.

Planning elements: if you're not using the Puppet Dashboard already
you'll want to think about whether the MySQL server and PE Console
services need to be HA.  If you're going to use the PE Console as an
ENC then I'd vote yes, since the ENC becomes a single point of failure
regardless of how many Masters you have.  You'll also want to read up
on the Puppet Certificate Authority since you'll be  dealing with your
existing certificates one way or another.

If you're not using MCollective it's one of the nice things about PE
since it comes pre-configured and you don't have to learn how to
configure ActiveMQ and friends right away.  Unfortunately it doesn't
run arbitrary programs so in order to extend it to do new things
you'll have to read up on a little bit of Ruby.

All-in-all the complexity of it mostly depends upon the complexity of
your existing environment.  As far as downtime goes, you can easily
run them side-by-side (managing different clients obviously) so you
shouldn't need to worry about having completely unmanaged systems.

-- 
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.