slmiller wrote: > Yes, you're correct, responding correctly to stimulus is all that is needed, > there's nothing that mandates python. > > Beyond that, I'm no help, I failed to figure out how to successfully model > devices via ssh when I originally setup my zenoss monitoring box long ago. I > know it can be done, but I never figured it out... >
I am trying to read through the code now and puzzle it out. The information in the 2.3 Developer's Guide in section 11 helps a little, but there's still a missing link in my understanding. I'm pretty sure the SSH configuration is correct because I get results from the zenoss.cmd.uname plugin and I can see zenmodeler describing its interaction with the DSA key material via SshClient. However, I get no other response unless the device has the Zenoss Plugins installed - not even an error telling me to get stuffed. For example, I have configured one of my non-Linux devices to have the zenoss.cmd.linux.memory plugin along with the zenoss.cmd.uname plugin. When I force zenmodeler to run, only the 'uname' plugin is executed, which is in contrast to a Linux device, which gets them all run, and gives me a clear error when it can't run because the device is unreachable. Moreover, there's no evidence that the 'uname' plugin actually updated anything in the model even after running apparently successfully. So I'm still at a loss to figure out how to bridge the concept gap. I have a feeling that somewhere the results of the zenoss.cmd.uname command are being used to determine how zenmodeler behaves, but I can't figure it out. Otherwise, I can't make any sense of the inability of the modeler to at least attempt to use the zenoss.cmd.linux.* plugins. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=28541#28541 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
