Re: [Puppet Users] Enumerating Puppet Arrays

Potentially easier, you could use prefix($scripts, '/path/'), which comes from puppetlabs-stdlib to put the path on all members of the array. Then just pass the now prefixed array to the defined type described above. This avoids storing the script names externally, which may or may not be desir

[Puppet Users] hiera_config ignored if in an environment block

Per-environment Blocks Blocks named for environments are the most specific, and can override settings in the run mode blocks. Only a small number of settings (specifically: modulepath, manifest, manifestdir, and templatedir) can be set in a p

Re: [Puppet Users] Enumerating Puppet Arrays

Check out defined types. For a faked together example: define make_it_so::make_one_thing_so { cron { $title: command => "/path/$title", user=> 'deploy', hour=> '*/4', minute => '0', } } http://docs.puppetlabs.com/learning/definedtypes.html Then add a data structure

Re: [Puppet Users] Re: Announce: Facter 2.0.1

Hi Eric, Andreas give me the right way ! thx for your answer, i keep the --trace in my mind, it would allowed me to fix it by myself ! Dje Le 02/04/2014 18:07, Eric Sorenson a écrit : Hi to both Stefan and DJE - these problems usually come up when there are multiple versions of facter instal

[Puppet Users] Enumerating Puppet Arrays

Is there a way to do something like this: class make_it_so { $scripts = ["a.rb", "b.rb"] cron { $scripts: command => "/path/$scripts", user=> 'deploy', hour=> '*/4', minute => '0', } } The attribute usage of the array will just take the entire arra

Re: [Puppet Users] Announce: Facter 2.0.1

Le 02/04/2014 23:25, Andreas Ntaflos a écrit : On 2014-04-02 11:02, DjE wrote: The issue (-d does not provide more informations) : facter -p undefined method `puppetversion' for Facter:Module Something like this can also happen when you have a custom fact (or function?) that calls the Facter AP

Re: [Puppet Users] Announce: Facter 2.0.1

On 2014-04-02 11:02, DjE wrote: > The issue (-d does not provide more informations) : > facter -p > undefined method `puppetversion' for Facter:Module Something like this can also happen when you have a custom fact (or function?) that calls the Facter API in a now defunct way. For example, we had

[Puppet Users] Chaining difficulties setting up MariaDB

Puppet 2.7, using the mysql module, version 2.1.0. I do not wish to have Puppet manage the root password because passwords should not be included in my manifests (which are captured in Git). I have a setup where /root/.my.cnf symlinks to a central .my.cnf file on a NFS mount. The goal is to have

Re: [Puppet Users] Managing big changes

Hi, A couple of things that I have tried before. 1. If the intention is to perform a refactor where the code changes are large, but the expected changes to the catalog are small, I would recommend looking at: - https://github.com/ripienaar/puppet-catalog-diff Depending on what versions of Pup

Re: [Puppet Users] RHEL 7 Repository up on yum.puppetlabs.com

Great to know - we'll keep a keen eye out for EL7 puppet 3.5.0. Thanks again, - Kodiak On Wednesday, April 2, 2014 1:50:56 PM UTC-4, Matthaus Litteken wrote: > > Kodiak, > A Puppet 3.4.3 master should have no problems supporting a Puppet > 3.5.0 client, and if it does it is a bug that you shou

Re: [Puppet Users] RHEL 7 Repository up on yum.puppetlabs.com

Kodiak, A Puppet 3.4.3 master should have no problems supporting a Puppet 3.5.0 client, and if it does it is a bug that you should raise with us. On Wed, Apr 2, 2014 at 10:27 AM, Kodiak Firesmith wrote: > Hi Matthaus, and thanks for the reply! > > We are looking to run RHEL 7 clients during Redha

[Puppet Users] Service[foo] fails under --noop if its package has never been installed

Hello! I'm running `apply --noop` regularly. I would really like to also do it on a fresh machine before changing bits on the disk. Unfortunately this fails for Service types because their init scripts don't yet exist. For example, take ntp: package { "ntp": ensure => present, }

Re: [Puppet Users] RHEL 7 Repository up on yum.puppetlabs.com

