[Puppet Users] Re: variables that are available inside a template

2009-02-20 Thread Brice Figureau
On Fri, 2009-02-20 at 10:58 +0800, Ohad Levy wrote: > Thanks, I know that, but I was hoping to avoid it.. as I want to pass > an array of files to the same template. > > is there a scope variable which define the current resource? maybe > something like scope.name? I think what you're looking fo

[Puppet Users] Re: One troublesome puppet hangs, an identical puppet does not

2009-02-20 Thread Brice Figureau
On Thu, 2009-02-19 at 08:23 -0800, Jeff wrote: > I have two servers with an identical configuration. Let's call them > 002 and 003. I've narrowed down my problem to the following two blocks > of puppet code: > > file {[ > "/usr/local/jboss/server", > "/usr/local/ATG/ATG2007.1/home/logs",

[Puppet Users] Re: Define statement not being recognised - or so it seems

2009-02-20 Thread paul matthews
Pete, Thanks very much. That was definitely one of the issues. The other seemed to be that the node definition in nodes.pp needed to say *zones::zone_instance { "solzone":* etc rather than *zone_instance { "solzone":* thanks Paul 2009/2/19 Peter Meier > [...] >> Running on the puppet client

[Puppet Users] Managing a symlink

2009-02-20 Thread Keith Edmunds
I have a directory that I wish to create and populate on clients, and that works fine. However, I want to include a symlink in that directory. Initially I wrote a "file" directive to create the symlink, but Puppet complained with "Not managing more explicit file ...", presumably because it was alr

Re: [augeas-devel] Re: [Puppet Users] Testing help for new Augeas Puppet provider which only executes if required

2009-02-20 Thread Bryan Kearney
Ben wrote: > David Lutterkort wrote: >> On Thu, 2009-02-19 at 16:26 -0500, Bryan Kearney wrote: >> >>> so.. the next question this is if we attempt the model of not executing >>> unless changes are made at the initial scan, it is possible that some >>> other change between steps 3.3 and 5.1

[Puppet Users] Access to config settings in manifests

2009-02-20 Thread Bruce Richardson
Is there currently a way of accessing arbitrary puppet configuration settings from manifests? A function or a virtual class (as in PuppetConf('plugindest') or $puppet::plugindest. I'm guessing not, but that writing a function to do this wouldn't be hard (in which case I'll go off and do it). --

[Puppet Users] user type issue

2009-02-20 Thread nmay
Hi guys. I have virtual user in my *.pp like that @user { "grt_user2": uid => "N", gid => "N", comment => "", home => "/home/grt_user2", membership => minimum, shell => "/bin/bash", groups =

Re: [augeas-devel] Re: [Puppet Users] Testing help for new Augeas Puppet provider which only executes if required

2009-02-20 Thread David Lutterkort
On Fri, 2009-02-20 at 07:53 -0500, Bryan Kearney wrote: > One question If I have a file with 10 nodes, does augeas re-write > the whole file, or just scan for the nodes which changed? It will write a new file (into a tmp location) and then replace the old file with the new one. Since rename(

[Puppet Users] Controlling gconf values

2009-02-20 Thread Brad Dixon
Hello: I'd like to ensure that I've set-up various gconf settings for users. I cobbled together this little sad definition: define gconf($type, $value, $user) { exec{"set $name to $value": command => "/bin/su $user -c '/usr/bin/gconftool-2 --config-source xml:readwrite:/home/$user/.g

[Puppet Users] How to force virtual resource collection?

2009-02-20 Thread Jeff Palmer
Hello! I am currently running puppet 0.24.4 on ubuntu, and I am using the nagios types to automatically generate services and hosts as servers are stopped and started at EC2. I am currently deleting host entries from the stored config DB when a server is shutdown, but I can't figure out how to ge

[Puppet Users] Re: Controlling gconf values

2009-02-20 Thread Mike Renfro
On 2/20/2009 4:52 PM, Brad Dixon wrote: > Hello: > > I'd like to ensure that I've set-up various gconf settings for users. > I cobbled together this little sad definition: > > define gconf($type, $value, $user) { > exec{"set $name to $value": > command => "/bin/su $user -c '/usr/bin/