I created some manifest files, but my client doesn''t seem to be picking
them up. According to all of the tutorials, I''m doing this right, so
I''m
not sure what the issue is.
nodes.pp:
node default {
include ntp
}
ntp.pp:
class ntp {
package {
ntp:
ensure => installed
}
service {
ntpd:
ensure => running,
}
}
puppetd --test:
dnsdomainname: Unknown host
dnsdomainname: Unknown host
info: Caching catalog for testserver
info: Applying configuration version ''1346184997''
notice: Finished catalog run in 0.01 seconds
--
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.
Could you please link me to these tutorials, so I may destroy them. Okay, anyway, here''s how Puppet works: The master has ONE manifest file that it ALWAYS reads, called /etc/puppet/manifests/site.pp. (use puppet master --configprint manifest to confirm its location. You can set the ''manifest'' setting to change that.) It also OPTIONALLY can have an external node classifier; don''t worry about that right now. The main manifest and the ENC can declare classes. Puppet will AUTOLOAD classes from MODULES. See here: http://docs.puppetlabs.com/puppet/2.7/reference/modules_fundamentals.html If you use an IMPORT statement in site.pp, you can also load arbitrary files like nodes.pp or nodes/somethingelse.pp. See here: http://docs.puppetlabs.com/puppet/2.7/reference/lang_import.html But you don''t need to do this right now. So to get your simple thing working now: * rename nodes.pp to site.pp so puppet master will use it * move ntp.pp to /etc/puppet/modules/ntp/manifests/init.pp On Tuesday, August 28, 2012 1:19:23 PM UTC-7, Bai Shen wrote:> > I created some manifest files, but my client doesn''t seem to be picking > them up. According to all of the tutorials, I''m doing this right, so I''m > not sure what the issue is. > > nodes.pp: > node default { > include ntp > } > > > ntp.pp: > class ntp { > package { > ntp: > ensure => installed > } > > service { > ntpd: > ensure => running, > } > } > > > puppetd --test: > dnsdomainname: Unknown host > dnsdomainname: Unknown host > info: Caching catalog for testserver > info: Applying configuration version ''1346184997'' > notice: Finished catalog run in 0.01 seconds > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/ABbfMKE7JkgJ. 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, And see to that you get output while going for this command # dnsdomainname example.com Regards, System Admin Ashish Jaiswal On Wednesday 29 August 2012 04:25:23 AM IST, Nick Fagerlund wrote:> Could you please link me to these tutorials, so I may destroy them. > > Okay, anyway, here''s how Puppet works: > > The master has ONE manifest file that it ALWAYS reads, called > /etc/puppet/manifests/site.pp. (use puppet master --configprint > manifest to confirm its location. You can set the ''manifest'' setting > to change that.) It also OPTIONALLY can have an external node > classifier; don''t worry about that right now. > > The main manifest and the ENC can declare classes. Puppet will > AUTOLOAD classes from MODULES. See here: > http://docs.puppetlabs.com/puppet/2.7/reference/modules_fundamentals.html > > If you use an IMPORT statement in site.pp, you can also load arbitrary > files like nodes.pp or nodes/somethingelse.pp. See here: > http://docs.puppetlabs.com/puppet/2.7/reference/lang_import.html But > you don''t need to do this right now. > > So to get your simple thing working now: > > * rename nodes.pp to site.pp so puppet master will use it > * move ntp.pp to /etc/puppet/modules/ntp/manifests/init.pp > > On Tuesday, August 28, 2012 1:19:23 PM UTC-7, Bai Shen wrote: > > I created some manifest files, but my client doesn''t seem to be > picking them up. According to all of the tutorials, I''m doing > this right, so I''m not sure what the issue is. > > nodes.pp: > node default { > include ntp > } > > > ntp.pp: > class ntp { > package { > ntp: > ensure => installed > } > > service { > ntpd: > ensure => running, > } > } > > > puppetd --test: > dnsdomainname: Unknown host > dnsdomainname: Unknown host > info: Caching catalog for testserver > info: Applying configuration version ''1346184997'' > notice: Finished catalog run in 0.01 seconds > > -- > You received this message because you are subscribed to the Google > Groups "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/ABbfMKE7JkgJ. > 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.
Anatoliy Lisovskiy
2012-Aug-29 03:38 UTC
Re: [Puppet Users] Re: Puppet not picking up manifests
On Tue, Aug 28, 2012 at 3:55 PM, Nick Fagerlund < nick.fagerlund@puppetlabs.com> wrote:> Could you please link me to these tutorials, so I may destroy them. >It is easy to destroy incomplete tutorials, but harder to offer something good instead! When I started using Puppet it took long time until I suddenly found somewhere that the starting point is site.pp After that all went flawlessly. But this first step was very hard to understand. It would be nice to have a working scenario that describes basic details, how Puppet works, step by step, instead of long explanations of syntax, variables, and tricks with code optimization that are not needed to start running it. Anatoliy> > Okay, anyway, here''s how Puppet works: > > The master has ONE manifest file that it ALWAYS reads, called > /etc/puppet/manifests/site.pp. (use puppet master --configprint manifest to > confirm its location. You can set the ''manifest'' setting to change that.) > It also OPTIONALLY can have an external node classifier; don''t worry about > that right now. > > The main manifest and the ENC can declare classes. Puppet will AUTOLOAD > classes from MODULES. See here: > http://docs.puppetlabs.com/puppet/2.7/reference/modules_fundamentals.html > > If you use an IMPORT statement in site.pp, you can also load arbitrary > files like nodes.pp or nodes/somethingelse.pp. See here: > http://docs.puppetlabs.com/puppet/2.7/reference/lang_import.html But you > don''t need to do this right now. > > So to get your simple thing working now: > > * rename nodes.pp to site.pp so puppet master will use it > * move ntp.pp to /etc/puppet/modules/ntp/manifests/init.pp > > > On Tuesday, August 28, 2012 1:19:23 PM UTC-7, Bai Shen wrote: >> >> I created some manifest files, but my client doesn''t seem to be picking >> them up. According to all of the tutorials, I''m doing this right, so I''m >> not sure what the issue is. >> >> nodes.pp: >> node default { >> include ntp >> } >> >> >> ntp.pp: >> class ntp { >> package { >> ntp: >> ensure => installed >> } >> >> service { >> ntpd: >> ensure => running, >> } >> } >> >> >> puppetd --test: >> dnsdomainname: Unknown host >> dnsdomainname: Unknown host >> info: Caching catalog for testserver >> info: Applying configuration version ''1346184997'' >> notice: Finished catalog run in 0.01 seconds >> >> -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/ABbfMKE7JkgJ. > > 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 Tuesday, August 28, 2012 10:39:01 PM UTC-5, Anatoliy Lisovskiy (Wavebourn) wrote:> > > > On Tue, Aug 28, 2012 at 3:55 PM, Nick Fagerlund <nick.fa...@puppetlabs.com<javascript:> > > wrote: > >> Could you please link me to these tutorials, so I may destroy them. >> > > It is easy to destroy incomplete tutorials, but harder to offer something > good instead! > > When I started using Puppet it took long time until I suddenly found > somewhere that the starting point is site.pp > After that all went flawlessly. But this first step was very hard to > understand. It would be nice to have a working scenario that describes > basic details, how Puppet works, step by step, instead of long explanations > of syntax, variables, and tricks with code optimization that are not needed > to start running it. >I have always found PuppetLabs''s Puppet Language Guide to be a great resource. It was easy to find on PL''s (then called "Reductive Labs") web site when I first started with Puppet about three years ago, and it still is. It covers this point, among many others. There are also some good books about Puppet available. Additionally, there are a number of third-party tutorials spread around the web, of varying quality and thoroughness. Is there something else specific that you would have liked to see? John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/rjHuDUJ3UucJ. 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.
This is the tutorial I was using. http://bitfieldconsulting.com/puppet-tutorial Once I changed nodes.pp to site.pp Puppet saw it. Now I just have to change the rest of the manifests. Thanks. On Tue, Aug 28, 2012 at 6:55 PM, Nick Fagerlund < nick.fagerlund@puppetlabs.com> wrote:> Could you please link me to these tutorials, so I may destroy them. > > Okay, anyway, here''s how Puppet works: > > The master has ONE manifest file that it ALWAYS reads, called > /etc/puppet/manifests/site.pp. (use puppet master --configprint manifest to > confirm its location. You can set the ''manifest'' setting to change that.) > It also OPTIONALLY can have an external node classifier; don''t worry about > that right now. > > The main manifest and the ENC can declare classes. Puppet will AUTOLOAD > classes from MODULES. See here: > http://docs.puppetlabs.com/puppet/2.7/reference/modules_fundamentals.html > > If you use an IMPORT statement in site.pp, you can also load arbitrary > files like nodes.pp or nodes/somethingelse.pp. See here: > http://docs.puppetlabs.com/puppet/2.7/reference/lang_import.html But you > don''t need to do this right now. > > So to get your simple thing working now: > > * rename nodes.pp to site.pp so puppet master will use it > * move ntp.pp to /etc/puppet/modules/ntp/manifests/init.pp > > > On Tuesday, August 28, 2012 1:19:23 PM UTC-7, Bai Shen wrote: >> >> I created some manifest files, but my client doesn''t seem to be picking >> them up. According to all of the tutorials, I''m doing this right, so I''m >> not sure what the issue is. >> >> nodes.pp: >> node default { >> include ntp >> } >> >> >> ntp.pp: >> class ntp { >> package { >> ntp: >> ensure => installed >> } >> >> service { >> ntpd: >> ensure => running, >> } >> } >> >> >> puppetd --test: >> dnsdomainname: Unknown host >> dnsdomainname: Unknown host >> info: Caching catalog for testserver >> info: Applying configuration version ''1346184997'' >> notice: Finished catalog run in 0.01 seconds >> >> -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/ABbfMKE7JkgJ. > 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.
Eric Sorenson
2012-Aug-30 23:21 UTC
Re: [Puppet Users] Re: Puppet not picking up manifests
I''ll mail John Arundel (don''t think he is active on this list) and ask him to fix this -- from the comments on that page there''s at least one more problem with the tutorial as written. On Wednesday, August 29, 2012 8:09:13 AM UTC-7, Bai Shen wrote:> > This is the tutorial I was using. > > http://bitfieldconsulting.com/puppet-tutorial > > Once I changed nodes.pp to site.pp Puppet saw it. Now I just have to > change the rest of the manifests. > > Thanks. > > On Tue, Aug 28, 2012 at 6:55 PM, Nick Fagerlund <nick.fa...@puppetlabs.com<javascript:> > > wrote: > >> Could you please link me to these tutorials, so I may destroy them. >> >> Okay, anyway, here''s how Puppet works: >> >> The master has ONE manifest file that it ALWAYS reads, called >> /etc/puppet/manifests/site.pp. (use puppet master --configprint manifest to >> confirm its location. You can set the ''manifest'' setting to change that.) >> It also OPTIONALLY can have an external node classifier; don''t worry about >> that right now. >> >> The main manifest and the ENC can declare classes. Puppet will AUTOLOAD >> classes from MODULES. See here: >> http://docs.puppetlabs.com/puppet/2.7/reference/modules_fundamentals.html >> >> If you use an IMPORT statement in site.pp, you can also load arbitrary >> files like nodes.pp or nodes/somethingelse.pp. See here: >> http://docs.puppetlabs.com/puppet/2.7/reference/lang_import.html But you >> don''t need to do this right now. >> >> So to get your simple thing working now: >> >> * rename nodes.pp to site.pp so puppet master will use it >> * move ntp.pp to /etc/puppet/modules/ntp/manifests/init.pp >> >> >> On Tuesday, August 28, 2012 1:19:23 PM UTC-7, Bai Shen wrote: >>> >>> I created some manifest files, but my client doesn''t seem to be picking >>> them up. According to all of the tutorials, I''m doing this right, so I''m >>> not sure what the issue is. >>> >>> nodes.pp: >>> node default { >>> include ntp >>> } >>> >>> >>> ntp.pp: >>> class ntp { >>> package { >>> ntp: >>> ensure => installed >>> } >>> >>> service { >>> ntpd: >>> ensure => running, >>> } >>> } >>> >>> >>> puppetd --test: >>> dnsdomainname: Unknown host >>> dnsdomainname: Unknown host >>> info: Caching catalog for testserver >>> info: Applying configuration version ''1346184997'' >>> notice: Finished catalog run in 0.01 seconds >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/puppet-users/-/ABbfMKE7JkgJ. >> To post to this group, send email to puppet...@googlegroups.com<javascript:> >> . >> To unsubscribe from this group, send email to >> puppet-users...@googlegroups.com <javascript:>. >> 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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/NrNDev-mdHIJ. 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.