nagaina: Mon Dec 4 01:20:00 2006

Mon Dec 4 01:20:00 2006

"dependencies" break down into three categories:

• class-wide: "ssh requires ping", "ntp requires ping". These can probably go into the probe implementations directly. (That also simplifies the "http requires ping" case, where the ping target is only part of the http target.
• instance-wide: "ping remote-host requires ping router". These clearly need to be in the config file, but need a clear non-repetitive syntax.
• category-wide: "http thisurl requires this batch of afsXX tests to pass". This is trickier mostly in terms of grouping the afs tests.

Since the latter two require some naming cleverness, I'll let them stew and just implement class-wide requirements for now. It looks like ping is the only thing that actually works as a target, which simplifies things further...

So now we have a set() of results to test against, of which only "DOWN machinename" is currently implemented, and a decorator to fail a test if self.machine is listed as DOWN. This means the pings have to be explicitly run first for them to matter. Also, this underlying structure should be easy to use for instance prerequistes, once I figure out how to name them.

Future additions:

• more bad_probes tests for the rest of the ping dependencies
• modify notifier to complain differently (or not at all) for untested