Hi,
I wrote the queuing code for monitoring services and so on for exceptions.
So, now if someone were to give a repeating operation to it, it would
execute it repeatedly until it fails or was cancelled. It would also
make sure that when new operations come in that only one at a time is
performed on the same resource. And, oh yeah, the OCF resource agents
I've implemented a few days ago can also, start, stop, restart and
migrate resources (for those that support it).
Two things still remain...
1) Code in the nanoprobes to receive a packet and give it to this
queueing code, and send a reply packet when it terminates (one way or
another).
2) Code in the CMA to send such a packet, and log something when it gets
a failure return.
There are a couple of remaining issues...
Should this code be modified to also be able to perform discovery
operations - eliminating the existing code for that purpose?
Exactly how to handle the case of noticing when something gets better
after failing...
Currently the code stops repeating the operation when it succeeds. I
just need to think about exactly how I want this case to work -- and
keep in mind the possibility of the repeating discovery case - where we
want to only send something back when something changes...
I have some test code for this, but I need to see if I can think of some
more test cases to write.
G'night! Tomorrow's my birthday.
-- Alan Robertson
[email protected]
_______________________________________________
Assimilation mailing list - Discovery-Driven Monitoring
[email protected]
http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation
http://assimmon.org/
