For my use case, I have set the following in puppet.conf on the agent
[puppetd]
noop=true
on the server, in the puppet module, I set the following:
file{"/etc/puppet/puppet.conf":
noop => false,
content => template("puppet/puppet-agent.conf"),
}
I have noticed that this works, noop effects everything except the
puppet.conf file, here is some output
notice: Starting catalog run
notice: //Node[SERVER]/test/Exec[echo "This is the Test
Class"]/returns: is
notrun, should be 0 *(noop)*
39c39
< # TEST1
---> # TEST2
notice: //Node[SERVER]/base/puppet/File[/etc/puppet/puppet.conf]:
Filebucketed to main with sum 612edd1118e135cdd89675c1c8f981ae
notice: //Node[SERVER]/base/puppet/File[/etc/puppet/puppet.conf]/content:
content changed ''{md5}612edd1118e135cdd89675c1c8f981ae'' to
''{md5}14ce20b1d2499bed640a26e051a52909''
notice: Reparsing /etc/puppet/puppet.conf
My question is:
Is this intended behavior, will this be supported in future versions, or
will this be likely to break.
regards,
Dan
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
David Schmitt
2009-Jul-15 14:35 UTC
[Puppet Users] Re: will resource noop always override puppetd
Dan Bode wrote: [noop on resource overrides global noop setting]> Is this intended behavior, will this be supported in future versions, or > will this be likely to break.The UPGRADE document for 0.24.3 says this:> Downloading plugins and facts now ignores noop. Note that this > changes the behaviour of a resource''s noop setting. The resources noop> setting will now alway override the global setting (previously, > whichever was true would win). from http://reductivelabs.com/trac/puppet/wiki/UPGRADE#id16 Regards, DavidS --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Nigel Kersten
2009-Jul-15 15:06 UTC
[Puppet Users] Re: will resource noop always override puppetd
On Wed, Jul 15, 2009 at 7:35 AM, David Schmitt<david@dasz.at> wrote:> > Dan Bode wrote: > [noop on resource overrides global noop setting] >> Is this intended behavior, will this be supported in future versions, or >> will this be likely to break. > > The UPGRADE document for 0.24.3 says this: > >> Downloading plugins and facts now ignores noop. Note that this >> changes the behaviour of a resource''s noop setting. The resources noop > > setting will now alway override the global setting (previously, > > whichever was true would win). > > from http://reductivelabs.com/trac/puppet/wiki/UPGRADE#id16This isn''t true for factsync or pluginsync though. root# puppetd --version 0.24.8 root# rm -Rf /var/lib/puppet/facts/* root# rm -Rf /var/lib/puppet/lib/* root# puppetd -t --factsync --pluginsync --noop info: Retrieving plugins notice: /File[/var/puppet/lib]/checksum: checksum changed ''{mtime}Wed Jun 17 11:29:46 -0700 2009'' to ''{mtime}Wed Jul 15 08:05:11 -0700 2009'' notice: /File[/var/puppet/lib/provider]/ensure: created [...] info: Retrieving facts notice: /File[/var/puppet/facts]/checksum: checksum changed ''{mtime}Tue Jul 14 09:33:23 -0700 2009'' to ''{mtime}Wed Jul 15 08:05:08 -0700 2009'' [...] and I''ve yet to get any reliable working method going for facts and plugins in modules with environments that doesn''t rely upon factsync/pluginsync.> > > Regards, DavidS > > > >-- Nigel Kersten nigelk@google.com System Administrator Google, Inc. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Dan Bode
2009-Jul-15 15:06 UTC
[Puppet Users] Re: will resource noop always override puppetd
thanks David, At least this feature was implemented for a good reason (even though I wish they would add certificates to that list:) It seems reasonable to assume that this feature will not break in the future. On Wed, Jul 15, 2009 at 4:35 PM, David Schmitt <david@dasz.at> wrote:> > Dan Bode wrote: > [noop on resource overrides global noop setting] > > Is this intended behavior, will this be supported in future versions, or > > will this be likely to break. > > The UPGRADE document for 0.24.3 says this: > > > Downloading plugins and facts now ignores noop. Note that this > > changes the behaviour of a resource''s noop setting. The resources noop > > setting will now alway override the global setting (previously, > > whichever was true would win). > > from http://reductivelabs.com/trac/puppet/wiki/UPGRADE#id16 > > > Regards, DavidS > > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
David Schmitt
2009-Jul-16 07:56 UTC
[Puppet Users] Re: will resource noop always override puppetd
Nigel Kersten wrote:> On Wed, Jul 15, 2009 at 7:35 AM, David Schmitt<david@dasz.at> wrote: >> Dan Bode wrote: >> [noop on resource overrides global noop setting] >>> Is this intended behavior, will this be supported in future versions, or >>> will this be likely to break. >> The UPGRADE document for 0.24.3 says this: >> >>> Downloading plugins and facts now ignores noop. Note that this >>> changes the behaviour of a resource''s noop setting. The resources noop >> > setting will now alway override the global setting (previously, >> > whichever was true would win). >> >> from http://reductivelabs.com/trac/puppet/wiki/UPGRADE#id16 > > > This isn''t true for factsync or pluginsync though. > > > root# puppetd --version > 0.24.8 > root# rm -Rf /var/lib/puppet/facts/* > root# rm -Rf /var/lib/puppet/lib/* > root# puppetd -t --factsync --pluginsync --noop > info: Retrieving plugins > notice: /File[/var/puppet/lib]/checksum: checksum changed ''{mtime}Wed > Jun 17 11:29:46 -0700 2009'' to ''{mtime}Wed Jul 15 08:05:11 -0700 2009'' > notice: /File[/var/puppet/lib/provider]/ensure: created > [...] > info: Retrieving facts > notice: /File[/var/puppet/facts]/checksum: checksum changed > ''{mtime}Tue Jul 14 09:33:23 -0700 2009'' to ''{mtime}Wed Jul 15 08:05:08 > -0700 2009'' > [...]But that''s exactly what the cited paragraph says, no: "Downloading plugins and facts now ignores noop." Regards, DavidS --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Luke Kanies
2009-Jul-22 00:15 UTC
[Puppet Users] Re: will resource noop always override puppetd
On Jul 15, 2009, at 1:24 AM, Dan Bode wrote:> For my use case, I have set the following in puppet.conf on the agent > > [puppetd] > noop=true > > on the server, in the puppet module, I set the following: > > file{"/etc/puppet/puppet.conf": > noop => false, > content => template("puppet/puppet-agent.conf"), > } > > I have noticed that this works, noop effects everything except the > puppet.conf file, here is some output > > notice: Starting catalog run > notice: //Node[SERVER]/test/Exec[echo "This is the Test Class"]/ > returns: is notrun, should be 0 (noop) > 39c39 > < # TEST1 > --- > > # TEST2 > notice: //Node[SERVER]/base/puppet/File[/etc/puppet/puppet.conf]: > Filebucketed to main with sum 612edd1118e135cdd89675c1c8f981ae > notice: //Node[SERVER]/base/puppet/File[/etc/puppet/puppet.conf]/ > content: content changed ''{md5}612edd1118e135cdd89675c1c8f981ae'' to > ''{md5}14ce20b1d2499bed640a26e051a52909'' > notice: Reparsing /etc/puppet/puppet.conf > > My question is: > > Is this intended behavior, will this be supported in future > versions, or will this be likely to break.That''s your own code managing puppet.conf, not puppet, so yeah, that will continue to work. -- Barondes'' First Law: Science abhors contradictions; scientists'' minds are replete with them. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---