Hi, I am looking for a way, i.e. best practice for managing config changes safely and efficiently. Something like clever module organization could certainly help, but I am looking for something else as well: Is it possible to set up puppetd in a way, that it just listens and reports, but does not apply config changes automatically, and in the same time has the ability to trigger it somehow? Thanks, Bela --- [production] 13 modulepath=/srv/puppet/modules:/etc/puppet/modules:/usr/share/ puppet/modules 14 15 [testing] 16 modulepath=/srv/puppet/modules-testing:/etc/puppet/modules:/usr/ share/puppet/modules 17 18 [development] 19 modulepath=/srv/puppet/modules-development:/etc/puppet/modules:/ usr/share/puppet/modules 20 trace=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-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
--On Thursday, July 10, 2008 08:21:03 AM -0700 pc2 <bela.pesics@gmail.com> wrote:> Is it possible to set up puppetd in a way, that it just listens and > reports, but does not apply config changes automatically, and in the > same time has the ability to trigger it somehow?You can set noop = true in the puppet.conf and puppet will not make changes to the system. If you then run puppetd with --test, it will show you all the changes it would make but not actually make them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Thanks, I am aware of this possibility. However even if it was possible to override --noop somehow in case I wanted the changes it would not be push. ;-( Actually I have just that found I need: http://linux.die.net/man/8/puppetrun Then the question remains. How can I set up puppetd so that it listens/ reports but never applies changes automatically only when triggered by puppetrun? :-O On Jul 10, 8:31 pm, Digant C Kasundra <dig...@stanford.edu> wrote:> --On Thursday, July 10, 2008 08:21:03 AM -0700 pc2 <bela.pes...@gmail.com> > wrote: > > > Is it possible to set up puppetd in a way, that it just listens and > > reports, but does not apply config changes automatically, and in the > > same time has the ability to trigger it somehow? > > You can set noop = true in the puppet.conf and puppet will not make changes > to the system. If you then run puppetd with --test, it will show you all > the changes it would make but not actually make them.--~--~---------~--~----~------------~-------~--~----~ 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 Thu, Jul 10, 2008 at 5:23 PM, pc2 <bela.pesics@gmail.com> wrote:> > Thanks, I am aware of this possibility. However even if it was > possible to override --noop somehow in case I wanted the changes it > would not be push. ;-( > > Actually I have just that found I need: http://linux.die.net/man/8/puppetrun > > Then the question remains. How can I set up puppetd so that it listens/ > reports but never applies changes automatically only when triggered by > puppetrun? :-O >I am curious, why do you want to have to manually trigger puppet changes? The whole idea behind puppet is so that you don''t have to do things manually. You might be able to use environments to pull of what you want though. You have the normal operation take place in a an environment with noop set and when you want it you change to the noop false environment. Evan Evan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
This would be a trade-off to get some extra safety. We can not allow full automation, we only want changes when explicitly required. In that case of course pretty much everything is done automated by puppet. Environments are good, but the point is that I would like to trigger this via/from the puppetmaster without having to log-in to a server (puppetd client). Any ideas? I have not tried puppetrun, is it the right tool for something like this? /Bela On Jul 11, 11:34 pm, "Evan Hisey" <ehi...@gmail.com> wrote:> On Thu, Jul 10, 2008 at 5:23 PM, pc2 <bela.pes...@gmail.com> wrote: > > > Thanks, I am aware of this possibility. However even if it was > > possible to override --noop somehow in case I wanted the changes it > > would not be push. ;-( > > > Actually I have just that found I need:http://linux.die.net/man/8/puppetrun > > > Then the question remains. How can I set up puppetd so that it listens/ > > reports but never applies changes automatically only when triggered by > > puppetrun? :-O > > I am curious, why do you want to have to manually trigger puppet > changes? The whole idea behind puppet is so that you don''t have to do > things manually. You might be able to use environments to pull of what > you want though. You have the normal operation take place in a an > environment with noop set and when you want it you change to the noop > false environment. > > Evan > > Evan--~--~---------~--~----~------------~-------~--~----~ 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 Wed, Jul 16, 2008 at 2:38 PM, pc2 <bela.pesics@gmail.com> wrote:> > This would be a trade-off to get some extra safety. We can not allow > full automation, we only want changes when explicitly required. In > that case of course pretty much everything is done automated by > puppet. > > Environments are good, but the point is that I would like to trigger > this via/from the puppetmaster without having to log-in to a server > (puppetd client). > > Any ideas? I have not tried puppetrun, is it the right tool for > something like this? > > /Bela >You can setup the clients puppetd with listen= true. With this set you can use puppetrun to trigger remote puppetd executions and pass the settings on to it. It is documented on the wiki put I can''t place were of the top of my head. Evan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---