On Feb 2, 10:38 am, Michael DeHaan <mich...@reductivelabs.com> wrote:
> What do you think?

Please forgive me, but I am apprehensive about some of those ideas.
One of the reasons Puppet is great is that it is organized around a
compact goal and consistent operating and design principles.   Its
goal is to achieve and maintain system state, and among its key
operating principles is "Puppet chooses how to do it."  I am concerned
that Puppet will become less reliable, harder to use, and harder to
develop and maintain if it is extended in directions that are
inconsistent with its core goals, operating principles, and design
principles.

It seems a natural extension to enable Puppet to manage the collective
state of an entire network, which I hope you find a fair
characterization of your class (A).  I think there are some
significant practical problems with doing that, however, large among
them that of assessing the collective state of a whole network in the
first place.  The framework extensions needed to support this
extension could easily dwarf all the rest of Puppet.  Looking at it
another way, a generic solution to this class of problems would
essentially be a business process orchestration framework for system
configuration.  Google "business process orchestration" if you don't
appreciate the size and complexity of systems that do that.

As for your class (B), to the extent Puppet doesn't already support it
via Exec, just no.  At the risk of being pedantic, asking to "Be able
to run tasks [...]" of *any* kind via Puppet already runs counter to
the Puppet paradigm.  The Exec type notwithstanding, Puppet is not a
task runner.  I don't think Puppet is the right tool for that job, and
I would prefer that its operating principles not be compromised to
make it the right tool.

With all that said, if you think puppetd provides a good foundation
for some of these things then nothing prevents you from building on
it.  Puppet is fairly easy to extend with new resource types, and
nothing prevents you from hooking puppetd up to a process
orchestration suite.  I am sure you would have an interested audience
for such work.

-- 
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.

Reply via email to