I''m thinking about how to set up the processes for Production puppet runs now. Being ultra-conservative here, we''d like to see what would happen before pressing the red button. I can run in noop mode, and everything is evaluated but nothing is done. A YAML report magically appears on the Puppetmaster which my script parses and spits out something the management can read (I''m using reports = store). I''m currently running puppetd on a daily interval with noop=true in puppet.conf. My issue is how to make it run --no-noop. Puppetrun doesn''t have anything to override this AFAICS. Currently I''m saying ''Run puppetd --no-noop everywhere via ssh and a for loop'' but that''s not the best. I can''t find a way of using schedules or tags to limit execution because then you don''t see the classes evaluated and feeding into the report. Is there an easy way I''m missing? Best regards, Derek ------------------------------------------------------------------------ For important statutory and regulatory disclosures and more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons. Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167) with its registered office at 1 Churchill Place, London, E14 5HP. This email may relate to or be sent from other members of the Barclays Group. ------------------------------------------------------------------------
On Oct 8, 2007, at 8:04 AM, <Derek.Whayman@barclayscapital.com> <Derek.Whayman@barclayscapital.com> wrote:> Currently I''m saying ''Run puppetd --no-noop everywhere via ssh and > a for > loop'' but that''s not the best. > > I can''t find a way of using schedules or tags to limit execution > because > then you don''t see the classes evaluated and feeding into the report. > > Is there an easy way I''m missing?You''re correct, there isn''t a way to disable noop via puppetrun, and there clearly should. I guess feel free to make an enhancement request, but I wouldn''t expect to be able to implement it before 0.24.1, since I''m so focused on the xmlrpc => rest transition. -- I hate to advocate drugs, alcohol, violence, or insanity to anyone, but they''ve always worked for me. -- Hunter S. Thompson --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Thanks, #864 raised. Best regards, Derek -----Original Message----- From: puppet-users-bounces@madstop.com [mailto:puppet-users-bounces@madstop.com] On Behalf Of Luke Kanies Sent: 09 October 2007 05:05 To: Puppet User Discussion Subject: Re: [Puppet-users] Noop functionality On Oct 8, 2007, at 8:04 AM, <Derek.Whayman@barclayscapital.com> <Derek.Whayman@barclayscapital.com> wrote:> Currently I''m saying ''Run puppetd --no-noop everywhere via ssh and a > for loop'' but that''s not the best. > > I can''t find a way of using schedules or tags to limit execution > because then you don''t see the classes evaluated and feeding into the > report. > > Is there an easy way I''m missing?You''re correct, there isn''t a way to disable noop via puppetrun, and there clearly should. I guess feel free to make an enhancement request, but I wouldn''t expect to be able to implement it before 0.24.1, since I''m so focused on the xmlrpc => rest transition. -- I hate to advocate drugs, alcohol, violence, or insanity to anyone, but they''ve always worked for me. -- Hunter S. Thompson --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users ------------------------------------------------------------------------ For important statutory and regulatory disclosures and more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons. Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167) with its registered office at 1 Churchill Place, London, E14 5HP. This email may relate to or be sent from other members of the Barclays Group. ------------------------------------------------------------------------