Dan, yes I know I could do that, and in fact that's what I was doing (that is, simply do a puppet /path/to/manifest-that-could-just-be-site.pp) but yes, that article and occurrences elsewhere misled me. Appreciate your help, I am just trying to learn. Thanks and apologies for being a bit presumptuous.
Cheers. On Tue, Aug 17, 2010 at 10:29 PM, Dan Bode <d...@puppetlabs.com> wrote: > Hi, > > On Tue, Aug 17, 2010 at 9:50 AM, mohit chawla < > mohit.chawla.bin...@gmail.com> wrote: > >> I am sure I didn't make this up, but I was under the impression that >> either it will autoload the default site.pp (under /etc/puppet/manifests) or >> the one mentioned with the --manifest option. So, essentially I thought just >> the modulepath option (with or without the explicit --manifest option) would >> be sufficient in either case. >> > > you can achieve this functionality by running > > #>puppet /etc/puppet/manifests/site.pp > > only the puppet server (puppetmasterd) uses manifest/manifestdir to > automatically find site.pp > > >> I was mainly trying out alternative deployment approaches apart from the >> client/server arch that I have been using. Mainly inspired by this article: >> http://bitfieldconsulting.com/scaling-puppet-with-distributed-version-control >> > > I had a look at that article, it is slightly misleading. I think the > examples are trying to highlight that you can specify modulepath with the > puppet executalbe, but the statements: > > puppet --modulepath=/etc/puppet/modules > > are not valid, they will just hang unless the puppet manifest is also > passed as an argument. > > > >> >> Didn't think asking this would be so offensive. >> > > I am definitely not offend, and I don't mean to offend, just trying to > help. > > >> >> On Tue, Aug 17, 2010 at 12:10 PM, Dan Bode <d...@puppetlabs.com> wrote: >> >>> the puppet executable expects one of the following: >>> path to manifest file >>> puppet code passed to stdin >>> with the -e options, it accepts puppet code to execute. >>> >>> when you call puppet code without one of these options, it is patiently >>> waiting for code from STDIN. >>> >>> What behavior are you expecting? Maybe you should look into the >>> puppetmasterd/puppetd executables. >>> >>> -Dan >>> >>> On Mon, Aug 16, 2010 at 11:17 PM, mohit chawla < >>> mohit.chawla.bin...@gmail.com> wrote: >>> >>>> Puppet version is 0.25.5 on Debian Squeeze. >>>> >>>> >>>> On Tue, Aug 17, 2010 at 11:43 AM, alcy >>>> <mohit.chawla.bin...@gmail.com>wrote: >>>> >>>>> If I do >>>>> >>>>> 1) puppet --modulepath=/home/abc/puppet/modules >>>>> >>>>> OR >>>>> >>>>> 2) puppet --modulepath=/home/abc/puppet/modules --manifest=/home/abc/ >>>>> puppet/site.pp >>>>> >>>>> (...where site.pp has import "nodes.pp", and nodes.pp has a default >>>>> node definition that includes basic modules defined under /home/abc/ >>>>> puppet/modules) >>>>> >>>>> OR >>>>> >>>>> 3) 2) with confdir set as /home/abc/puppet with a puppet.conf just >>>>> pointing to the var, ssl and other directories. >>>>> >>>>> , then I do not get any output (or anything in the logfile with the >>>>> logdest set) whatsoever even with trace, logdest, debug and verbose >>>>> options set. >>>>> >>>>> >>>>> If however I explicitly do >>>>> >>>>> 4) puppet -e node default { include xyz include pqr} --modulepath=/ >>>>> home/abc/puppet/modules >>>>> >>>>> ,then the modules are applied fine. >>>>> >>>>> Any pointers regarding this behavior of the standalone executable ? >>>>> Suggestions/tips for better understanding its working ? >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Puppet Users" group. >>>>> To post to this group, send email to puppet-us...@googlegroups.com. >>>>> To unsubscribe from this group, send email to >>>>> puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@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-us...@googlegroups.com. >>>> To unsubscribe from this group, send email to >>>> puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@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-us...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@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-us...@googlegroups.com. >> To unsubscribe from this group, send email to >> puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@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-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@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-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
