search for: node_terminus

All, For those that are using external nodes (as local files) and multiple environments, where do you put the external node files? Ie, do you put them down in the environment itself /etc/puppet/env/env1/manifests/extdata/nodes /etc/puppet/env/env.../manifests/extdata/nodes /etc/puppet/env/envN/manifests/extdata/nodes OR, up above the environments? /etc/puppet/manifests/extdata/nodes Which

...tc/puppet/environments/manifests/install/site.pp [agent] server = puppet report = true [master] ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY storeconfigs = true storeconfigs_backend = puppetdb reports=log,puppetdb,foreman external_nodes = /etc/puppet/node.rb node_terminus = exec* ----------------------------------------------------------- If i comment the last two lines (external_nodes and node_terminus) on the puppetmaster puppet.conf node, The puppet manifest is applied correctly. Anybody has an idea ? Thanks -- You received this message because you are su...

I am trying to configure puppet with LDAP repository . I have set puppet schema and I have also added node definition at LDAP. Here is my configuration details . ############################################################## Puppet.conf node_terminus = ldap ldapserver = 10.250.11.127 ldapbase = ou=Hosts,dc=xyz,dc=com ldapassword = secret ############################################################# Node details #################### # extended LDIF # # LDAPv3 # base <dc=xyz,dc=com> with scope sub # filter: (objectclass=*) # requesting...

...running 3.2.4 on the client and master both: Here''s what I''m trying: here''s my static node definition: *site.pp:* *node default {* * notify { "static node definition": }* * * *}* and my puppet.conf without any node definition: *puppet.conf* *[master]* * node_terminus = plain* works beautifully: *[root@vacsld01target ~]# /usr/bin/puppet agent --onetime --daemonize --verbose --test* *Info: Retrieving plugin* *<snip>* *Info: Caching catalog for vacsld01target.oss.central1.com* *Info: Applying configuration version ''1377125492''* *Notice:...

...for ["hola", {"mens"=>"HOLA"}]:Array on node casa I have a very simple parameter class : class hola( $mens = "HELLO" ) { notify{"puppet": message => "$mens"} } I''m setting puppet.conf in master section : node_terminus = exec external_nodes = /etc/puppet/tools/dummycp.sh My script dummycp.sh is : #!/bin/sh cat <<"END" --- classes: hola: mens: HOLA parameters: manager: Jane Doe END exit 0 I appreciate any help, thanks in advance, eduardo. -- You received this message because y...

...are controlled in the site.pp by node ''FQDN'' {blah} for the same puppetmaster ? I am wondering once parameters are set for the master to look for an ENC based definitions, will it conflict with the site.pp node definitions ? For example these two basic parameters for ENC : node_terminus = exec external_nodes = /usr/local/bin/enclassifier Thanks for any suggestion. ------ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsu...

...t into site.pp, it will retrieve the proper catalog / classes, but I would like to avoid having to do that. I''m also using environments (production/testing/ development) as well, but think I have most of this configured correctly - on the puppetmaster''s puppet.conf - I do have: node_terminus = exec external_nodes = /etc/puppetlabs/puppet/node.rb node.rb does exist and is owned by pe-puppet, executable, etc. I''ve verified I can view the yaml for a test client using the script. and I have stanzas for each environment in the master''s puppet.conf - [production] modulep...

I''m trying to setup dashboard as a node classifier w/puppet 2.6.14. Not sure why this is not working... In puppet.conf on the master I have: node_terminus = exec external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http:// localhost /usr/share/puppet-dashboard/bin/external_node The agent''s return: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find node ''myhost''; cannot compile I can...

...was matching nodes in my directory to determine what classes to apply. I upgraded to 0.25 and this stopped working. I do not even see attempts from the Puppetmaster to search the directory (i.e., no connections to the ldap server). I *did* update the puppetmasterd conf, adding the variable "node_terminus = ldap" since that apparently changed between versions. Here are all three entries: # LDAP Config node_terminus = ldap ldapserver = ldap.<some_domain>.com ldapbase = ou=nodes,dc=<domain>,dc=com Like I said, this was working great before. If it makes a difference, w...

.../Using_Multiple_Environments as my base. In my puppet.conf on puppetmaster I have cat /etc/puppet.conf [main] <snip> manifest = /etc/puppet/manifests/site.pp modulepath = /etc/puppet/modules [development] manifest = /etc/puppet_devel/manifests/site.pp modulepath = /etc/puppet_devel/modules node_terminus = exec external_nodes = /.foo/bin/puppet_node_classifier.sh In my head that tells the development area to use /etc/puppet_devel and to use the node classifier, whereas the main area uses /etc/ puppet/ and does NOT use the node classifier. My testing shows that if I run ''puppetd --test...

