Ashley Penney wrote:
I think some really interesting things could be done around a much
more flexible require => infrastructure that would allow various
things such as global requires, requires that trigger tests in some
fashion on other hosts. I could conceive of some kind of
functionality whereby test{} exists in modules and provides a method
by which you can check some functionality is working. You would then
be able to trigger a test{} on another host and get back true/false
with which puppet could decide if it should skip some action on the
original node. I guess there are many more flexible and undoubtedly
better ways to do this but it would seem to be closest to the puppet
way that would allow you to test and rely on other functionality being
in place.
I like the idea of being able to support arbitrary tests for
redlight-greenlight type status (could be very nice for dashboard,
too... lightweight monitoring!).
I'm not entirely sure yet whether that requires requires [sic] though,
or tests should cause automated behavior.
Testing could just be a separately triggered system.
Teyo has pointed out before there's something a bit odd about using
Puppet to test Puppet, but in this case, we're using puppet's existing
(and solved) secure communications system to extend it into monitoring
territory.
I like this.
If you've got more info on what tests might trigger, I'd be interested
in hearing that.
--
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.
