[Puppet Users] Re: howto trigger action on another client

2011-06-28 Thread jcbollinger
On Jun 28, 2:36 am, Andreas Kuntzagk wrote: [... I wrote:] > > In general, facts, including custom facts, are the Puppet means for > > providing nodes' state details to the puppetmaster. > > It's probably the "clean puppet way(tm)" to do it but to write custom facts > you > need to learn some

Re: [Puppet Users] Re: howto trigger action on another client

2011-06-28 Thread Andreas Kuntzagk
Hi On Jun 27, 9:37 am, Andreas Kuntzagk wrote: Thanks for these infos. I think I got at least a vague idea how this works and can already use it for some simple cases. One more question: If I define checks for the "exported exec" (like "creates" or "onlyif" will these run on the exporting agen

[Puppet Users] Re: howto trigger action on another client

2011-06-27 Thread jcbollinger
On Jun 27, 9:37 am, Andreas Kuntzagk wrote: > Thanks for these infos. I think I got at least a vague idea how this works and > can already use it for some simple cases. > One more question: > If I define checks for the "exported exec" (like "creates" or "onlyif" will > these run on the exporting

Re: [Puppet Users] Re: howto trigger action on another client

2011-06-27 Thread Andreas Kuntzagk
Thanks for these infos. I think I got at least a vague idea how this works and can already use it for some simple cases. One more question: If I define checks for the "exported exec" (like "creates" or "onlyif" will these run on the exporting agent or the executing agent? (my guess is the second

[Puppet Users] Re: howto trigger action on another client

2011-06-24 Thread jcbollinger
On Jun 24, 9:18 am, Andreas Kuntzagk wrote: > Daniel Maher wrote: > > On 06/24/2011 03:39 PM, Andreas Kuntzagk wrote: > > >>> Exported resources are the Puppet means for one node to provide > >>> resources for another. In this case, the execution host could export > >>> an Exec resource for the

Re: [Puppet Users] Re: howto trigger action on another client

2011-06-24 Thread Ken Barber
Another mechanism. You can use mcollective and this resource to trigger mco calls inside puppet: https://github.com/ripienaar/puppet-mcollective The resource acts like an exec ... and can be refreshed and notified. For example: file {"/tmp/foo1": # content => "foo", content => inline_template

Re: [Puppet Users] Re: howto trigger action on another client

2011-06-24 Thread Andreas Kuntzagk
Daniel Maher wrote: On 06/24/2011 03:39 PM, Andreas Kuntzagk wrote: Exported resources are the Puppet means for one node to provide resources for another. In this case, the execution host could export an Exec resource for the master to collect and apply. Hmm, in the (very short) time I've bee

Re: [Puppet Users] Re: howto trigger action on another client

2011-06-24 Thread Daniel Maher
On 06/24/2011 03:39 PM, Andreas Kuntzagk wrote: Exported resources are the Puppet means for one node to provide resources for another. In this case, the execution host could export an Exec resource for the master to collect and apply. Hmm, in the (very short) time I've been working with puppet

Re: [Puppet Users] Re: howto trigger action on another client

2011-06-24 Thread Andreas Kuntzagk
jcbollinger wrote: On Jun 24, 3:14 am, Andreas Kuntzagk wrote: Hi, I want to automate installation of GridEngine with puppet. GE comes with some prepared script for automatic installation. Unfortunately this is to be run on the GE master to install the executions host (=clients). (This then

[Puppet Users] Re: howto trigger action on another client

2011-06-24 Thread jcbollinger
On Jun 24, 3:14 am, Andreas Kuntzagk wrote: > Hi, > > I want to automate installation of GridEngine with puppet. GE comes with some > prepared script for automatic installation. > Unfortunately this is to be run on the GE master to install the executions > host > (=clients).  (This then will ru