Hi all, I keep doing my own scalability test. Trying to run puppet in all nodes at once. I''ve started with a fresh puppet+mongrel install (4 cpus, 4 puppetmasterd). I decided to start with a simple test, copying 1MB file to 188 nodes. No node type/group. It worked really fine. Now I''m trying with new test, 100files, one rpm install and 1 service stop. No node type/group. Worked fine. Next test is my prod conf. I has many classes, some definition, host group, dependencies, etc... And here puppet crashes... So I''d like to simplify my conf, and I''m wondering how puppet evaluates a node conf, so maybe I could reduce its complexity... For example, user/group creation, I rarely add users, so I could disable that class in a dynamic way? maybe adding some condition? or adding a condition will overload puppet server? or packages, i have about 50 sepaarte packages, If I define a var with all packages, will the load down? Any tips will be appreciate, Cheers, Arnau --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Hi all, More test.... I had a class which creates 250 users, If I comment it, puppet is able to run in 188 nodes at once with no problem. so, definitely, scalability issues comes from code. anyway, if someone could give me some tips on the OT will be appreciate. Cheers, Arnau --~--~---------~--~----~------------~-------~--~----~ 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-Jun-12 10:34 UTC
[Puppet Users] Re: trying to understand puppet internal
Arnau Bria schrieb:> Hi all, > > More test.... > > I had a class which creates 250 users, If I comment it, puppet is able > to run in 188 nodes at once with no problem. > so, definitely, scalability issues comes from code. > > anyway, if someone could give me some tips on the OT will be appreciate.Compiling the manifest is the single most resource-intensive operation the puppetmaster has to do. Therefore it is not recommended to have all clients hit the server at the same time. A more realistic measurement would be to use splay and see how far you can reduce the runinterval. That way you can spread out the load and still get fast turn-around times. For maximum performance you want to avoid any file-server operations (file.source with puppet://, filebucket to server}, set the catalog_format to marshal on the client, don''t use reports, don''t use storeconfigs and use the most recent available version of puppet (0.24.8 or even the 0.25 beta). Regards, DavidS -- dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at Klosterneuburg UID: ATU64260999 FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg --~--~---------~--~----~------------~-------~--~----~ 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 Fri, 12 Jun 2009 12:34:25 +0200 David Schmitt wrote: Hi David,> Compiling the manifest is the single most resource-intensive > operation the puppetmaster has to do.Yep, I noticed that.> Therefore it is not recommended to have all clients hit the server at > the same time.I know, but we''re trying to see if we can use puppet for immediate changes (I know puppet is not designed for that, for we''d like to test it).> A more realistic measurement would be to use splay and > see how far you can reduce the runinterval. That way you can spread > out the load and still get fast turn-around times.I do use splay.> For maximum performance you want to avoid any file-server operations > (file.source with puppet://, filebucket to server},I was thinking on implement an rsync in same puppet server and do a rsync Exec...> set the catalog_format to marshal on the client,what diff are there between marshal and yaml? I mean, do I lose information? reports ?> don''t use reports,Wow... I use Gridview and we really like it... but maybe we could live without it and adding some nagios sensors.> don''t use storeconfigs and use the most recent available version of > puppet (0.24.8 or even the 0.25 beta).I''m on 0.24.8. Any tips on coding?> Regards, DavidSMany thanks for your reply David. Cheers, Arnau --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
James Turnbull
2009-Jun-12 11:02 UTC
[Puppet Users] Re: trying to understand puppet internal
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Arnau Bria wrote: >> For maximum performance you want to avoid any file-server operations>> (file.source with puppet://, filebucket to server}, > I was thinking on implement an rsync in same puppet server and do a > rsync Exec...That''ll work.>> set the catalog_format to marshal on the client, > what diff are there between marshal and yaml? I mean, do I lose > information? reports ? >It''s all internal - you won''t see any external differences and you lose no data or reports.>> don''t use reports, > Wow... I use Gridview and we really like it... but maybe we could live > without it and adding some nagios sensors.What''s GridView - is that a Puppet specific tool?>> don''t use storeconfigs and use the most recent available version of >> puppet (0.24.8 or even the 0.25 beta). > I''m on 0.24.8. >Give the 0.25.0beta1 a try (or HEAD). Regards James Turnbull - -- Author of: * Pro Linux Systems Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKMjWr9hTGvAxC30ARAgS/AJ0STsel9EbQ5esejMNNBWF6TNmrfgCgo8S/ cb3Y/sjVmfiMJ5DjffhHmDE=4LB8 -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ 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-Jun-12 11:07 UTC
[Puppet Users] Re: trying to understand puppet internal
Arnau Bria schrieb:>> Therefore it is not recommended to have all clients hit the server at >> the same time. > I know, but we''re trying to see if we can use puppet for immediate > changes (I know puppet is not designed for that, for we''d like to test > it).Use the method I described in my earlier message to find the "sweet" spot of your setup. Then you know (and can repeatedly measure) how long an "immediate" application of your change will take. Most likely you''ll be faster if you don''t hammer your puppetmaster by starting all clients at the same time.>> For maximum performance you want to avoid any file-server operations >> (file.source with puppet://, filebucket to server}, > I was thinking on implement an rsync in same puppet server and do a > rsync Exec...Or use NFS or a local checkout of some VCS.>> set the catalog_format to marshal on the client, > what diff are there between marshal and yaml? I mean, do I lose > information? reports ?AFAIK marshal is equivalent to yaml, only faster and not backwards compatible.>> don''t use reports, > Wow... I use Gridview and we really like it... but maybe we could live > without it and adding some nagios sensors.To send a report, another call to the server has to be done. That''s more work for the server. Regards, DavidS -- dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at Klosterneuburg UID: ATU64260999 FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg --~--~---------~--~----~------------~-------~--~----~ 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 Friday 12 June 2009 22:46:53 Arnau Bria wrote:> > For maximum performance you want to avoid any file-server operations > > (file.source with puppet://, filebucket to server}, > > I was thinking on implement an rsync in same puppet server and do a > rsync Exec...Can''t you have puppet:/// servers separate to the catalogue server? Would that help? -- Robin <robin@kallisti.net.nz> JabberID: <eythian@jabber.kallisti.net.nz> http://www.kallisti.net.nz/blog ||| http://identi.ca/eythian PGP Key 0xA99CEB6D = 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
James Turnbull
2009-Jun-12 11:28 UTC
[Puppet Users] Re: trying to understand puppet internal
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Robin Sheat wrote:> On Friday 12 June 2009 22:46:53 Arnau Bria wrote: >>> For maximum performance you want to avoid any file-server operations >>> (file.source with puppet://, filebucket to server}, >> I was thinking on implement an rsync in same puppet server and do a >> rsync Exec... > > Can''t you have puppet:/// servers separate to the catalogue server? Would that > help?Yes - see http://reductivelabs.com/trac/puppet/wiki/PuppetScalability Regards James Turnbull - -- Author of: * Pro Linux Systems Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKMjvJ9hTGvAxC30ARAnlCAJ9AT6AhAtwYmBYMuD/HtPLIo/hgJACeJyBK D07PpwBAQdZJk9D+sIFJvC0=3QeT -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ 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 Fri, 12 Jun 2009 21:02:03 +1000 James Turnbull wrote: [...]> >> don''t use reports, > > Wow... I use Gridview and we really like it... but maybe we could > > live without it and adding some nagios sensors. > > What''s GridView - is that a Puppet specific tool?sorry, PuppetView ... I work in Grid world and we have a monitor web called GridView... and yes, I had it open while writing last email.> > I''m on 0.24.8. > > > > Give the 0.25.0beta1 a try (or HEAD).On production? My real problem comes when I try to run puppet in ALL production hosts (~ 200), when I test new releases in few hosts I have no problems... But I''ll take a look and give it a simple try (now that I know how to run client agains diff servers with no conf change).> Regards > > James TurnbullThanks for your reply, Arnau --~--~---------~--~----~------------~-------~--~----~ 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 Fri, 12 Jun 2009 21:28:09 +1000 James Turnbull wrote:> > Can''t you have puppet:/// servers separate to the catalogue server? > > Would that help? > > Yes - see http://reductivelabs.com/trac/puppet/wiki/PuppetScalabilityFrom my tests I saw that filserver is not a problem but users module is. So I can copy 500 files (10MB) with no problem but I have to comment out users module. I don''t know where''s the limit on fileserver, but I did not hit it...> Regards > > James TurnbullCheers, Arnau --~--~---------~--~----~------------~-------~--~----~ 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-Jun-12 13:08 UTC
[Puppet Users] Re: trying to understand puppet internal
David Schmitt schrieb:> Arnau Bria schrieb: >>> Therefore it is not recommended to have all clients hit the server at >>> the same time. >> I know, but we''re trying to see if we can use puppet for immediate >> changes (I know puppet is not designed for that, for we''d like to test >> it). > > Use the method I described in my earlier message to find the "sweet" > spot of your setup. Then you know (and can repeatedly measure) how long > an "immediate" application of your change will take. > > Most likely you''ll be faster if you don''t hammer your puppetmaster by > starting all clients at the same time.You might also want to look into puppetrun''s --parallel option: parallel: How parallel to make the connections. Parallelization is provided by forking for each client to which to connect. The default is 1, meaning serial execution. Then you could test how high you can go on --parallel before your puppetmaster goes down. Regards, DavidS -- dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at Klosterneuburg UID: ATU64260999 FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg --~--~---------~--~----~------------~-------~--~----~ 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 Fri, 12 Jun 2009 13:07:25 +0200 David Schmitt wrote: [...]> > what diff are there between marshal and yaml? I mean, do I lose > > information? reports ? > > AFAIK marshal is equivalent to yaml, only faster and not backwards > compatible.will try.> >> don''t use reports, > > Wow... I use Gridview and we really like it... but maybe we could > > live without it and adding some nagios sensors. > > To send a report, another call to the server has to be done. That''s > more work for the server.Will see how works the server now and then evaluate if report is necessary or not.> Regards, DavidSMany thanks, Arnau --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Aurelien Degremont
2009-Jun-12 14:00 UTC
[Puppet Users] Re: trying to understand puppet internal
Hello David Schmitt wrote :> For maximum performance you want to avoid any file-server operations> (file.source with puppet://, filebucket to server}, set the I agree with you, mainly, fileserver is slow. But few tests I made using ''file://'' instead of ''puppet://'' didn''t speed up my puppet runs... I was quite surprised...> set the > catalog_format to marshal on the client,Good. Indeed, ''Config retrieval'' performance is better with this, but the catalog cache is stored in a binary format in /var/lib/puppet/localconfig.yaml (still named .yaml even if it is not in yaml anymore) But, my main concern is that we used the cache catalog to debug our puppet configuration. It is really useful when Puppet doesn''t setup thing as you expect, it helps understand which resources were setup and send to your client. With marshal format, the file is near from unreadable. Is there a way to workaround this? > don''t use reports, don''t use> storeconfigs and use the most recent available version of puppet (0.24.8 > or even the 0.25 beta).That''s a pity. I really would like to use this, but performance matters... Hope REST in pupet 0.25 will help a lot in this area... -- Aurelien Degremont --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Aurelien Degremont
2009-Jun-12 14:02 UTC
[Puppet Users] Re: trying to understand puppet internal
Arnau Bria a écrit :> Hi all, > > More test.... >If your doing benchmarking with puppet try: # puppetd -t --summarize Really helpful. -- Aurelien Degremont CEA --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
James Turnbull
2009-Jun-12 14:10 UTC
[Puppet Users] Re: trying to understand puppet internal
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Aurelien Degremont wrote:> Arnau Bria a écrit : >> Hi all, >> >> More test.... >> > > If your doing benchmarking with puppet > try: > > # puppetd -t --summarize >Also puppet-test in the ext directory is useful too. Regards James Turnbull - -- Author of: * Pro Linux Systems Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKMmHu9hTGvAxC30ARAh7JAJ9MI5tyPkctS4HB7F0S6xxNtIM7PwCeNIfK pQDgX0fA/A379ub0fUI5zoc=93GR -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Jean-Baptiste Quenot
2009-Jun-12 17:54 UTC
[Puppet Users] Re: trying to understand puppet internal
2009/6/12 Aurelien Degremont <aurelien.degremont@cea.fr>:> > Arnau Bria a écrit : >> Hi all, >> >> More test.... >> > > If your doing benchmarking with puppet > try: > > # puppetd -t --summarize > > Really helpful.Interesting. Any reason why this option is not documented in puppetd -h? I''m using 0.24.8 FWIW. Cheers, -- Jean-Baptiste Quenot http://jbq.caraldi.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 -~----------~----~----~----~------~----~------~--~---
Aurelien Degremont
2009-Jun-15 09:32 UTC
[Puppet Users] Re: trying to understand puppet internal
Jean-Baptiste Quenot a écrit :> 2009/6/12 Aurelien Degremont <aurelien.degremont@cea.fr>: >> Arnau Bria a écrit : >>> Hi all, >>> >>> More test.... >>> >> If your doing benchmarking with puppet >> try: >> >> # puppetd -t --summarize >> >> Really helpful. > > Interesting. Any reason why this option is not documented in puppetd > -h? I''m using 0.24.8 FWIW.Unfortunately, there is more than just this argument which is not implemented. Here is some of them: . centrallogging . no-splay . show_diff Those ones are visible in puppetd man page, but not explicit list in OPTIONS section: . no-usecacheonfailure . ignorecache . tags Mainly, all options, settable in puppet.conf configuration file are supported on command-line. You can see all of them here: /usr/lib/ruby/site_ruby/1.8/puppet/defaults.rb ''puppetmasted'' and ''puppet'' command also supports much more args it is explained in its help page. -- Aurelien Degremont --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
James Turnbull
2009-Jun-15 16:40 UTC
[Puppet Users] Re: trying to understand puppet internal
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Aurelien Degremont wrote: | Jean-Baptiste Quenot a écrit : |> 2009/6/12 Aurelien Degremont <aurelien.degremont@cea.fr>: |>> Arnau Bria a écrit : |>>> Hi all, |>>> |>>> More test.... |>>> |>> If your doing benchmarking with puppet |>> try: |>> |>> # puppetd -t --summarize |>> |>> Really helpful. |> Interesting. Any reason why this option is not documented in puppetd |> -h? I''m using 0.24.8 FWIW. | | Unfortunately, there is more than just this argument which is not | implemented. Here is some of them: | | . centrallogging | . no-splay | . show_diff | | Those ones are visible in puppetd man page, but not explicit list in | OPTIONS section: | | . no-usecacheonfailure | . ignorecache | . tags | | Mainly, all options, settable in puppet.conf configuration file are | supported on command-line. | You can see all of them here: | | /usr/lib/ruby/site_ruby/1.8/puppet/defaults.rb | | ''puppetmasted'' and ''puppet'' command also supports much more args it is | explained in its help page. See http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference Every Puppet executable (generally) accepts all configuration options but some are obviously not appropriate. For particular executables we try to document key options in the man page or --help output but not every possible option. If you think one or other option SHOULD be documented in there please free to suggest it or submit a patch. Thanks James Turnbull - -- Author of: * Pro Linux Systems Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKNnmX9hTGvAxC30ARAgAXAKCJws/H7Raz/I2Md/vOcFszghEgewCbB9HM RZVcR/tqyDtzl88CGf2yB6A=GTB7 -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ 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-Jun-17 09:50 UTC
[Puppet Users] Re: trying to understand puppet internal
James Turnbull wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Aurelien Degremont wrote: > | Jean-Baptiste Quenot a écrit : > |> 2009/6/12 Aurelien Degremont <aurelien.degremont@cea.fr>: > |>> Arnau Bria a écrit : > |>>> Hi all, > |>>> > |>>> More test.... > |>>> > |>> If your doing benchmarking with puppet > |>> try: > |>> > |>> # puppetd -t --summarize > |>> > |>> Really helpful. > |> Interesting. Any reason why this option is not documented in puppetd > |> -h? I''m using 0.24.8 FWIW. > | > | Unfortunately, there is more than just this argument which is not > | implemented. Here is some of them: > | > | . centrallogging > | . no-splay > | . show_diff > | > | Those ones are visible in puppetd man page, but not explicit list in > | OPTIONS section: > | > | . no-usecacheonfailure > | . ignorecache > | . tags > | > | Mainly, all options, settable in puppet.conf configuration file are > | supported on command-line. > | You can see all of them here: > | > | /usr/lib/ruby/site_ruby/1.8/puppet/defaults.rb > | > | ''puppetmasted'' and ''puppet'' command also supports much more args > it is > | explained in its help page. > > See http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference > > Every Puppet executable (generally) accepts all configuration > options but some are obviously not appropriate. For particular > executables we try to document key options in the man page or --help > output but not every possible option. > > If you think one or other option SHOULD be documented in there > please free to suggest it or submit a patch.Don''t forget that some parameters that are accepted by the programs are not configration options. An example would be puppetd''s --test. 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 -~----------~----~----~----~------~----~------~--~---