similar to: Puppet environment can't be used in extlookup (precedence)

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.

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

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

Hi, I have been trying to improve the coding of some of my puppet recipes and had some trouble so wrote this: http://blog.wl0.org/2011/05/thoughts-about-extlookup-in-puppet/ Comments on the web seem to indicate that extlookup() solves "all problems" but I don''t really see that and hence have proposed a possible way to keep the data closer together and make the extlookup()

I''m new to Puppet, and I''m a software developer, not a sysadmin, so be gentle. I have puppet managing some files via templates, and one of the template variables that needs to be plugged in is a password of sorts that shouldn''t be generally available. In particular, it can''t be stored in the manifest, as that''s stored in version control, and the

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

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

Hi all I have been pondering this for a while, but not yet seen a clean way to do it I have a few puppet classes (apache/ntp/mysql/bacula/nagios/etc) I would like to generate part of my bacula and nagios configs for each host based on which other classes that host belongs to (or to put it another way, I would like to export variables from classes which would be used by my bacula and nagios

Hi list, Reading the thread "can a class require an other class?" it''s been mentioned that perhaps one way forward for the Puppet language is to phase out the include keyword in favour of parametrised classes. I''m thinking of my Puppet and the several levels of include chaining I use and I''m wondering how on earth that''d be possible. Maybe

Is there a way to use send multiple parameter values using puppet dashboard ENC? For example, nameserver = 10.0.0.1, 10.0.0.2 or perhaps nameserver = [''10.0.0.1'',''10.0.0.2''} then the template erb file can loop through each of the nameserver values to set up mulitple nameservers in resolve.conf? Thanks - Oli -- You received this message because you are

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

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

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

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"

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 {

Let''s start with this: class whatever ( $myType=''other'' ) { file { "some-config-file": ... content => $myType ? { ''this'' => template("whatever/this.erb"), ''that'' => template("whatever/that.erb"), ''other'' =>

Switch the 53c700 driver to only use non-coherent descriptor memory if it really has to because dma_alloc_coherent fails. This doesn't matter for any of the platforms it runs on currently, but that will change soon. To help with this two new helpers to transfer ownership to and from the device are added that abstract the syncing of the non-coherent memory. The two current bidirectional cases

Switch the 53c700 driver to only use non-coherent descriptor memory if it really has to because dma_alloc_coherent fails. This doesn't matter for any of the platforms it runs on currently, but that will change soon. To help with this two new helpers to transfer ownership to and from the device are added that abstract the syncing of the non-coherent memory. The two current bidirectional cases

Switch the 53c700 driver to only use non-coherent descriptor memory if it really has to because dma_alloc_coherent fails. This doesn't matter for any of the platforms it runs on currently, but that will change soon. To help with this two new helpers to transfer ownership to and from the device are added that abstract the syncing of the non-coherent memory. The two current bidirectional cases