Hi. Have anyone ever managed several geographically distributed systems with Puppet? I have several almost exactly similar deployments (except the server IP''s), which management I''m looking to convert to Puppet. I have 2 options: * Have each deployment to host it''s own PuppetMaster for providing local configurations, then synchronize somehow the PuppetMasters (maybe with puppet again) * Host the PuppetMaster on AWS EC2 for high-availability, and provide configurations to all deployments from single point Has anyone tried the second option, and how it worked out? I''m especially interested in High-Availability performance under such environment. Thanks. -- 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.
hello, I have machines in 4 countries, I tend to put a master per country but not always - depends on the amount of machines. Furthest away I have one is ~350 ms and it works fine, I send puppets to nearest master using geodns and have one designated as reporting server ----- "SyRenity" <stas.oskin@gmail.com> wrote:> Hi. > > Have anyone ever managed several geographically distributed systems > with Puppet? > > I have several almost exactly similar deployments (except the server > IP''s), which management I''m looking to convert to Puppet. > > > I have 2 options: > > * Have each deployment to host it''s own PuppetMaster for providing > local configurations, then synchronize somehow the PuppetMasters > (maybe with puppet again) > > * Host the PuppetMaster on AWS EC2 for high-availability, and provide > configurations to all deployments from single point > > Has anyone tried the second option, and how it worked out? I''m > especially interested in High-Availability performance under such > environment. > > Thanks. > > -- > 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.-- R.I.Pienaar -- 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 Mon, Jan 11, 2010 at 10:07 AM, SyRenity <stas.oskin@gmail.com> wrote:> Hi. > > Have anyone ever managed several geographically distributed systems > with Puppet? > > I have several almost exactly similar deployments (except the server > IP''s), which management I''m looking to convert to Puppet. > > > I have 2 options: > > * Have each deployment to host it''s own PuppetMaster for providing > local configurations, then synchronize somehow the PuppetMasters > (maybe with puppet again) >Isn''t your config already in an SCM of some kind? We just sync all our puppet masters to our repositories.> > * Host the PuppetMaster on AWS EC2 for high-availability, and provide > configurations to all deployments from single point > > Has anyone tried the second option, and how it worked out? I''m > especially interested in High-Availability performance under such > environment.> Thanks. > > -- > 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > > >-- nigel -- 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.
Hi.> Isn''t your config already in an SCM of some kind? > > We just sync all our puppet masters to our repositories.I''m just building our first config, and trying to get it as right as possible. So the preferred approach is to host the configs in SVN, running on EC2 machine for example, then have scheduled SVN updates for the geographically distributed puppet masters? Then it would still give central management, but allow to let each deployment work against it''s own puppet master? Thanks. -- 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.
I have many puppet masters, and each one can provide configuration to each and every client (or master which is also a client), the puppet mater can run against it self or another puppet master. cheers, Ohad On Tue, Jan 12, 2010 at 5:36 PM, SyRenity <stas.oskin@gmail.com> wrote:> Hi. > > > Isn''t your config already in an SCM of some kind? > > > > We just sync all our puppet masters to our repositories. > > I''m just building our first config, and trying to get it as right as > possible. > > So the preferred approach is to host the configs in SVN, running on > EC2 machine for example, then have scheduled SVN updates for the > geographically distributed puppet masters? > > Then it would still give central management, but allow to let each > deployment work against it''s own puppet master? > > Thanks. > > -- > 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > > >-- 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.
Hi. Thanks for all the advices. So the recommended strategy seems to be: * One super-master puppet in cloud * Local puppet master in every deployment * Super-puppet master configures all the local puppet-masters, which in turn configure their clients Something like this? The questions I have are: 1) Is it possible to push modules/manifests update via Puppet? Is it git, or there can be another, push (non-code version) approach? 2) Will such setup require global DNS, or I can still have local DNS in every deployment? Thanks again. On Jan 12, 2:38 pm, Ohad Levy <ohadl...@gmail.com> wrote:> I have many puppet masters, and each one can provide configuration to each > and every client (or master which is also a client), the puppet mater can > run against it self or another puppet master. > > cheers, > Ohad > > On Tue, Jan 12, 2010 at 5:36 PM, SyRenity <stas.os...@gmail.com> wrote: > > Hi. > > > > Isn''t your config already in an SCM of some kind? > > > > We just sync all our puppet masters to our repositories. > > > I''m just building our first config, and trying to get it as right as > > possible. > > > So the preferred approach is to host the configs in SVN, running on > > EC2 machine for example, then have scheduled SVN updates for the > > geographically distributed puppet masters? > > > Then it would still give central management, but allow to let each > > deployment work against it''s own puppet master? > > > Thanks. > > > -- > > 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<puppet-users%2Bunsubscribe@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/puppet-users?hl=en.-- 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.