with it.There is a bit of work that needs to be done in order to merge it but you can take a look at start to playThere is a bit of ongoing work to provide jsonrpc client for vdsm and you can code how to use it here [1].to define api interface between the engine and vdsm with validation on both sides.We need to update the API docs that we have and there is a bit of work (hopefully) scheduled for 4.0Sandro,The API hasn't changed between xmlrpc and jsonrpc. The only difference is format how we provide it.
On Wed, Oct 7, 2015 at 3:21 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:Hi,I'm looking at Bug 1228641 - [RFE] Switch from XML-RPC to JSON-RPC API and I'm searching google about "vdsm json rpc API documentation" without success.I've seen /usr/share/doc/vdsm-jsonrpc/vdsm-api.html shipped within vdsm-jsonrpc rpm but it doesn't explain how to use the api./usr/lib/python2.7/site-packages/vdsmapi.py looks useless/usr/share/vdsm/rpc/ are not public API but something only vdsm process should use.The feature pages http://www.ovirt.org/Features/Design/JsonRpc3.5 and http://www.ovirt.org/Features/Design/JsonRpc are incomplete or outdated and miss proper testing section specifying how to test the API.VDSM API pages are outdated or incomplete:Any hint on how to use VDSM JSON RPC API anywhere?Can someone please write a clear VDSM API reference documentation?Piotr, as a kickstart, can you give me a code sample for connecting to vdsm and call getVdsCaps using jsonrpc?Thanks,--Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com