Add an object model to clientIFmaster
commit60ee53bbf4d862d9be19d2e9f7b13ce15724a997
authorAdam Litke <agl@us.ibm.com>
Fri, 16 Dec 2011 15:26:17 +0000 (16 09:26 -0600)
committerDan Kenigsberg <danken@redhat.com>
Tue, 31 Jan 2012 11:01:14 +0000 (31 06:01 -0500)
tree9ab03b5e252d20db34c97ee5b2098508cd679d45
parent6d286ff0d8cf78678cfee00e3490f538b04444a8
Add an object model to clientIF

Create an object-based API for vdsm.  The current objects are: Task,
StoragePool, StorageDomain, Image, Volume, ISCSIConnection, LVMVolumeGroup, and
VM.  Additionally, a Global object currently handles APIs which don't map nicely
to one of the above objects.  Right now this interface is only an abstraction
that maps directly to the flat function namespace.  This will change later in
the patch series and more over time.  Since this API is internal (it only
affects bindings), we can continue to change it over time without affecting
ovirt-engine.

Change-Id: I2ee54277c87a02ac8dafe29a8761e2acf0f7397f
Signed-off-by: Adam Litke <agl@us.ibm.com>
Reviewed-on: http://gerrit.ovirt.org/984
Reviewed-by: Dan Kenigsberg <danken@redhat.com>
Tested-by: Dan Kenigsberg <danken@redhat.com>
vdsm.spec.in
vdsm/API.py [new file with mode: 0644]
vdsm/Makefile.am