[Puppet Users] Re: Moving from Puppet 0.25 to Puppet 2.6+ : global scope/variables

Hi, On 24 avr, 18:40, jcbollinger wrote: > Another alternative would be to do exactly as you would have done with > 0.24 or 0.25.  Global variables, node variables, and dynamic scoping > still work in 2.6, and even 2.7 (though 2.7 will issue warnings about > resolving variables via dynamic scopi

[Puppet Users] Re: Moving from Puppet 0.25 to Puppet 2.6+ : global scope/variables

On 24 avr, 19:54, Ashley Penney wrote: > It checks every layer of the hierarchy, so it would look for: > > fqdn/server1.yaml > environment/staging.yaml > common.yaml > > But the important thing to know is it's looking for an actual variable.  If > you had defined > selinux: disabled in common.ya

[Puppet Users] Re: Moving from Puppet 0.25 to Puppet 2.6+ : global scope/variables

On 24 avr, 19:10, Les Ault wrote: > > I use facter variables to set dynamic parameters based on the host.  For > example I created a module to modify sysctl entries: > > node dbserver.example.com { >    include sysctl > >    # Modify sysctl values >    $shmall = inline_template("<%= (memorysizei

[Puppet Users] Re: Moving from Puppet 0.25 to Puppet 2.6+ : global scope/variables

On 24 avr, 15:34, Ashley Penney wrote: > This was a long email! Yeah, I know it might get a few "TL;DR" but I wanted to provided all relevant information. :) > The answer to your problems is definitely something > like > Hiera.  You make a common.yaml that has all your "defaults" and then you

[Puppet Users] Moving from Puppet 0.25 to Puppet 2.6+ : global scope/variables

Hi, I worked with puppet (< 0.25) back in 2008/2009. We were able to deploy 200 servers from scratch and manage them. It worked fine. I'm now with a new customer and I'm pushing Puppet (and I'm also back to puppet on a side project). We're considering Puppet 2.6 to manage RHEL/CentOS 5 or 6 host

[Puppet Users] Re: How to structure configuration using Puppet and version control tools

so like to hear how people do this in their setups. Thanks, Calimero --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To uns

[Puppet Users] Re: Puppetrun does not work with certificate error.

t figure out... OK, so I'll assume you've signed the certificate ! ;-) Is the time/date set correctly on the puppet client (and everywhere else) ? openssl doesn't like certificates signed in the future, for example. -- Calimero --~--~-~--~~~---~--~~ Yo

[Puppet Users] Re: Monitoring whether puppetd should be run

e a look at "The Foreman" which looks interesting. But I'd rather not add an extra layer / extra database. Thanks ! Calimero --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group.

[Puppet Users] Monitoring whether puppetd should be run

zabbix (our monitoring tool) and delete the report. Anyway, I'm wondering whether there's already a nifty feature that does what I want and that I missed. By the way we're running 0.24.8 but if 0.25 has better (well... "simple to parse") reporting, we could probably mov

[Puppet Users] Re: 32bit and 64bit versions of packages

ks like yum-basearchonly worked. Anyway we didn't experience any 32b/64b gotchas since we've set multilib to "best". Calimero --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users

[Puppet Users] User/managehome with useradd provider on CentOS

.7 package. I cannot report this (minor) bug through Redmine as the system just won't let me register... Hope it helps. Bye, Calimero --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group.

[Puppet Users] Re: "Scope" / Tags / Classes

On 5 fév, 16:53, Luke Kanies wrote: > It might just be an ordering thing - auto-imported classes certainly   > use exactly the same code internally that any other classes use. > > Check your classes.txt file on the client - I'm sure the classes are   > in there. You're right. All classes are fo

[Puppet Users] "Scope" / Tags / Classes

Hi, I've stumbled across the following behavior which I don't really understand: classes that are automatically "imported" (thanks to modulepath, ...) are not "really/fully" included. If I iterate over the classes and tags variables in a template: <% classes.each do |c| -%> Class: <%= c %> <% en

[Puppet Users] Re: Mounts: virtual ressources or multiple classes ?

arbitrary metadata around your resources, and   > then add them to the catalog without literal listings. Will dig into this too. Thanks for your input ! -- Calimero --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

[Puppet Users] Mounts: virtual ressources or multiple classes ?

Hi, We're trying to implement the following structure: class my_pool { include linux, httpd... base modules include project_A include project_B } One pool can have many projects. One projects can be on many pools. A project is basically made of: - directories + NFS mounts - users and cr

[Puppet Users] Modules / inheritance / best practices

tpd_listen_ports a global variable in sites.pp but doesn't this defeat the purpose of modules ? Bottom line is: how do I define default values in a "module" that can be (quite) easily and overriden ? I guess I must be missing something here. Maybe I should look at define() ? Thanks fo