Hello All, I''m trying to start using external nodes under foreman, and I''m running into some issues. I have the entries in puppet.conf: [main] external_nodes = /etc/puppet/external_node.rb node_terminus = exec The enternal_node.rb script is the one that came with foreman: #!/usr/bin/ruby # a simple script which fetches external nodes from Foreman # you can basically use anything that knows how to get http data, e.g. wget/curl etc. # Foreman url foreman_url="https://hostname:443"...

I am trying to get a custom fact to sync. The fact is in a module. It will sync if I run puppet with "--pluginsync" but not otherwise. I have "pluginsync=true" in my puppet.conf. Shouldn''t the command line option and puppet.conf option have the same results? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group.

...################# This is my puppet.conf: [main] vardir = /var/lib/puppet logdir = /var/log/puppet rundir = /var/run/puppet reports= log,foreman,rrdgraph,store clientyamldir = /var/lib/puppet/yaml/node pluginsync = true external_nodes = /etc/puppet/external_node.rb node_terminus = exec [puppetmasterd] ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY modulepath = $confdir/modules templatedir = /etc/puppet/manifests/templates #clientyamldir = /var/lib/puppet/yaml/node reportdir = /var/lib/puppet/reports storeconfig...

...host2.example.net.example.com finished with exit code 2 Failed: host1.example.net.example.com, host2.example.net.example.com --- Maybe Puppetmaster was loaded "cn=host1.example.net" and "dc=example,dc=com". Puppetmaster and LDAP Server Config, puppet.conf --- [main] node_terminus = ldap ldapserver = 192.168.0.101 ldapport = 389 ldapbase = ou=Servers,dc=puppet,dc=sf ldapstring = (&(objectclass=puppetClient)(cn=%s)) ldapuser=cn=Manager,dc=example,dc=com ldappassword=******* --- host1.ldif --- dn: cn=host1.example.net, ou...

I want to deploy puppet with openldap for specific node configuration, but only for specific nodes, every other node (not in LDAP) should follow the ''default'' node definition. Is it possible to mix and match like this? As I try it I am getting err: Could not retrieve catalog: Could not find node ''myhostname'' instead. -- Mark Foster - Sr. Systems Engineer

...copy all Ruby code from all modules to your clients. Just enable ''pluginsync'' on the clients and your clients will get any custom types, providers, or facts before they start their configuration run. - Modifying how external node support works. You must now specify the node_terminus setting, which obsoletes the ldapnodes setting. You must use ''exec'' as the node_terminus if you are using external nodes, and you must still specify the path to the external nodes command in ''external_nodes''. See the wiki:IndirectionReference for more i...

...or servers (i.e., `puppet master`) this provides the default environment for nodes # we know nothing about. # The default value is ''production''. environment = pre # Where to find information about nodes. # The default value is ''plain''. # node_terminus = plain # Where the puppet agent web server logs. # The default value is ''$logdir/http.log''. httplog = <logpath>/http.log # Send the process into the background. This is the default. # The default value is ''true''. daemonize = true...

...= root fileserverconfig = /etc/puppet/fileserver.conf reportdir = /home/logs/puppet/reports masterhttplog = /home/logs/puppet/masterhttp.log masterlog = /home/logs/puppet/puppetmaster.log reports = log,foreman reports=foreman,log templatedir = /etc/puppet/templates node_terminus = exec external_nodes = /etc/puppet/puppet_node_classifier site.pp: #node default { # exec {"echo 123": # path => "/sbin:/usr/bin:/usr/sbin:/bin", # } #} #node /local-web-cdn-70-200.idc.test.cn/ { # include tools #} run script: [root@puppe...

...t;. I am using 3.1.1 What is the different of find and search? I have done a puppet clean node <node> and its seems to only partially have worked. A #find /var/lib/puppet -name ''<node>*'' , does not find any files A puppet node search ''*'' --node_terminus yaml --clientyamldir `puppet master --configprint yamldir` | | grep <node> again nothing, thougnthe search return all the nodes but a puppet node find <node>, does return a "node" record, with the name of <node> I have several post with "clean" and am...

...tckeeper-commit-pre postrun_command=/etc/puppet/etckeeper-commit-post [master] ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY storeconfigs = true storeconfigs_backend = puppetdb reports = store,puppetdb reporturl = http://dashboard/reports/upload node_terminus = exec external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http://dashboard /usr/share/puppet-dashboard/bin/external_node I have restarted/rebooted/reinstalled but still hit the same issue for puppet-dashboard. -- You received this message because you are subscribed to the Google Groups &quo...