I''m trying to set a global noop but it doesn''t seem possible, There are 2 bugs open about this which to me look pretty serious as the expected behaviour isn''t the case. http://projects.puppetlabs.com/issues/21286 http://projects.puppetlabs.com/issues/6549 If anyone has a work around (that doesn''t include modifying puppet.conf file) I would be very interested. Cheers, Sam -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
How are you running puppet? If cron or mcollective, you can add a --noop flag to the command line somewhere. On Monday, July 22, 2013 4:29:24 PM UTC-7, Sam Morrison wrote:> > I''m trying to set a global noop but it doesn''t seem possible, > > There are 2 bugs open about this which to me look pretty serious as the > expected behaviour isn''t the case. > > http://projects.puppetlabs.com/issues/21286 > http://projects.puppetlabs.com/issues/6549 > > If anyone has a work around (that doesn''t include modifying puppet.conf > file) I would be very interested. > > Cheers, > Sam > > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
On Wednesday, 24 July 2013 03:12:10 UTC+10, Ellison Marks wrote:> > How are you running puppet? If cron or mcollective, you can add a --noop > flag to the command line somewhere. >We''re just using it the standard way running it as a daemon -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
> > well - perhaps you can put noop = trueor something in puppet.conf on the clients ? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Yeah but then when we push out noop = true in puppet.conf how do we then push out noop = false via puppet if they''re all in noop. Managing on the server is the only way to do it in a safe and scalable way (we have 500+ nodes) On Thu, Jul 25, 2013 at 10:18 PM, Klavs Klavsen <klavs@enableit.dk> wrote:> well - perhaps you can put noop = true > > or something in puppet.conf on the clients ? > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/HzjRMtQlHRU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscribe@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. > > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Hi Sam, it somewhat depends on your requirements, but if you have a window during which changes are not permitted, end of story, what about a cronjob to set it to false at a particular time? or in the same run that you set noop to true, require an exec which creates an at job to re-enable at a specific time? you could go full tilt maverick, and have a cron job which does a curl to a known server asking if the value should be true/false and use sed to change the value, and then wake puppet from its nap. you''re essentially removing the ability for puppet to do anything so you''ll have to use some other tool to let puppet out of it''s cage. I''m sure others have additional (likely better) suggestions.. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Sam,
You could make some changes to you site.pp and set some defaults like this
Exec {
schedule => $::globalvars_schedule,
noop => $::globalvars_noop,
}
File {
schedule => $::globalvars_schedule,
noop => $::globalvars_noop,
}
Group {
schedule => $::globalvars_schedule,
noop => $::globalvars_noop,
}
Mount {
schedule => $::globalvars_schedule,
noop => $::globalvars_noop,
}
Package {
schedule => $::globalvars_schedule,
noop => $::globalvars_noop,
}
Service {
schedule => $::globalvars_schedule,
noop => $::globalvars_noop,
}
User {
schedule => $::globalvars_schedule,
noop => $::globalvars_noop,
}
..... and more .....
Make sure that all puppet types you use within you modules are covered in
the site.pp and have the noop => $::globalvars_noop added.
The final step is to set the topscope variable
''globalvars_noop'' somewhere
(for example hiera, or Puppet console) and your node will be run with noop.
No need to touch any puppet config on the clients, and very easy to manage
:-)
Regards,
Rene vd Linden
Blog: https://www.rvanderlinden.net/wordpress
On Tuesday, July 23, 2013 1:29:24 AM UTC+2, Sam Morrison wrote:
> I''m trying to set a global noop but it doesn''t seem
possible,
>
> There are 2 bugs open about this which to me look pretty serious as the
> expected behaviour isn''t the case.
>
> http://projects.puppetlabs.com/issues/21286
> http://projects.puppetlabs.com/issues/6549
>
> If anyone has a work around (that doesn''t include modifying
puppet.conf
> file) I would be very interested.
>
> Cheers,
> Sam
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Sam, You should setup MCollective. You can implement a simple plugin that changes the global noop setting in puppet.conf and restarts the daemon. That will give you the best scalability, and you have fine-grained control in MCollective on which hosts run using metadata in your Puppet classes and facts. Regards, Justin On Sat, Jul 27, 2013 at 10:52 AM, rvlinden <rene.vanderlinden73@gmail.com> wrote:> Sam, > > You could make some changes to you site.pp and set some defaults like this > > Exec { > schedule => $::globalvars_schedule, > noop => $::globalvars_noop, > } > File { > schedule => $::globalvars_schedule, > noop => $::globalvars_noop, > } > Group { > schedule => $::globalvars_schedule, > noop => $::globalvars_noop, > } > Mount { > schedule => $::globalvars_schedule, > noop => $::globalvars_noop, > } > Package { > schedule => $::globalvars_schedule, > noop => $::globalvars_noop, > } > Service { > schedule => $::globalvars_schedule, > noop => $::globalvars_noop, > } > User { > schedule => $::globalvars_schedule, > noop => $::globalvars_noop, > } > > ..... and more ..... > > > > Make sure that all puppet types you use within you modules are covered in > the site.pp and have the noop => $::globalvars_noop added. > > The final step is to set the topscope variable ''globalvars_noop'' somewhere > (for example hiera, or Puppet console) and your node will be run with noop. > No need to touch any puppet config on the clients, and very easy to manage > :-) > > Regards, > Rene vd Linden > Blog: https://www.rvanderlinden.net/wordpress > > > On Tuesday, July 23, 2013 1:29:24 AM UTC+2, Sam Morrison wrote: >> >> I''m trying to set a global noop but it doesn''t seem possible, >> >> There are 2 bugs open about this which to me look pretty serious as the >> expected behaviour isn''t the case. >> >> http://projects.puppetlabs.com/issues/21286 >> http://projects.puppetlabs.com/issues/6549 >> >> If anyone has a work around (that doesn''t include modifying puppet.conf >> file) I would be very interested. >> >> Cheers, >> Sam >> >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscribe@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Thanks Justin, Yes MCollective would be great, just have to find the time. Rene: I have gone with your solution at the moment. I still think it''s a bug that doing it on the Resource resource doesn''t work, hopefully someone will look into those bugs. Cheers, Sam On Sunday, 28 July 2013 02:11:25 UTC+10, Justin Brown wrote:> > Sam, > > You should setup MCollective. You can implement a simple plugin that > changes the global noop setting in puppet.conf and restarts the > daemon. > > That will give you the best scalability, and you have fine-grained > control in MCollective on which hosts run using metadata in your > Puppet classes and facts. > > Regards, > Justin > > On Sat, Jul 27, 2013 at 10:52 AM, rvlinden > <rene.vand...@gmail.com <javascript:>> wrote: > > Sam, > > > > You could make some changes to you site.pp and set some defaults like > this > > > > Exec { > > schedule => $::globalvars_schedule, > > noop => $::globalvars_noop, > > } > > File { > > schedule => $::globalvars_schedule, > > noop => $::globalvars_noop, > > } > > Group { > > schedule => $::globalvars_schedule, > > noop => $::globalvars_noop, > > } > > Mount { > > schedule => $::globalvars_schedule, > > noop => $::globalvars_noop, > > } > > Package { > > schedule => $::globalvars_schedule, > > noop => $::globalvars_noop, > > } > > Service { > > schedule => $::globalvars_schedule, > > noop => $::globalvars_noop, > > } > > User { > > schedule => $::globalvars_schedule, > > noop => $::globalvars_noop, > > } > > > > ..... and more ..... > > > > > > > > Make sure that all puppet types you use within you modules are covered > in > > the site.pp and have the noop => $::globalvars_noop added. > > > > The final step is to set the topscope variable ''globalvars_noop'' > somewhere > > (for example hiera, or Puppet console) and your node will be run with > noop. > > No need to touch any puppet config on the clients, and very easy to > manage > > :-) > > > > Regards, > > Rene vd Linden > > Blog: https://www.rvanderlinden.net/wordpress > > > > > > On Tuesday, July 23, 2013 1:29:24 AM UTC+2, Sam Morrison wrote: > >> > >> I''m trying to set a global noop but it doesn''t seem possible, > >> > >> There are 2 bugs open about this which to me look pretty serious as the > >> expected behaviour isn''t the case. > >> > >> http://projects.puppetlabs.com/issues/21286 > >> http://projects.puppetlabs.com/issues/6549 > >> > >> If anyone has a work around (that doesn''t include modifying puppet.conf > >> file) I would be very interested. > >> > >> Cheers, > >> Sam > >> > >> > > -- > > You received this message because you are subscribed to the Google > Groups > > "Puppet Users" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to puppet-users...@googlegroups.com <javascript:>. > > To post to this group, send email to puppet...@googlegroups.com<javascript:>. > > > Visit this group at http://groups.google.com/group/puppet-users. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.