similar to: Using regex to match hostnames in hiera

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

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''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

I am using puppet 2.6.11 and want to pass parameter for implementing sudo for mulitple users. So here is my simple code, which I would like to pass to hiera to specify user name lookup. Appreciate any help, thanks in advance. class sudo( $name) { #Class:: sudo # # package { "sudo": ensure => present, } file { "/etc/sudoers": owner => root, group => root,

Morning All I''m trying to use Hiera with Puppet 3.0 to streamline some of my module configuration... However I''m having issues using the ''*%{::clientcert}*'' variable as part of the hierarchy... Currently, my *hiera.yaml* file looks like: --- :backends: - yaml - json :yaml: :datadir: /etc/puppet/hieradata :json: :datadir: /etc/puppet/hieradata

I am trying to create a hostgroup using the Foreman API (foreman-0.4-0.1rc1.noarch): Using perl v.5.14.2, REST::Client et. al., ending up with sending: POST /hostgroups {"name":"api-created-

I am trying to supplement and ultimately provide a patch for ''foreman'' which is an adjunct to puppet. Essentially, there is a Hosts class which belongs_to Hostgroup and Hostgroup class has a column called ''ancestry'' which is actually a Hostgroup (probably what is referred to as STI but I am not sure) and thus within Foreman, nesting Hostgroups is not uncommon.

I''ve tried to achieve my overall goals with several different features of Puppet, but I''ve hit a bit of a wall here. I think it''s time for me to explain what I''m trying to accomplish: I want the enabling of a service in my manifests to configure the monitoring of that service by a nagios server, without needless repetition. Let me explain how my

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 all . i am running puppet version 2.6.16 and foreman Version 0.4.2 . my question is as follows . i would like to know if there is a way to tag server with a group tagging . for example . let say i am running apache with a unique configuration and network architecture and want to tag in with "tag1" and a i have few more apache installation with the a new unique configuration and

Hi all, I''d like to specify a base_directory and a list of directories (as variables that may be pulled via hiera later) that will be created under that base directory. base_dir = "/home/base" bars = ["a", "b", "c"] bars will be used to create the folders under base and also part of the information going into building a template so I

I have a module located at /etc/puppet/environments/test/modules/ruby. I n this I have a manifests folder with two .pp files - init.pp and gemInstall.pp. In one of my node def files I have: include ruby ruby::gemInstall { ''someGem-version.gem'': path => ''/path/to/agent/local/gem/repo'', } ruby::gemInstall is a define, and it has some logic to get around

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()

Hi everyone, I am reconsidering how I am using the Puppet nagios functionality, at the moment I am creating one service for each check on each host. A lot of them are identical, and would be better tied to hostgroups to simplify my config. Namely, I have about 5,000 checks in there now which will go up to about 20K over the next month, and it''s taking about 5-10 minutes for a Puppet

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

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 all! I''m trying to setup a puppet module for sudo that will write multiple files with separate data for each file, all dependent on the hiera hierarchy. Here''s the relevant portion of my hiera.yaml: > :hierarchy: > > - "datacenter/app/role/node/%{::clientcert}" > > - "datacenter/app/role/%{::server_role}" > > -

We''re trying to set a role variable in one of our role classes i.e. class role::nameserver { $::role = ''nameserver'' include profile::baseline } however we get the following error Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment production: Cannot assign to variables in other namespaces We do not get

Hi list, I ran again against a long standing bug / feature request but from a new angle: creating directories with parents ( http://projects.puppetlabs.com/issues/86). I wanted to create a module, where a path could be supplied with a class parameter. The path would be used in a rsync configuration, so I would like to be sure the path exists. As I want the module to be general and completely