Hello All, I am trying to put puppet into push mode only. The instructions I''ve seen have said to put listen=true in puppet.conf but that doesn''t seem to have stopped the pull every 30 minutes. What else needs to be set? Thanks, Jim -- “Twenty years from now you will be more disappointed by the things that you didn’t do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover.” – Mark Twain -- 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.
man puppet.conf
---
runinterval
How often puppetd applies the client configuration; in seconds.
* Default: 1800
---
i would assume that an interval of 0 would prevent puppet from running
periodically, perhaps someone else can correct me if i''m wrong.
byron
From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On
Behalf Of James Louis
Sent: Tuesday, October 05, 2010 9:34 AM
To: puppet-users@googlegroups.com
Subject: [Puppet Users] puppet push mode
Hello All,
I am trying to put puppet into push mode only. The instructions I''ve
seen have said to put listen=true in puppet.conf but that doesn''t seem
to have stopped the pull every 30 minutes. What else needs to be set?
Thanks,
Jim
--
"Twenty years from now you will be more disappointed by the things that you
didn''t do than by the ones you did do. So throw off the bowlines. Sail
away from the safe harbor. Catch the trade winds in your sails. Explore. Dream.
Discover."
- Mark Twain
--
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.
--no-client Ohad On Tue, Oct 5, 2010 at 3:33 PM, James Louis <jglouisjr@gmail.com> wrote:> Hello All, > > I am trying to put puppet into push mode only. The instructions I''ve seen > have said to put listen=true in puppet.conf but that doesn''t seem to have > stopped the pull every 30 minutes. What else needs to be set? > > Thanks, > > Jim > > -- > “Twenty years from now you will be more disappointed by the things that you > didn’t do than by the ones you did do. So throw off the bowlines. Sail away > from the safe harbor. Catch the trade winds in your sails. Explore. Dream. > Discover.” > – Mark Twain > > -- > 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<puppet-users%2Bunsubscribe@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.
I couldn''t find anything that said the setting of runinterval would affect the stopping of pull. Ohad, I did find the no-client option and have it in effect. It does appear to stop the pull. On Wed, Oct 6, 2010 at 7:53 AM, Ohad Levy <ohadlevy@gmail.com> wrote:> --no-client > > Ohad > > On Tue, Oct 5, 2010 at 3:33 PM, James Louis <jglouisjr@gmail.com> wrote: > >> Hello All, >> >> I am trying to put puppet into push mode only. The instructions I''ve seen >> have said to put listen=true in puppet.conf but that doesn''t seem to have >> stopped the pull every 30 minutes. What else needs to be set? >> >> Thanks, >> >> Jim >> >> -- >> “Twenty years from now you will be more disappointed by the things that >> you didn’t do than by the ones you did do. So throw off the bowlines. Sail >> away from the safe harbor. Catch the trade winds in your sails. Explore. >> Dream. Discover.” >> – Mark Twain >> >> -- >> 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<puppet-users%2Bunsubscribe@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<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- “Twenty years from now you will be more disappointed by the things that you didn’t do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover.” – Mark Twain -- 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 10/06/2010 03:01 PM, James Louis wrote:> I couldn''t find anything that said the setting of runinterval would affect > the stopping of pull. Ohad, I did find the no-client option and have it in > effect. It does appear to stop the pull.can you look a ticket to improve documentation? Or even contribute a patch? Thanks! ~pete -- 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.
I am in a similar but different situation. I need to have puppet check in only upon boot up and then shutdown until next boot. Does anyone know a puppet way of handling this our should I resort to basic sh scripting to accommodate this? Regards, Mikel On Oct 6, 9:01 am, James Louis <jgloui...@gmail.com> wrote:> I couldn''t find anything that said the setting of runinterval would affect > the stopping of pull. Ohad, I did find the no-client option and have it in > effect. It does appear to stop the pull. > > > > On Wed, Oct 6, 2010 at 7:53 AM, Ohad Levy <ohadl...@gmail.com> wrote: > > --no-client > > > Ohad > > > On Tue, Oct 5, 2010 at 3:33 PM, James Louis <jgloui...@gmail.com> wrote: > > >> Hello All, > > >> I am trying to put puppet into push mode only. The instructions I''ve seen > >> have said to put listen=true in puppet.conf but that doesn''t seem to have > >> stopped the pull every 30 minutes. What else needs to be set? > > >> Thanks, > > >> Jim > > >> -- > >> “Twenty years from now you will be more disappointed by the things that > >> you didn’t do than by the ones you did do. So throw off the bowlines. Sail > >> away from the safe harbor. Catch the trade winds in your sails. Explore. > >> Dream. Discover.” > >> – Mark Twain > > >> -- > >> 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<puppet-users%2Bunsubscribe@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<puppet-users%2Bunsubscribe@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/puppet-users?hl=en. > > -- > “Twenty years from now you will be more disappointed by the things that you > didn’t do than by the ones you did do. So throw off the bowlines. Sail away > from the safe harbor. Catch the trade winds in your sails. Explore. Dream. > Discover.” > – Mark Twain-- 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 10/06/2010 03:17 PM, Mikel King wrote:> I am in a similar but different situation. I need to have puppet check > in only upon boot up and then shutdown until next boot. Does anyone > know a puppet way of handling this our should I resort to basic sh > scripting to accommodate this?@reboot if your cron supports that? ~pete -- 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, Oct 06, 2010 at 03:19:27PM +0200, Peter Meier wrote:> On 10/06/2010 03:17 PM, Mikel King wrote: > > I am in a similar but different situation. I need to have puppet check > > in only upon boot up and then shutdown until next boot. Does anyone > > know a puppet way of handling this our should I resort to basic sh > > scripting to accommodate this? > > @reboot if your cron supports that?If it doesn''t, every Linux distribution and *nix has a set of initscripts (rc scripts on BSDs) that run only on boot. Just run the puppet (rather than puppetd) binary from there. -- Bruce A problem shared brings the consolation that someone else is now feeling as miserable as you. -- 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.
Pete, Is there a central location for Puppet documentation? I would be glad to add/update the docs. Seems there should be a chapter/paragraph on using push only. Jim On Wed, Oct 6, 2010 at 8:16 AM, Peter Meier <peter.meier@immerda.ch> wrote:> On 10/06/2010 03:01 PM, James Louis wrote: > > I couldn''t find anything that said the setting of runinterval would > affect > > the stopping of pull. Ohad, I did find the no-client option and have it > in > > effect. It does appear to stop the pull. > > can you look a ticket to improve documentation? Or even contribute a > patch? Thanks! > > ~pete > > -- > 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- “Twenty years from now you will be more disappointed by the things that you didn’t do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover.” – Mark Twain -- 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.
Exactly what I plan to do, just was wondering if there were a puppet option for this. Thanks guys. On Oct 6, 9:29 am, Bruce Richardson <itsbr...@workshy.org> wrote:> On Wed, Oct 06, 2010 at 03:19:27PM +0200, Peter Meier wrote: > > On 10/06/2010 03:17 PM, Mikel King wrote: > > > I am in a similar but different situation. I need to havepuppetcheck > > > in only upon boot up and then shutdown until next boot. Does anyone > > > know apuppetway of handling this our should I resort to basic sh > > > scripting to accommodate this? > > > @reboot if your cron supports that? > > If it doesn''t, every Linux distribution and *nix has a set of > initscripts (rc scripts on BSDs) that run only on boot. Just run thepuppet(rather than puppetd) binary from there. > > -- > Bruce > > A problem shared brings the consolation that someone else is now > feeling as miserable as you.-- 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.
> Is there a central location for Puppet documentation? I would be glad to > add/update the docs. Seems there should be a chapter/paragraph on using push > only.The wiki is good starting point to add content. And James recently pointed out how to get things to the curated documentation [1]. But I''m not able to find the thread in time, so maybe James can tell you how?! ~pete [1] http://github.com/puppetlabs/puppet-docs -- 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 Oct 6, 2010, at 6:17 AM, Mikel King wrote:> I am in a similar but different situation. I need to have puppet check > in only upon boot up and then shutdown until next boot. Does anyone > know a puppet way of handling this our should I resort to basic sh > scripting to accommodate this?I assume that you can putting "run-once" or "runonce" I don''t remember which, in puppet.conf. If you want startup to hang until the manifest is applied, you can probably put no-daemonize in puppet.conf. Again, I haven''t tried these so make sure you do some testing before you use it in production.> On Oct 6, 9:01 am, James Louis <jgloui...@gmail.com> wrote: >> I couldn''t find anything that said the setting of runinterval would affect >> the stopping of pull. Ohad, I did find the no-client option and have it in >> effect. It does appear to stop the pull. >> >> >> >> On Wed, Oct 6, 2010 at 7:53 AM, Ohad Levy <ohadl...@gmail.com> wrote: >>> --no-client >> >>> Ohad >> >>> On Tue, Oct 5, 2010 at 3:33 PM, James Louis <jgloui...@gmail.com> wrote: >> >>>> Hello All, >> >>>> I am trying to put puppet into push mode only. The instructions I''ve seen >>>> have said to put listen=true in puppet.conf but that doesn''t seem to have >>>> stopped the pull every 30 minutes. What else needs to be set? >> >>>> Thanks, >> >>>> Jim >> >>>> -- >>>> “Twenty years from now you will be more disappointed by the things that >>>> you didn’t do than by the ones you did do. So throw off the bowlines. Sail >>>> away from the safe harbor. Catch the trade winds in your sails. Explore. >>>> Dream. Discover.” >>>> – Mark Twain >> >>>> -- >>>> 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<puppet-users%2Bunsubscribe@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<puppet-users%2Bunsubscribe@googlegroups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/puppet-users?hl=en. >> >> -- >> “Twenty years from now you will be more disappointed by the things that you >> didn’t do than by the ones you did do. So throw off the bowlines. Sail away >> from the safe harbor. Catch the trade winds in your sails. Explore. Dream. >> Discover.” >> – Mark Twain > > -- > 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.
On Wed, Oct 6, 2010 at 9:15 AM, Patrick <kc7zzv@gmail.com> wrote:> > On Oct 6, 2010, at 6:17 AM, Mikel King wrote: > >> I am in a similar but different situation. I need to have puppet check >> in only upon boot up and then shutdown until next boot. Does anyone >> know a puppet way of handling this our should I resort to basic sh >> scripting to accommodate this? > > I assume that you can putting "run-once" or "runonce" I don''t remember which, in puppet.conf."--onetime" http://projects.puppetlabs.com/issues/2646 You can''t put this in the config file in 0.25.x, but you should be able to in 2.6.x> > If you want startup to hang until the manifest is applied, you can probably put no-daemonize in puppet.conf. > > Again, I haven''t tried these so make sure you do some testing before you use it in production. > >> On Oct 6, 9:01 am, James Louis <jgloui...@gmail.com> wrote: >>> I couldn''t find anything that said the setting of runinterval would affect >>> the stopping of pull. Ohad, I did find the no-client option and have it in >>> effect. It does appear to stop the pull. >>> >>> >>> >>> On Wed, Oct 6, 2010 at 7:53 AM, Ohad Levy <ohadl...@gmail.com> wrote: >>>> --no-client >>> >>>> Ohad >>> >>>> On Tue, Oct 5, 2010 at 3:33 PM, James Louis <jgloui...@gmail.com> wrote: >>> >>>>> Hello All, >>> >>>>> I am trying to put puppet into push mode only. The instructions I''ve seen >>>>> have said to put listen=true in puppet.conf but that doesn''t seem to have >>>>> stopped the pull every 30 minutes. What else needs to be set? >>> >>>>> Thanks, >>> >>>>> Jim >>> >>>>> -- >>>>> “Twenty years from now you will be more disappointed by the things that >>>>> you didn’t do than by the ones you did do. So throw off the bowlines. Sail >>>>> away from the safe harbor. Catch the trade winds in your sails. Explore. >>>>> Dream. Discover.” >>>>> – Mark Twain >>> >>>>> -- >>>>> 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<puppet-users%2Bunsubscribe@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<puppet-users%2Bunsubscribe@googlegroups.com> >>>> . >>>> For more options, visit this group at >>>> http://groups.google.com/group/puppet-users?hl=en. >>> >>> -- >>> “Twenty years from now you will be more disappointed by the things that you >>> didn’t do than by the ones you did do. So throw off the bowlines. Sail away >>> from the safe harbor. Catch the trade winds in your sails. Explore. Dream. >>> Discover.” >>> – Mark Twain >> >> -- >> 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. > >-- nigel -- 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, Oct 6, 2010 at 9:01 AM, James Louis <jglouisjr@gmail.com> wrote:> I couldn''t find anything that said the setting of runinterval would affect > the stopping of pull. Ohad, I did find the no-client option and have it in > effect. It does appear to stop the pull. >That does not work for me... what version are you using? I set client=false in the client''s puppet.conf [puppetd] report = true listen = true #noop = true client = false #ignorecache = true But when I start puppet: /etc/init.d/puppet start It still downloads the config, and applies it... How do I make it download and apply only when triggered by puppetrun? And better yet... how do I make it work in noop mode, always, and in op mode only on request? Thanks so much. Mohamed. -- 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 have to use --no-client on the command line when running puppetd. I''ve set it up in my /etc/sysconfig/puppet file on CentOS so it''s pulled in as part of PUPPET_EXTRAOPTS. On Wed, Oct 6, 2010 at 3:09 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote:> On Wed, Oct 6, 2010 at 9:01 AM, James Louis <jglouisjr@gmail.com> wrote: > > I couldn''t find anything that said the setting of runinterval would > affect > > the stopping of pull. Ohad, I did find the no-client option and have it > in > > effect. It does appear to stop the pull. > > > > That does not work for me... what version are you using? > > I set client=false in the client''s puppet.conf > [puppetd] > report = true > listen = true > #noop = true > client = false > #ignorecache = true > > But when I start puppet: /etc/init.d/puppet start > It still downloads the config, and applies it... > > How do I make it download and apply only when triggered by puppetrun? > > And better yet... how do I make it work in noop mode, always, and in > op mode only on request? > > Thanks so much. > Mohamed. > > -- > 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- “Twenty years from now you will be more disappointed by the things that you didn’t do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover.” – Mark Twain -- 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, Oct 6, 2010 at 4:33 PM, James Louis <jglouisjr@gmail.com> wrote:> you have to use --no-client on the command line when running puppetd. I''ve > set it up in my /etc/sysconfig/puppet file on CentOS so it''s pulled in as > part of PUPPET_EXTRAOPTS. >Thanks a lot. That seems to work.... Now I know how to run puppetd in listen mode only, so I can cause changes via puppetrun when I need and can, only. My ideal config I am currently thinking is to be able to: Run puppetd in noop mode, every 30 minutes, so I get to know where a conifg needs to be applied. Then, when I am able to, depending on change control processes and change window times.... I then perform a remote run. One that is not noop. Do I need to script all this myself? or does some combination of puppet command line options provide this already? Thanks a lot. Mohamed. -- 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.
I think I got it... - Run puppetd with --no-client and listen mode. Activate changes by calling puppetrun - From cron, run puppetd --noop on regular basis to report on the config. Would this be proper configuration or would it be an unsupported hack ? Thanks a lot. Mohamed. -- 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.
that sounds like how I would set it up On Wed, Oct 6, 2010 at 4:42 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote:> I think I got it... > > - Run puppetd with --no-client and listen mode. Activate changes by > calling puppetrun > - From cron, run puppetd --noop on regular basis to report on the config. > > Would this be proper configuration or would it be an unsupported hack ? > > Thanks a lot. > Mohamed. > > -- > 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- “Twenty years from now you will be more disappointed by the things that you didn’t do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover.” – Mark Twain -- 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, Oct 6, 2010 at 6:33 PM, James Louis <jglouisjr@gmail.com> wrote:> that sounds like how I would set it up >One little problem though.... It I try to run puppetd from command line (and I assume from cron) with --onetime and --noop, while the listner is running, I get this: # puppetd --noop --test notice: Ignoring --listen on onetime run info: Caching catalog for chapeau.uis.georgetown.edu info: Applying configuration version ''1286391176'' notice: Finished catalog run in 8.16 seconds If I run the same with --test, it works fine... I could just use --test as a work around, and ignore stdout.. but what would be the right way? Thanks, -- 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.
The error when run without --test is: # puppetd --noop --onetime Could not prepare for execution: Could not create PID file: /var/lib/puppet/run/puppetd.pid On Wed, Oct 6, 2010 at 6:40 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote:> On Wed, Oct 6, 2010 at 6:33 PM, James Louis <jglouisjr@gmail.com> wrote: >> that sounds like how I would set it up >> > > One little problem though.... It I try to run puppetd from command > line (and I assume from cron) with --onetime and --noop, while the > listner is running, I get this: > > # puppetd --noop --test > notice: Ignoring --listen on onetime run > info: Caching catalog for chapeau.uis.georgetown.edu > info: Applying configuration version ''1286391176'' > notice: Finished catalog run in 8.16 seconds > > If I run the same with --test, it works fine... > > I could just use --test as a work around, and ignore stdout.. but what > would be the right way? > > Thanks, >-- " Logic merely sanctions the conquests of the intuition." Jacques Hadamard -- 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.
sounds like you have puppetd already running On Wed, Oct 6, 2010 at 5:42 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote:> The error when run without --test is: > > # puppetd --noop --onetime > Could not prepare for execution: Could not create PID file: > /var/lib/puppet/run/puppetd.pid > > > > On Wed, Oct 6, 2010 at 6:40 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote: > > On Wed, Oct 6, 2010 at 6:33 PM, James Louis <jglouisjr@gmail.com> wrote: > >> that sounds like how I would set it up > >> > > > > One little problem though.... It I try to run puppetd from command > > line (and I assume from cron) with --onetime and --noop, while the > > listner is running, I get this: > > > > # puppetd --noop --test > > notice: Ignoring --listen on onetime run > > info: Caching catalog for chapeau.uis.georgetown.edu > > info: Applying configuration version ''1286391176'' > > notice: Finished catalog run in 8.16 seconds > > > > If I run the same with --test, it works fine... > > > > I could just use --test as a work around, and ignore stdout.. but what > > would be the right way? > > > > Thanks, > > > > > > -- > " Logic merely sanctions the conquests of the intuition." > Jacques Hadamard > > -- > 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- “Twenty years from now you will be more disappointed by the things that you didn’t do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover.” – Mark Twain -- 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, Oct 6, 2010 at 7:07 PM, James Louis <jglouisjr@gmail.com> wrote:> sounds like you have puppetd already runningThat''s right. I am trying to see if I can run puppetd in listen mode, permanently. AND, from shell/cron, run puppetd --noop. Goal: - Receive constant reports about what needs to run (from the noop puppetd) - Be able to run a one time "do it now" through the listen-only puppetd. Thanks, Mohamed. -- 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.
if an instance of puppetd is already running then you''ll get that error message when you try to start up another instance. also there may be a puppetd.pid left from the last time it was ran. you would then have to remove that pid file. On Wed, Oct 6, 2010 at 6:16 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote:> On Wed, Oct 6, 2010 at 7:07 PM, James Louis <jglouisjr@gmail.com> wrote: > > sounds like you have puppetd already running > > That''s right. I am trying to see if I can run puppetd in listen mode, > permanently. AND, from shell/cron, run puppetd --noop. > > Goal: > - Receive constant reports about what needs to run (from the noop puppetd) > - Be able to run a one time "do it now" through the listen-only puppetd. > > Thanks, > Mohamed. > > -- > 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- “Twenty years from now you will be more disappointed by the things that you didn’t do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover.” – Mark Twain -- 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, Oct 6, 2010 at 7:33 PM, James Louis <jglouisjr@gmail.com> wrote:> if an instance of puppetd is already running then you''ll get that error > message when you try to start up another instance. also there may be a > puppetd.pid left from the last time it was ran. you would then have to > remove that pid file. >Thanks James. I understand. My question is that with --test option, the second puppetd seems to work fine... Is it? Should I just use --test option to run this second puppetd, or is there a better way? Thanks. Mohamed.> On Wed, Oct 6, 2010 at 6:16 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote: >> >> On Wed, Oct 6, 2010 at 7:07 PM, James Louis <jglouisjr@gmail.com> wrote: >> > sounds like you have puppetd already running >> >> That''s right. I am trying to see if I can run puppetd in listen mode, >> permanently. AND, from shell/cron, run puppetd --noop. >> >> Goal: >> - Receive constant reports about what needs to run (from the noop puppetd) >> - Be able to run a one time "do it now" through the listen-only puppetd. >> >> Thanks, >> Mohamed. >> >> -- >> 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. >> > > > > -- > “Twenty years from now you will be more disappointed by the things that you > didn’t do than by the ones you did do. So throw off the bowlines. Sail away > from the safe harbor. Catch the trade winds in your sails. Explore. Dream. > Discover.” > – Mark Twain > > -- > 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. >-- " Logic merely sanctions the conquests of the intuition." Jacques Hadamard -- 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.
all I know is you should probably only run one instance at a time. I''m kinda of a noob at this too so I hope I''ve been helpful. On Wed, Oct 6, 2010 at 7:20 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote:> On Wed, Oct 6, 2010 at 7:33 PM, James Louis <jglouisjr@gmail.com> wrote: > > if an instance of puppetd is already running then you''ll get that error > > message when you try to start up another instance. also there may be a > > puppetd.pid left from the last time it was ran. you would then have to > > remove that pid file. > > > > Thanks James. I understand. > My question is that with --test option, the second puppetd seems to > work fine... Is it? > Should I just use --test option to run this second puppetd, or is > there a better way? > > Thanks. > Mohamed. > > > On Wed, Oct 6, 2010 at 6:16 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote: > >> > >> On Wed, Oct 6, 2010 at 7:07 PM, James Louis <jglouisjr@gmail.com> > wrote: > >> > sounds like you have puppetd already running > >> > >> That''s right. I am trying to see if I can run puppetd in listen mode, > >> permanently. AND, from shell/cron, run puppetd --noop. > >> > >> Goal: > >> - Receive constant reports about what needs to run (from the noop > puppetd) > >> - Be able to run a one time "do it now" through the listen-only puppetd. > >> > >> Thanks, > >> Mohamed. > >> > >> -- > >> 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > >> For more options, visit this group at > >> http://groups.google.com/group/puppet-users?hl=en. > >> > > > > > > > > -- > > “Twenty years from now you will be more disappointed by the things that > you > > didn’t do than by the ones you did do. So throw off the bowlines. Sail > away > > from the safe harbor. Catch the trade winds in your sails. Explore. > Dream. > > Discover.” > > – Mark Twain > > > > -- > > 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > > For more options, visit this group at > > http://groups.google.com/group/puppet-users?hl=en. > > > > > > -- > " Logic merely sanctions the conquests of the intuition." > Jacques Hadamard > > -- > 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- “Twenty years from now you will be more disappointed by the things that you didn’t do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover.” – Mark Twain -- 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 Oct 6, 2010, at 5:20 PM, Mohamed Lrhazi wrote:> On Wed, Oct 6, 2010 at 7:33 PM, James Louis <jglouisjr@gmail.com> wrote: >> if an instance of puppetd is already running then you''ll get that error >> message when you try to start up another instance. also there may be a >> puppetd.pid left from the last time it was ran. you would then have to >> remove that pid file. >> > > Thanks James. I understand. > My question is that with --test option, the second puppetd seems to > work fine... Is it? > Should I just use --test option to run this second puppetd, or is > there a better way?I''m guessing that it will work if you run it with the -no-deamonize option. You really don''t want to use --test. That will have other effects.> Thanks. > Mohamed. > >> On Wed, Oct 6, 2010 at 6:16 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote: >>> >>> On Wed, Oct 6, 2010 at 7:07 PM, James Louis <jglouisjr@gmail.com> wrote: >>>> sounds like you have puppetd already running >>> >>> That''s right. I am trying to see if I can run puppetd in listen mode, >>> permanently. AND, from shell/cron, run puppetd --noop. >>> >>> Goal: >>> - Receive constant reports about what needs to run (from the noop puppetd) >>> - Be able to run a one time "do it now" through the listen-only puppetd. >>> >>> Thanks, >>> Mohamed. >>> >>> -- >>> 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. >>> >> >> >> >> -- >> “Twenty years from now you will be more disappointed by the things that you >> didn’t do than by the ones you did do. So throw off the bowlines. Sail away >> from the safe harbor. Catch the trade winds in your sails. Explore. Dream. >> Discover.” >> – Mark Twain >> >> -- >> 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. >> > > > > -- > " Logic merely sanctions the conquests of the intuition." > Jacques Hadamard > > -- > 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.
On 10/07/2010 04:48 AM, Patrick wrote:> > On Oct 6, 2010, at 5:20 PM, Mohamed Lrhazi wrote: > >> On Wed, Oct 6, 2010 at 7:33 PM, James Louis <jglouisjr@gmail.com> wrote: >>> if an instance of puppetd is already running then you''ll get that error >>> message when you try to start up another instance. also there may be a >>> puppetd.pid left from the last time it was ran. you would then have to >>> remove that pid file. >>> >> >> Thanks James. I understand. >> My question is that with --test option, the second puppetd seems to >> work fine... Is it? >> Should I just use --test option to run this second puppetd, or is >> there a better way? > > I''m guessing that it will work if you run it with the -no-deamonize option. > > You really don''t want to use --test. That will have other effects.Patrick, could you elaborate on that? Because --test is what we are using constantly here. I believe it''s a tip from "Pulling strings with puppet". From what I gathered, it''s the standard way to enforce a run while puppet is also running in daemon mode, which is quite exactly what Mohammed needs. So what are the catches to be wary of? Thanks in advance, Felix -- 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 Oct 7, 2010, at 12:40 AM, Felix Frank wrote:> On 10/07/2010 04:48 AM, Patrick wrote: >> >> On Oct 6, 2010, at 5:20 PM, Mohamed Lrhazi wrote: >> >>> On Wed, Oct 6, 2010 at 7:33 PM, James Louis <jglouisjr@gmail.com> wrote: >>>> if an instance of puppetd is already running then you''ll get that error >>>> message when you try to start up another instance. also there may be a >>>> puppetd.pid left from the last time it was ran. you would then have to >>>> remove that pid file. >>>> >>> >>> Thanks James. I understand. >>> My question is that with --test option, the second puppetd seems to >>> work fine... Is it? >>> Should I just use --test option to run this second puppetd, or is >>> there a better way? >> >> I''m guessing that it will work if you run it with the -no-deamonize option. >> >> You really don''t want to use --test. That will have other effects. > > Patrick, > > could you elaborate on that? > > Because --test is what we are using constantly here. I believe it''s a > tip from "Pulling strings with puppet". > > From what I gathered, it''s the standard way to enforce a run while > puppet is also running in daemon mode, which is quite exactly what > Mohammed needs. > > So what are the catches to be wary of?Last I checked, you were''s supposed to use --test for something non-interactive so --test might change. That means it''s safer to just list off the options that --test sets. The ones I remember that it sets are: --verbose --onetime --no-daemonize Something like, "Don''t use cached catalog on compile failure" I think there''s something that affects how long is should wait for a cert. Anyway, I think that "--verbose --onetime --no-daemonize" is all people usually want. Using --test still won''t force a puppet run if the service is also applying a run at the same time. It just allows you to run two copies of puppetd at the same time. The reason why you can is the --no-daemonize flag, so it''s usually safer to just list which flags you wanted from --test instead of using --test. -- 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.
----- Original Message -----> From: "Felix Frank" <felix.frank@alumni.tu-berlin.de> > To: puppet-users@googlegroups.com > Sent: Thursday, October 7, 2010 3:40:01 AM > Subject: Re: [Puppet Users] puppet push mode > On 10/07/2010 04:48 AM, Patrick wrote:> > I''m guessing that it will work if you run it with the -no-deamonize > > option. > > > > You really don''t want to use --test. That will have other effects. > > Patrick, > > could you elaborate on that?From the 2.6.1 man page: test: Enable the most common options used for testing. These are +onetime+, +verbose+, +ignorecache, +no-daemonize+, and +no-usecacheonfailure+.> > Because --test is what we are using constantly here. I believe it''s a > tip from "Pulling strings with puppet". > > From what I gathered, it''s the standard way to enforce a run while > puppet is also running in daemon mode, which is quite exactly what > Mohammed needs. > > So what are the catches to be wary of?I would be wary of ignoring your catalog cache. Deploying this throughout the environment would be detrimental to performance. The individual flags are a better way to go. -- 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.
>>> I''m guessing that it will work if you run it with the -no-deamonize >>> option. >>> >>> You really don''t want to use --test. That will have other effects. >> >> Patrick, >> >> could you elaborate on that? > > From the 2.6.1 man page: > > test: Enable the most common options used for testing. > These are +onetime+, +verbose+, +ignorecache, > +no-daemonize+, and +no-usecacheonfailure+. > > >> >> Because --test is what we are using constantly here. I believe it''s a >> tip from "Pulling strings with puppet". >> >> From what I gathered, it''s the standard way to enforce a run while >> puppet is also running in daemon mode, which is quite exactly what >> Mohammed needs. >> >> So what are the catches to be wary of? > > I would be wary of ignoring your catalog cache. Deploying this throughout the environment would be detrimental to performance. The individual flags are a better way to go. >Ah, misundersting. It is not used for general management. That is done by a plain old daemon process. When a newly changed manifest needs immediate running (e.g. when building a new manifest for a machine or changing something), that is when --test is used here. In such cases, you don''t care about the cache, because when the manifest cannot be parsed or the catalogue contains errors, you don''t want to apply the original catalogue. You only care to find the source of the errors. Since you put it that way, I think it will be safe for us to stick with --test. Even if the implied options will change, it will still be for testing, which is essentially what I (and Mohamed, I think) am looking for. Thanks, Felix -- 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.
> > From the 2.6.1 man page: > > > > test: Enable the most common options used for testing. > > These are +onetime+, +verbose+, +ignorecache, > > +no-daemonize+, and +no-usecacheonfailure+. > > > > > >> > >> Because --test is what we are using constantly here. I believe it''s > >> a > >> tip from "Pulling strings with puppet". > >> > >> From what I gathered, it''s the standard way to enforce a run while > >> puppet is also running in daemon mode, which is quite exactly what > >> Mohammed needs. > >> > >> So what are the catches to be wary of? > > > > I would be wary of ignoring your catalog cache. Deploying this > > throughout the environment would be detrimental to performance. The > > individual flags are a better way to go. > > > > Ah, misundersting. > > It is not used for general management. That is done by a plain old > daemon process. > > When a newly changed manifest needs immediate running (e.g. when > building a new manifest for a machine or changing something), that is > when --test is used here. > In such cases, you don''t care about the cache, because when the > manifest > cannot be parsed or the catalogue contains errors, you don''t want to > apply the original catalogue. You only care to find the source of the > errors. > > Since you put it that way, I think it will be safe for us to stick > with > --test. Even if the implied options will change, it will still be for > testing, which is essentially what I (and Mohamed, I think) am looking > for.Ah, Sorry, I''m with you now. That makes sense and is similar to how I operate. FWIW, I''m interested in what you and Mohamed are too. Until we get the trust buy-in for Puppet throughout the environment, being able to have regular reports come in about what''s out of sync and be able to kick off changes from the puppet master is ideal. --Ryan> > Thanks, > Felix >-- 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.
Am thinking about configrung my clients this way:
1: Daemonized puppet runs from init.d script as normal with this:
[root@chapeau ~]# cat /etc/sysconfig/puppet
...
PUPPET_EXTRA_OPTS=--no-client
...
[root@chapeau ~]# cat /etc/puppet/puppet.conf
[puppetd]
report = true
listen = true
2: A cron job, scheduled for every 30 minutes runs to report changes
only, like this:
/usr/sbin/puppetd --noop --onetime --no-daemonize > /dev/null 2>&1
&
I hope I understood everyone''s input here...
Thanks,
Mohamed.
On Thu, Oct 7, 2010 at 11:44 AM, Ryan Y. Coleman <dudeinpa@gmail.com>
wrote:>
>
>> > From the 2.6.1 man page:
>> >
>> > test: Enable the most common options used for testing.
>> > These are +onetime+, +verbose+, +ignorecache,
>> > +no-daemonize+, and +no-usecacheonfailure+.
>> >
>> >
>> >>
>> >> Because --test is what we are using constantly here. I believe
it''s
>> >> a
>> >> tip from "Pulling strings with puppet".
>> >>
>> >> From what I gathered, it''s the standard way to
enforce a run while
>> >> puppet is also running in daemon mode, which is quite exactly
what
>> >> Mohammed needs.
>> >>
>> >> So what are the catches to be wary of?
>> >
>> > I would be wary of ignoring your catalog cache. Deploying this
>> > throughout the environment would be detrimental to performance.
The
>> > individual flags are a better way to go.
>> >
>>
>> Ah, misundersting.
>>
>> It is not used for general management. That is done by a plain old
>> daemon process.
>>
>> When a newly changed manifest needs immediate running (e.g. when
>> building a new manifest for a machine or changing something), that is
>> when --test is used here.
>> In such cases, you don''t care about the cache, because when
the
>> manifest
>> cannot be parsed or the catalogue contains errors, you don''t
want to
>> apply the original catalogue. You only care to find the source of the
>> errors.
>>
>> Since you put it that way, I think it will be safe for us to stick
>> with
>> --test. Even if the implied options will change, it will still be for
>> testing, which is essentially what I (and Mohamed, I think) am looking
>> for.
>
> Ah, Sorry, I''m with you now. That makes sense and is similar to
how I operate.
>
> FWIW, I''m interested in what you and Mohamed are too. Until we get
the trust buy-in for Puppet throughout the environment, being able to have
regular reports come in about what''s out of sync and be able to kick
off changes from the puppet master is ideal.
>
> --Ryan
>
>>
>> Thanks,
>> Felix
>>
>
> --
> 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.
>
>
--
" Logic merely sanctions the conquests of the intuition."
Jacques Hadamard
--
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 10/07/2010 09:01 PM, Mohamed Lrhazi wrote:> Am thinking about configrung my clients this way: > > 1: Daemonized puppet runs from init.d script as normal with this: > > [root@chapeau ~]# cat /etc/sysconfig/puppet > ... > PUPPET_EXTRA_OPTS=--no-client > ... > > [root@chapeau ~]# cat /etc/puppet/puppet.conf > [puppetd] > report = true > listen = true > > 2: A cron job, scheduled for every 30 minutes runs to report changes > only, like this: > /usr/sbin/puppetd --noop --onetime --no-daemonize > /dev/null 2>&1 & > > I hope I understood everyone''s input here...Looks good to me. And it''s an interesting sort of setup. Probably not what the designers had in mind, but quite possible and rather elegant I think. Cheers, Felix -- 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.