On May 18, 2010, at 11:30 PM, James Turnbull wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 19/05/10 3:39 PM, Luke Kanies wrote:
This wouldn't be all that difficult - just record each event as it
comes in, and remove it once it's dealt with. Then when Puppet
starts
up, it just deals with any un-dealt-with event, as it were.
We currently only queue events in memory, but it's not like it's a
huge architectural shift to record the events on disk.
+1. Perhaps also using the same principle of "complete",
"incomplete", "failed", "skipped" runs that a package management
tool like YUM does. Give users the option - rather than make it
mandatory to complete the events in a run if the previous one failed.
That would definitely be important, but I don't really know how the
interface of that would be handled. Track whether the user is on an
interactive console, and ask a question? Send a notice to the server
and update the dashboard or something?
Seems a bit complicated.
--
A conservative is a man who believes that nothing should be done for
the first time. --Alfred E. Wiggam
---------------------------------------------------------------------
Luke Kanies -|- http://puppetlabs.com -|- +1(615)594-8199
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" 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-dev?hl=en.