similar to: hiera scope and hiera-foreman

I''ve begun using Hiera in combination with Foreman, primarily storing data that is best left in Array/Hash form. I''d like to be able to have a module, in this case BackupPC, query all the Hiera data for each node where the backup directories/databases are stored. Then use all that information on the BackupPC server to generate proper configuration files for each

Dear puppetteers, I am having a philosophical question about parametrized classes. When building modules, one wants to be as flexible as possible, to try to target as many puppet flavors as possible. This is our target: - Foreman users, using foreman as an ENC with smart variables (or potentially any other ENC, but I would say this is the most widespread one). - Pure Puppet''s site.pp

Hi, I have just started to use Foreman 1.1. I have been using Puppet for a while and have some custom modules and ones that have been dragged down from git etc. I am using nodes.pp in Puppet to assign classes and template entries to hosts. So is Foreman meant to eliminate my need for a nodes.pp? How do I manage my erb templates in Puppet without a nodes.pp? Thanks, -- You received

I''ve been trying to find information, suggestions, etc. for how to combine scaling Puppet with the use of management tools like Dashboard/Foreman and MCollective. Our current thinking for an initial deployment is two VMs as Puppet Master worker nodes fronted by a pair of NetScalers. However, I''m not sure how to go about implementing Dashboard or Foreman and MCollective servers in

After digressing into this discussion on #puppet last night, I was wondering what the community feelings are on ENCs vs Hiera... I know that Dashboard/Console still exists, but have heard rumors (for years) of it being either replaced by something else, or totally rewritten. Then there's Foreman, and a bunch of us with homegrown ENCs. On the other hand, it seems that the bleeding edge of the

Hiera was properly working in my environment. But puppet was looking at old version even when I have the latest hiera gem installed. So I could''nt use json backend. But puppet is not looking at my latest hiera gem. Not sure when went wrong here. Scenario: I have installed hiera couple of months back. So the gem was installed under /opt/puppet/lib/gems/1.8/gems/hiera-0.3.0

Hi Puppet Users, For some bizzare reason I am unable to use hiera-puppet with a parameterised class. The output is: ---------------------------- root@hiera hieratest/manifests# puppet apply -e "include hieratest" Error: undefined method `catalog'' for #<Hash:0xb6c53d00> at line 1 on node hiera.localdomain Wrapped exception: undefined method `catalog'' for

Hi, I''m trying to use standard hiera on puppet (gentoo). I simply did # gem install hiera Then setup /etc/hiera.yaml When i call the hiera() function in puppet i get "Error 400 on SERVER: Unknown function hiera at /data/puppet/manifests/ site.pp:27" Is there a step that I''m missing? BTW. standalone hiera works fine. -- You received this message because you

Hiera-Puppet 1.0.0rc1 is a feature release candidate designed to accompany Puppet 3.0 and Hiera 1.0. It includes Puppet functions for hiera and also the puppet backend for hiera lookups. Downloads are available: * Source http://downloads.puppetlabs.com/hiera/hiera-puppet-1.0.0rc1.tar.gz * Apt and yum development repositories * Apple package

Hi, This follows on a bit from the previous thread ''trouble with hiera and puppet defines'' [1] Up to now I''ve had a large file of virtual resources and then enabled them on demand on various services. The very standard. @metric{''1234: one => 1 two => [1,2] } @metric{''abcd'': one => a, two => [b,c] } and

Hi, Before I begin, my environment consists of a standard master/client config with the exception that all my clients run under a non-root user. I have to use non-root so I can''t simply restart under root to fix the problem. Master -> 3.1.1 Client -> 2.7.17 using mostly the hiera() function in my classes. problem: I have run into an issue today where my custom fact is not

Hi all, I''m trying to work with hiera database in puppet and i''m having problems using %{variables} because they don''t get the values and i don''t know why. file hiera.yaml: cat hiera.yaml --- :backends: - yaml - puppet :hierarchy:- nodes/%{domain}/%{hostname} - os/%{operatingsystem}/%{operatingsystemrelease} -

All, I have found very few references to this error so I''m guessing I must be doing something wrong. I have just started using hiera and am trying to use it in the simplest way possible, I have a class that looks like this: class app_users2($compresslogs = hiera(''compresslogs'')) {

Hi All, I have a working installation of a Puppet Master (CA) with Puppet agents, this using The Foreman. I really see the usage of Puppet this way but because The Foreman supports pushing your classes/templates to you nodes (agents) and uses the depricated Run/Kick for it I''m looking into Mcollective. Mcollective is supported by The Foreman since 1.2, the version I''m

Hi, I''m trying to do something with Hiera, whereby the ''default'' configuration for a class is within it''s role/profile manifest, which can then be overridden on a node specific basis by hiera. As an example; class profile::base { class { ''::ntp'': servers => [''a'', ''b'', ''c'',

Hi all, Over the weekend I came up with a new backend for hiera for looking up configuration values directly from a MySQL database that may be useful to some.... http://www.craigdunn.org/2012/03/introducing-hiera-mysql-mysql-backend-for-hiera/ http://github.com/crayfishx/hiera-mysql Regards Craig -- Craig Dunn | http://www.craigdunn.org Yahoo/Skype: craigrdunn | Twitter: @crayfishX --

Hi, I''ve just run into a small glitch with Hiera. I have a YAML file that has a definition like this: puppet_agent_splay: false but the run fails because of "err: Could not find data item puppet_agent_splay in any Hiera data file and no default supplied at /puppet/modules/puppet/manifests/agent/config.pp:6 on node slave1.local" Digging into this it turns out that lookup in

Hi, I''m using Puppet 3.2.1 and heavily relying on hiera data bindings. I have the following situation: class software ( $my_content = undef, ) { file { ''/path/to/file'': content => $software::my_content, } } in hieradata/software.yaml (hiera.yaml seems ok): software::my_content: template(''mymodule/myfile.erb'') With this configuration I

Hi, I''m trying to reconcile the advice in the Puppet 3 class doc with our current use of Hiera. We currently retrieve variables from Hiera in one big collection while the Puppet 3 doc seems to indicate storing variables without the collection. For example, we have a module to manage a log indexer. In its init.pp it says: class log_indexer( $log_indexer_conf =

Hello, I have number of classes that deal with user management and I''ve run into a snag with needing to extend/modify either the user or group types. I''m using theforeman as an ENC. The class structure I have is something like the following. users::common users::dev users::prod etc... users::{dev, prod} do not use inheritance. Almost all node include users::common.