On Tue, Oct 11, 2011 at 02:13:36AM -0700, Lucian Holland wrote:
> Hi All,
>
> I've been exploring puppet and mcollective recently and I was
> wondering if people here might be able to point me towards some
> information on a potential use case. It seems like puppet is primarily
> used at the moment as a tool for managing individual machine
> configurations ('What do I need for a web server in production?'). At
> the same time there is work going into imperative, distributed
> solutions for provisioning machines and getting them set up with
> puppet, either based on mcollective or custom built with tools like
> fog (e.g. the new cloud provisioner). I'm wondering, though, has
> anyone gone a step further and used the puppet declarative approach to
> define the structure of a whole network? This would be particularly
> useful for local CI environments when combined with virtualisation.
I've been pondering something not dissimiliar to this recently, a sort
of "config introspection", for some of our live services (e.g. load
balancers). My initial thoughts were geared around collected resources,
but I'm not sure the model works well for them. We already use puppet
manifests to provide control info to mcollective, so feeding mcollective
discovery back into puppet might be an interesting way to do some of
this information gathering. The scope of what we're thinking about is a
fair bit smaller than the sort of holistic, whole system stuff Lucian is
talking about though.
Stu
--
>From the prompt of Stu Teasdale
Computer programmers never die, they just get lost in the processing.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