Hi Matthaus, and thanks for the reply! We are looking to run RHEL 7 clients during Redhat's beta to prepare for the general release. We'll be upgrading our RHEL 6 Puppet Master to 3.4.3 shortly but don't plan to upgrade the Puppet Master to RHEL 7 any time soon. Will the version skew of a 3

Re: [Puppet Users] Puppet certification PPT-202

Someone know the score to pass? I'll examine next week Regards El 02/04/2014 12:17, "Julien Deloubes" escribió: > Hello Nathan, > indeed i noticed that the cert was updated to reflect the Puppet 3 new > features and what a change! > I can write manifests with the new best practices for coding in

Re: [Puppet Users] RHEL 7 Repository up on yum.puppetlabs.com

Kodiak, Puppet 3.5.0 is currently in RC and should go final soon. Are there packages you are looking for besides Puppet itself? On Wed, Apr 2, 2014 at 10:05 AM, Kodiak Firesmith wrote: > Hi PuppetLabs, > Any more word on the RHEL 7 effort? I'm a little surprised that EL7 is so > far into beta an

Re: [Puppet Users] RHEL 7 Repository up on yum.puppetlabs.com

Hi PuppetLabs, Any more word on the RHEL 7 effort? I'm a little surprised that EL7 is so far into beta and we still don't have much in http://yum.puppetlabs.com/el/7/. Thanks, - Kodiak On Tuesday, February 11, 2014 8:23:03 PM UTC-5, Melissa Stone wrote: > > On Mon, Feb 10, 2014 at 1:16 PM, J

[Puppet Users] Newbie namespace question: how to access variable in different module

Hi all, I am quite new to Puppet and are currently struggeling with the namespace. Thus, I have a manifest to deploy my service organized in manifests --> myservice.pp node "myservice.thing.foo"{ class {'myservice::deploy':} } The module is located in modules --> myservice --> manifests -->

[Puppet Users] Re: Announce: Facter 2.0.1

