Joel Merrick <joel.merr...@gmail.com> writes:
> On Tue, Oct 26, 2010 at 11:35 AM, Daniel Pittman <dan...@rimspace.net> wrote:
>>
>> The other is to use puppet to perform the work, and to use the
>> PuppetCommander[3] mcollective plugin. This allows you to schedule puppet
>> runs from a central service.
>>
>> With this you can configure, for example, concurrency per collection of
>> machines, where "collection" is defined as any mcollective search.
>
> That's brilliant. I only became aware of MCollective yesterday (really
> intrigued by the exim stuff, can see it being extremely useful!) and I can
> see that fabric being a really good way of managing service.
*nod* MCollective was also recently acquired by Puppet Labs, so it is
... well, presumably related to the long term direction of the two products to
work together.
> I'll go off an do some reading regarding it. Many thanks for the heads
> up, you were spot on with the git question too.
Glad I could help.
Daniel
--
✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
