Re: [Puppet Users] Best practice for modules used for multiple environments

2009-12-16 Thread Kenneth Holter
This looks really great. I will definately look into this approach. Thanks for the tip! Regards, Kenneth On Thu, Dec 10, 2009 at 12:47 PM, Ohad Levy wrote: > You might consider using extlookup (http://nephilim.ml.org/~rip/puppet/* > extlookup*.rb) > or if you use foreman, you could define vari

Re: [Puppet Users] Best practice for modules used for multiple environments

2009-12-10 Thread Christopher Johnston
I do this exactly the same way, we just use the domainname fact and match that to the site. All really depends on the environment of course. Works perfectly, one thing you might want to stick is a default at the bottom which either provides a failsafe set of attributes and/or fails so you can pic

Re: [Puppet Users] Best practice for modules used for multiple environments

2009-12-10 Thread Carl Caum
Currently, we handle this by using variables that we set when parsing site.pp. We have a directory /etc/puppet/manifests/resources. In site.pp, we have 'import resources/*' before we have any node definitions. One of the files in the resources directory may be something like sites.pp where we

Re: [Puppet Users] Best practice for modules used for multiple environments

2009-12-10 Thread R.I.Pienaar
hello, - "Peter Meier" wrote: > $vhosts_dir = $operatingsystem ? { >centos => "$apache::centos::config_dir/vhosts.d", >gentoo => "$apache::gentoo::config_dir/vhosts.d", >debian => "$apache::debian::config_dir/vhosts.d", >ubuntu => "$apache::ubuntu::config_dir/vhosts.d", >

Re: [Puppet Users] Best practice for modules used for multiple environments

2009-12-10 Thread Peter Meier
> I've been trying to get some modules written for CentOS/RedHat working > on my Ubuntu systems, and wondering the best way to do this myself. A > good example is the differences between Apache on the two kinds of > system: > > Apache runs as 'www' on the RH systems, and 'www-data' on the > Debian

Re: [Puppet Users] Best practice for modules used for multiple environments

2009-12-10 Thread Julian Simpson
2009/12/10 M.F.Haris : > Yeah I have a similar issue as I have to configure SNMP on different clients > and the structure of SNMP (configurations files and service management) is > different and vary from client to client as some clients are running on > Fedora, some on SuSe and some on IBM AIX. I

Re: [Puppet Users] Best practice for modules used for multiple environments

2009-12-10 Thread M.F.Haris
Yeah I have a similar issue as I have to configure SNMP on different clients and the structure of SNMP (configurations files and service management) is different and vary from client to client as some clients are running on Fedora, some on SuSe and some on IBM AIX. any suggestions and comments are

Re: [Puppet Users] Best practice for modules used for multiple environments

2009-12-10 Thread Ohad Levy
You might consider using extlookup (http://nephilim.ml.org/~rip/puppet/* extlookup*.rb) or if you use foreman, you could define variables in different levels (e.g. in the domain level, subnet level etc). cheers, Ohad On Thu, Dec 10, 2009 at 7:19 PM, Kenneth Holter wrote: > Hi. > > > Some types of

[Puppet Users] Best practice for modules used for multiple environments

2009-12-10 Thread Kenneth Holter
Hi. Some types of configurations need different parameters depending on which environment/network the puppet client reside in. An example is DNS configuration found in /etc/resolv.conf, which may vary depending on which network the puppet client is on. Another example is LDAP client setup, may al