Whew.... I am struggling on a puppet architecture design learning curve. I believe if i could find a good ''stand alone'' example, it would clarify a lot of the questions I have and it would help me set up a test machine. I hoping to find an example of a stand alone that has a process flow similar to: - start puppet with Capistrano - puppet checks the ''repository'' and determines changes have been made - applies any changes Please share any instructions or good reads ... I am looking to support a set of servers that support 10+ clients, each client has a dev, test and production server for 5 different web applications. Regards. -- 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 12 July 2010 14:33, bmort <propertywholesaler@gmail.com> wrote:> > - start puppet with Capistrano > - puppet checks the ''repository'' and determines changes have been > made > - applies any changes > >Can I ask why you want to do that? You want to push the Puppet manifests out to the node with Capistrano? It would be a simple capistrano task to run Puppet standalone. You can override configuration settings on the command line. But I ''m wondering why you''d want do to that. J. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- 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.
Lindsay Holmwood
2010-Jul-13 00:01 UTC
Re: [Puppet Users] puppet capistrano and repository
On 13 July 2010 06:51, Julian Simpson <simpsonjulian@gmail.com> wrote:> > > On 12 July 2010 14:33, bmort <propertywholesaler@gmail.com> wrote: >> >> - start puppet with Capistrano >> - puppet checks the ''repository'' and determines changes have been >> made >> - applies any changes >> > > Can I ask why you want to do that? You want to push the Puppet manifests > out to the node with Capistrano? It would be a simple capistrano task to > run Puppet standalone. You can override configuration settings on the > command line. But I ''m wondering why you''d want do to that.Running Puppet without a puppetmaster would be one reason. You could have a repository of your manifests that your machines check out and run against. Cap is a poor mans way of orchestrating that setup in lieu of something more powerful like MCollective. Lindsay -- w: http://holmwood.id.au/~lindsay/ t: @auxesis -- 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 Jul 12, 9:33 am, bmort <propertywholesa...@gmail.com> wrote:> Whew.... I am struggling on a puppet architecture design learning > curve. > > I believe if i could find a good ''stand alone'' example, it would > clarify a lot of the questions I have and it would help me set up a > test machine. > > I hoping to find an example of a stand alone that has a process flow > similar to: > > - start puppet with Capistrano > - puppet checks the ''repository'' and determines changes have been > made > - applies any changes > > Please share any instructions or good reads ... > > I am looking to support a set of servers that support 10+ clients, > each client has a dev, test and production server for 5 different web > applications. > > Regards.i''m sort of looking to do similar things. basically, i''m trying to hash out the best way to run puppet without a puppetmaster. i support various businesses with mostly lenient outbound firewalls, though some restrict traffic on high ports and the like. one way around this is to run puppet locally. i have some basic groundwork to keep all the manifests and modules, etc. in a git repo which then gets checked out via http by the clients. i''m looking to use git hooks to run puppet. something simple like this seemed to work, though puppet didn''t actually run on the client. no error checking or anything in this yet… just quick and dirty. #!/bin/bash # post-checkout testing # stored in .git/hooks/post-checkout # 100712, initial version, nate # /usr/bin/logger -t PUPPET -i "running puppet..." /usr/bin/puppet -v /etc/pconfig/manifests/site.pp /usr/bin/logger -t PUPPET -i "puppet run complete" instead of using capistrano, would a post pull/clone hook do what you want? -- 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.
Patrick Mohr
2010-Jul-13 02:54 UTC
Re: [Puppet Users] Re: puppet capistrano and repository
On Jul 12, 2010, at 6:31 PM, nate wrote:> On Jul 12, 9:33 am, bmort <propertywholesa...@gmail.com> wrote: >> Whew.... I am struggling on a puppet architecture design learning >> curve. >> >> I believe if i could find a good ''stand alone'' example, it would >> clarify a lot of the questions I have and it would help me set up a >> test machine. >> >> I hoping to find an example of a stand alone that has a process flow >> similar to: >> >> - start puppet with Capistrano >> - puppet checks the ''repository'' and determines changes have been >> made >> - applies any changes >> >> Please share any instructions or good reads ... >> >> I am looking to support a set of servers that support 10+ clients, >> each client has a dev, test and production server for 5 different web >> applications. >> >> Regards. > > i''m sort of looking to do similar things. basically, i''m trying to > hash out the best way to run puppet without a puppetmaster. > > i support various businesses with mostly lenient outbound firewalls, > though some restrict traffic on high ports and the like.What about running the puppetmaster on a low port?> one way around this is to run puppet locally. i have some basic > groundwork to keep all the manifests and modules, etc. in a git repo > which then gets checked out via http by the clients. > > i''m looking to use git hooks to run puppet. something simple like this > seemed to work, though puppet didn''t actually run on the client. no > error checking or anything in this yet… just quick and dirty. > > #!/bin/bash > # post-checkout testing > # stored in .git/hooks/post-checkout > # 100712, initial version, nate > # > /usr/bin/logger -t PUPPET -i "running puppet..." > /usr/bin/puppet -v /etc/pconfig/manifests/site.pp > /usr/bin/logger -t PUPPET -i "puppet run complete" > > > > instead of using capistrano, would a post pull/clone hook do what you > want? > > -- > 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. >-- 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.
> > Running Puppet without a puppetmaster would be one reason. > > You could have a repository of your manifests that your machines check > out and run against. Cap is a poor mans way of orchestrating that > setup in lieu of something more powerful like MCollective. > > I could have asked that question in a more coherent way. I run Puppetwithout a puppetmaster myself. My process starts with a Rake build that invokes Puppet standalone, with all of the relevant configuration options supplied on the command line, with their paths resolved so I can check out my repo and then run ''rake puppet:run''. The original question suggested that they wanted something more complex, with a Continuous Integration-like approach to checking for changes. Personally I wouldn''t do that as you should be able to run Puppet with impunity, whenever you feel like it. To me, testing for changes suggests that someone really isn''t happy about the idea :) Best Julian. -- 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.
Good stuff thanks all. All of the responses have got me thinking. Sorry for any confusion about the starting of the puppet client. Whenever I feel like is the goal. Process goal: - change a monit, apache, odbc, passenger, mongrel config - check that change(s) into svn for that server(s) - start puppet on that server(s) (Capistrano is a legacy app; mcollective is on the radar. ty) - puppet checks the repository of manifest or do i get the manifest files to the server before starting puppet? - puppet applies any changes ( maybe send a little obtw email ) i guess quick and dirty svn hook is what i am looking for .... On Jul 13, 5:56 am, Julian Simpson <simpsonjul...@gmail.com> wrote:> > Running Puppet without a puppetmaster would be one reason. > > > You could have a repository of your manifests that your machines check > > out and run against. Cap is a poor mans way of orchestrating that > > setup in lieu of something more powerful like MCollective. > > > I could have asked that question in a more coherent way. I run Puppet > > without a puppetmaster myself. My process starts with a Rake build that > invokes Puppet standalone, with all of the relevant configuration options > supplied on the command line, with their paths resolved so I can check out > my repo and then run ''rake puppet:run''. The original question suggested > that they wanted something more complex, with a Continuous Integration-like > approach to checking for changes. > > Personally I wouldn''t do that as you should be able to run Puppet with > impunity, whenever you feel like it. To me, testing for changes suggests > that someone really isn''t happy about the idea :) > > Best > > Julian.-- 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.
Hmmm ... looks like vcsrepo might be the hook I am looking for .... Here is a current puppet users thread discussion: http://groups.google.com/group/puppet-users/browse_thread/thread/954f3bb356e9a468 On Jul 13, 9:02 am, bmort <propertywholesa...@gmail.com> wrote:> Good stuff thanks all. All of the responses have got me thinking. > > Sorry for any confusion about the starting of the puppet client. > Whenever I feel like is the goal. > > Process goal: > - change a monit, apache, odbc, passenger, mongrel config > - check that change(s) into svn for that server(s) > - start puppet on that server(s) (Capistrano is a legacy app; > mcollective is on the radar. ty) > - puppet checks the repository of manifest or do i get the manifest > files to the server before starting puppet? > - puppet applies any changes ( maybe send a little obtw email ) > > i guess quick and dirty svn hook is what i am looking for .... > > On Jul 13, 5:56 am, Julian Simpson <simpsonjul...@gmail.com> wrote: > > > > Running Puppet without a puppetmaster would be one reason. > > > > You could have a repository of your manifests that your machines check > > > out and run against. Cap is a poor mans way of orchestrating that > > > setup in lieu of something more powerful like MCollective. > > > > I could have asked that question in a more coherent way. I run Puppet > > > without a puppetmaster myself. My process starts with a Rake build that > > invokes Puppet standalone, with all of the relevant configuration options > > supplied on the command line, with their paths resolved so I can check out > > my repo and then run ''rake puppet:run''. The original question suggested > > that they wanted something more complex, with a Continuous Integration-like > > approach to checking for changes. > > > Personally I wouldn''t do that as you should be able to run Puppet with > > impunity, whenever you feel like it. To me, testing for changes suggests > > that someone really isn''t happy about the idea :) > > > Best > > > Julian.-- 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.