[Zenoss-dev] Re: How to monitor water pumps?

[wairoa]

Thanks for the quick reply and sorry that I wasn't following up earlier. I did quite a bit more reading and the infrastructure we are building around the water pumps is becoming clearer. 

What we are going to have is a central controller which communicates with the pumps That controller has a REST interface to receive commands and can call a REST interface to report the status of the pumps.

>From my reading of the developer manual it seems that we would add zProperties to the existing Device class or subclass that to keep things in one place so we can track future Zenoss releases.

Each pump has its own location, which means a one-to-one relationship between Device and Location leading to a lot of locations but that shouldn't be a problem. The location hierarchy will be still useful as the pumps are clustered. 

The only tricky part I'm seeing is around the schedule. Each cluster of pumps is associated with a schedule on when the pumps should be switched on and for how long. That will happen more than once a day, but not every day. There will most likely be only a small number of schedules with many pump clusters associated to the same schedule. Now it would be nice to manage the schedule through Zenoss, but the more important requirement initially and appropriate for a management system is to raise an alarm if a pump is reported off when it's supposed to be on and vice-versa.

What would be the best strategy to adapt Zenoss to what I have sketched out here? I have looked through the code and it's much easier and cleaner than I though - great work - and I also managed to debug my first python program (unrelated to this) the other day. I have been working with scripting languages for many, many years, but python somehow always confused me without knowing really why.

Anyway, any help would be greatly appreciated.




-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=15009#15009

-------------------- m2f --------------------