search for: antoninus

I would like to do a case statement based on different vlans. If a person does a case statement on $ipaddress provided by facter, can you match regex expressions such as case $ipaddress { "192.168.1.[0-9]+": do something "192.168.2.[0-9]+": do something else } Also, would this best be solved by a case statement or other functionality within puppet? Thanks

...sage mailing list, a couple of people are debating the relative merits of Puppet and cfengine: http://www.sage.org/lists/sage-members-archive/2006/msg01433.html -- Never esteem anything as of advantage to you that will make you break your word or lose your self-respect. -- Marcus Aurelius Antoninus --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com

Hi, I''ve added in some initial user management to my growing puppet configs, and I''m seeing an odd behavior in that it is trying to set the groups for the users each time, despite them already being set. The list of groups it is setting for the user contains each group twice, in what seems to be a random order, like this: notice:

Hi, Is it possible to have an array as the output of a custom fact? And then to pass it into a template in Puppet? I currently have a fact that looks like this: Facter.add("exports") do setcode do case Facter.hostname when (/thishost/i): [ "/local", "/local2" ] end end end & a template like this: <%

In my puppet client I have puppet.conf defined puppet server as mypuppet server = mypuppet.example.net Not sure why the puppet client puppet-test is still sending these noises to the syslog Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911 daemon.error] Could not find server : getaddrinfo: node name or service name not known Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911

I testing Puppet 0.19.3. If we decide to use it, we''d deploy it across several thousand hosts. The method described for creating client certificates described in the documentation - running "puppetd --server <server> --waitforcert 60 --test" and "puppetca --sign <client>" - is not practical for our installation. I''ve tried creating

Hello, i wanted to know if we can use exported ressrouces to do things like this: - for all nodes tagged as xxx create on the node yyy a file which content is a template where we can have each hostname , or create one file per nodes matching exemple /etc/hosts.allow sshd: host1 sshd: host2 ... or /etc/backuppc/host1 /etc/backuppc/host2 ... from the docs it seems i can collect only ALL

Hello everyone, A long time ago, I posted the Stanford Best Practices and I''ve gone through and updated it today. I''d like to have people go through it and see if we can strip out some Stanford specific stuff and tag this as an official best practice. I think an official best practice will be important as more and more people consider making shareable modules, etc (mostly