Hi to both Stefan and DJE - these problems usually come up when there are multiple versions of facter installed, i.e. one via gem and one via RPM/deb. Can you verify this is the case? Run with --trace and do something like 'find / -name facter -type d' (hopefully with some smarter options if yo

Re: [Puppet Users] Re: Announce: Facter 2.0.1

For those that are getting the undefined method errors, could you please run with --debug and --trace and paste the results so we could see a bit more information about where those methods are called from? Thanks, -Jeff -Jeff On Wed, Apr 2, 2014 at 7:50 AM, Stefan Wiederoder wrote: > we´ve

[Puppet Users] Managing big changes

Hi, I'm wondering if there's an established way on how to write and improve modules with potentially system-breaking or incompatible changes. One example are changes in the filesystem layout, or simply the change of an OS user's homedir (usermod fails because of running processes). Of course,

[Puppet Users] Error: Multilib version problems found

Hi Puppet Users, I'm facing below error after the repo updates: Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install libstdc++.i686' returned 1: Error: Multilib version problems found. This often means that the root cause is something else and multilib version checking is just

[Puppet Users] Re: Announce: Facter 2.0.1

we´ve had trouble with the new version too: [root@zoe ~]# facter undefined method `kernel' for Facter:Module result was a downgraded to 1.7.5-1 RHEL6-64 with ruby: 1.8.7.352 puppet: 3.4.3 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To u

Re: [Puppet Users] Duplicate hiera hashes in the same data source override instead of merge

On Tuesday, April 1, 2014 12:00:45 PM UTC-5, Robin Bowes wrote: > > I suspect duplicate keys are not valid YAML. > Indeed they are not. The keys of a YAML mapping are required to be unique ( http://www.yaml.org/spec/1.2/spec.html#id2764044). How a particular YAML processor deals with duplicat

[Puppet Users] Re: advice change user group aix

On Tuesday, April 1, 2014 8:43:14 AM UTC-5, hop wrote: > > Hello. > I wantaed to ask, if is a better way to change user groups then this: > > exec {"process $usr": > command =>"chgrp . $newGroup", > path=>[ "/bin/", "/sbin/" , "/usr/bin/", "/usr/sbin/" ] >

Re: [Puppet Users] puppet class require fails depending on declaration order

On Wednesday, April 2, 2014 4:57:39 AM UTC-5, David Portabella wrote: > > Oh My God! > > you mean that "it's not a bug, it is a feature" ? > > It is not a feature in the sense of a desired outcome, but it *is* the intended behavior. Specifically, if there is any parameterized-style declaratio

Re: [Puppet Users] Re: If-than-else

Hi, On 04/02/2014 12:38 PM, Sandro von Matterhorn wrote: > But why is there no sample for this in the puppet docu? :-( good point. The guide in http://docs.puppetlabs.com/guides/templating.html#erb-template-syntax does link to official ERB documentation, but that's less than helpful. An exampl

Re: [Puppet Users] Duplicate hiera hashes in the same data source override instead of merge

On 2 April 2014 08:47, Felix Frank wrote: > Yeah, sounds about right. > > Pardon my prejudice, but from your description I get the feeling that > you are not employing hiera to the height of its strengths. You want > your hierarchy to contain *data* for your nodes. While it's possible to > map al

[Puppet Users] Re: If-than-else

Am Mittwoch, 2. April 2014 12:13:20 UTC+2 schrieb Sandro von Matterhorn: > > Hi, > > when I use a template with such code: > > <% if @LDAPpuppetVar %> > do something > <% end %> > > it works in a way: If the puppetVar in LDAP exist, than do something, else > ignore. > > But how could I manage, tha

Re: [Puppet Users] Puppet certification PPT-202

Hello Nathan, indeed i noticed that the cert was updated to reflect the Puppet 3 new features and what a change! I can write manifests with the new best practices for coding included in P3 but all these new things included in PE scarred me a bit (Hiera, PuppetDB, ...), i mean i play a bit with t

[Puppet Users] If-than-else

Hi, when I use a template with such code: <% if @LDAPpuppetVar %> do something <% end %> it works in a way: If the puppetVar in LDAP exist, than do something, else ignore. But how could I manage, that if the puppetVar in LDAP exist than do something, else do something other? -- You received

Re: [Puppet Users] puppet class require fails depending on declaration order

Oh My God! you mean that "it's not a bug, it is a feature" ? On Wednesday, April 2, 2014 11:36:34 AM UTC+2, Jose Luis Ledesma wrote: > > hi, > > > from: > > > http://docs.puppetlabs.com/puppet/latest/reference/lang_classes.html#declaring-classes > > Include-Like vs. Resource-Like > > Puppet has

Re: [Puppet Users] puppet class require fails depending on declaration order

Thanks Jose for your answer. The note from the doc is quite vague in my opinion. I would understand that class c1 { class { 'c2' : } require "c3" } effectively mixes the two behaviors, but class { 'c1' : } class c1 { require "c2" } should not be a case of mixed behavior. The followin

Re: [Puppet Users] puppet class require fails depending on declaration order

hi, from: http://docs.puppetlabs.com/puppet/latest/reference/lang_classes.html#declaring-classes Include-Like vs. Resource-Like Puppet has two main ways to declare classes: include-like and resource-like. *Note:* These two behaviors *should not be mixed* for a given class. Puppet's behavior w

Re: [Puppet Users] Announce: Facter 2.0.1

Hi, First, Thank's for this new featured version of facter ! For your information, we have an issue with facter 2.0.1 on RedHat/CentOS 5.x (with ruby 1.8.7) and lastest puppet agent 3.4.3 When you say "no longer support ruby 1.8.5", what's about the 1.8.7 ? (here provided by the linux distribu

Re: [Puppet Users] Re: Is ensure_resource() evil?

I'm torn. While the duplication of resources across modules is a huge issue, I'm not sure I'd be comfortable with opening this particular box of Pandora's. Imagining a world where users can (and will, trust me) declare the same resource all over the place, I see much potential for bugs, unintended

Re: [Puppet Users] Duplicate hiera hashes in the same data source override instead of merge

Yeah, sounds about right. Pardon my prejudice, but from your description I get the feeling that you are not employing hiera to the height of its strengths. You want your hierarchy to contain *data* for your nodes. While it's possible to map all your resources to YAML and make heavy use of create_r