[Ovirt-devel] Managed Node qpid Modeling

[Bryan Kearney]

Ian Main wrote:
> So here's what I've come up with so far.  I have run this past a few folks and hopefully it's in a reasonable shape now.  I suspect there may be some aspects that are lacking or need changing but that's what lots of eyes are for. :)  Also once we get into implementation it'll flesh itself out.
> 
> For those who haven't seen this yet, this is an XML markup for qpid modeling.  qpid is an implementation of the AMQP specification, see http://cwiki.apache.org/qpid/ for more information.  The modeling aspect is pretty new and I don't know if there's any good documentation on it yet.  It's also not released yet so I guess that's to be expected.. :)
> 
> This defines a model or object oriented API that taskomatic will use to talk to the managed nodes.  Properties are updated when set on the nodes and statistics are pushed at a regular interval.  Methods can be called asynchronously or synchronously.  
> 
> The idea is to unify our communications between the nodes and wui with qpid modeling.  If you look at what is available here and what taskomatic, host-status, host-collect and even some of ovirt-identify-node do, you'll see that's pretty much all contained within this model/API.
> 
> So please take a look and feel free to post questions or comments.
> 
> Thanks!
> 
> 	Ian
> 

This seems to combine state with RPC syntax. Any way of breaking those 
out into seperate schemas?

-- bk