similar to: Sourcing node variables

Hmmm.... So I was just trying the extlookup function that comes with puppet 2.6.1. It now lets you do this: $version = extlookup("rsyslog_version", "present", "packages") which, according to the documentation: # This will look for a version configured in packages.csv and then in the rest as configured # by $extlookup_precedence if it''s not found anywhere

Is there a way I can split a line in a manifest across multiple lines, ala shell style? ie: $include_postfix_module = extlookup("IncludePostfixModule", \ extlookup("IncludePostfixModule", \ extlookup("IncludePostfixModule", \ "",

Hi, We currently use ldap ENC to set server role variables and extlookup to set domain or environment variables. I have a suggestion regarding ldap use as an ENC - if a node within ldap has the environment attribute set then it should inherit/mixin (if available) from a node named after it''s environment. It could be populated with only puppetVar type attributes so that any environment

I''m trying to upgrade from 2.6.7 to to 2.7.6 and I''m running into an issue in my extlookup() calls. A lot of the variables which should be defined aren''t defined within extlookup.rb. I''ve tested 2.6.7 agent and 2.7.5 agent against the 2.6.7 master and 2.7.6 master. I adjusted extlookup.rb slightly to provide some debug output.

Running puppet 2.6.11 opensource on Red Hat 5.6 client. I cannot explain this logically but I have a directory structure like so: /etc/puppet/manifests/hiera/hostgroups/ with directories for each of my application areas like so: *clickz core devel dns icross iswap itch puppet test ubuntu* *What is weird is that if I put anything under the directory named "core", the ext

Hi, I''m having a problem with extlookup not respecting the ''certname'' parameter[1].  When executing a puppet run with either the --certname or --fqdn parameters, it ends up using the specified SSL certificate and gets the correct node definition applied from the puppetmaster.  However, it still retrieves extlookup data using the node''s actual FQDN, not the one

On Fri, May 27, 2011 at 1:08 PM, R.I.Pienaar <rip@devco.net> wrote: > And for what its worth this afternoon just to see how hard it is > and to again ask to myself ''wtf has no-one done this yet?'' and also > ''wtf are people at Puppet Labs reinventing this wheel?'' I wrote > a new extlookup that has pluggable backends. > The bit about

I''ve got this: file { ''/opt/sugarsync/tomcat/tomcat-home/current'': ensure => "tomcat-$config[''tomcat_version_server'']"; where $config[''tomcat_version_server''] was set with extlookup (the yaml one), by loading: --- tomcat_config: tomcat_version_server: 6.0.20-1 tomcat_version_libs: 1.0-1

I''m confused about this... https://github.com/puppetlabs/puppetlabs-stdlib/ I see a lot of functions there that are the same as the ones that come standard with puppet. If I create a module and dump this stuff in there, what happens to the existing stuff? How does puppet know which one to use? Doug -- You received this message because you are subscribed to the Google Groups

Anyone able to explain why "$fqdn" works and "$environment" doesn''t in: $extlookup_precedence=["%{fqdn}","%{environment}","common"] How to reproduce it: ----------------------------- - In "/etc/puppet/manifests/site.pp" : $extlookup_datadir = "/etc/puppet/manifests/extdata"

I''ve been struggling with puppet variable scope all day, well, for several months actually. I think I have pretty simple requirements. For any given node, I want to be able to set a series of variables and include a set of classes, based on three different aspects of a node, being physical location, operating system, and function. If I try and do this with classes, I find that variables

Seems like nodes are matching the default node before they are matching the more specific nodes. My site.pp has: include "nodes/*.pp" In the nodes directory are two files, default.pp and nagios_server.pp. default.pp: node default { include role::common } nagios_server.pp: node ''mon01.us1.xxx.com'' { $node_env = "production" include

Oh my god.... what is this? Getting this on first boot of new client. Aug 24 01:11:09 app03 puppet-agent[5392]: Reopening log files Aug 24 01:11:09 app03 puppet-agent[5392]: Could not request certificate: Neither PUB key nor PRIV key:: header too long I stop the client, and remove the ssl directory on the client: [root@app03 puppet]# service puppet stop Stopping puppet:

Trying to use extlookup from within template i use <%= scope.function_extlookup("blah") %> but get the undefined method `function_extlookup'' error According to http://docs.puppetlabs.com/guides/templating.html#access-to-variables-and-puppet-functions-with-the-scope-object this should work. Thanks Alex -- You received this message because you are subscribed to the

Hi, Is it possible to use facts from external nodes via stored configs, based on a filter such as class? To illustrate, I provide the following use case ; class nagios::nrpe { # No such resource "ip". I''d like to use "ip" fact of any node that is assigned to class "nagios::server" $nagios_servers = Ip <<| class="nagios::server"

Imho, should be intesting some idea on the integration of puppet in large corporation, the possible workflow, the separation of duty. For example using something as gitolite, the integration with quality control of some sort, the reporting. I have read something in pro puppet : i am sorry but most of that is discussed there in this area is very basic. Best regards ----Messaggio originale---- Da:

I''m looking for a bit of best-practices here. Our puppet environment up-until-today has been owned and operated by IT Operations only. We''ve had a single ''production'' environment and our code has been managed in a local GitHub::FI install. We have ~14,000 lines of code in our PP files. We''re trying to make two changes to our environment... that may need

Hi I''m having some trouble with the following setup: node ''serverA'' inherits server-defaults { include myApp::install } node ''server-defaults'' inherits default { $sudoenv = ''custom_server'' } node default { $sudoenv = ''default'' include sudoers::config } class sudoers::config { file {

Hi All, Just to share something small, I''ve adjusted rip excellent extlookup function to be able to search for csv files also inside of modules. You can store your data files inside your modules directly, and it is also possible to lookup in different modules. for example - if you have a common module and a location module, the variables defaults can be stored in the common module, and

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