Change in vdsm[master]: API: Separate clientIF and the xmlrpc server

agl at us.ibm.com agl at us.ibm.com
Thu Dec 15 21:04:25 UTC 2011


Adam Litke has uploaded a new change for review.

Change subject: API: Separate clientIF and the xmlrpc server
......................................................................

API: Separate clientIF and the xmlrpc server

Currently the xmlrpc server functionality is entwined with the clientIF class.
In order to proceed with the API bridge plan (http://ovirt.org/wiki/Vdsm_API) I
would like to separate the xmlrpc server into its own class.  This brings
clientIF one step closer to becoming a generic API Bridge that is able to host
additional bindings such as REST and QMF.

Despite the size of this patch, this was a pretty simple refactoring.  I made
the following choices as I split this out:

- The xmlrpc server binding class has start() and prepareForShutdown() APIs
- clientIF will still own the storage dispatcher but API wrapper mechanisms
  have moved into the xmlrpc class.

Change-Id: I5026e11f3d39343c957b59606e90c23acbb598ba
Signed-off-by: Adam Litke <agl at us.ibm.com>
---
M vdsm/clientIF.py
1 file changed, 137 insertions(+), 110 deletions(-)


  git pull ssh://gerrit.ovirt.org:29418/vdsm refs/changes/20/620/1
--
To view, visit http://gerrit.ovirt.org/620
To unsubscribe, visit http://gerrit.ovirt.org/settings

Gerrit-MessageType: newchange
Gerrit-Change-Id: I5026e11f3d39343c957b59606e90c23acbb598ba
Gerrit-PatchSet: 1
Gerrit-Project: vdsm
Gerrit-Branch: master
Gerrit-Owner: Adam Litke <agl at us.ibm.com>


More information about the vdsm-patches mailing list