Re: [ovirt-devel] [VDSM][JSON RPC] new vdsClient?
On Fri, Nov 14, 2014 at 5:52 PM, Nir Soffer <nsoffer(a)redhat.com> wrote:
----- Original Message -----
> From: "Francesco Romani" <fromani(a)redhat.com>
> To: devel(a)ovirt.org
> Sent: Friday, 14 November, 2014 6:34:57 PM
> Subject: [ovirt-devel] [VDSM][JSON RPC] new vdsClient?
>
> Hi everyone,
>
> the recent JSONRPC discussion and my last work around vdsClient reminded me
> that
> since a long time there it was vague plans for a vdsClient overhaul
>
> or at least I haven't ever found a detailed plan :)
>
> Since we have to add jsonrpc support anyway, it could be a good chance to
> bootstrap
> a new vdsClient, and incrementally enhance it as needs arises; the old
> vdsClient will
> not go away very soon, I guess.
>
> At least, we can to put together a wishlist for a new vdsClient and add it to
> the wiki.
>
> My one, so far:
> * client library package: we should have a program-friendly python package to
> access
> VDSM, in order
> * JSON for input: I's like to open logs, grab a line including a command and
> feed
> vdsClient with the very same line
Currently we don't see commands json input in the logs, but this can be a good
idea (in debug mode).
+1
JSON for output: current vdsClient format replies in a mix of text and json. We
need to print the json returned from vdsm as is.
I started discussion about it and here is what I was able to gather:
- we should start new vdsClient like tool which holds current vdsClient
command line interface.
- vdsClient should stay as it is and we can extend new client with additional
functionality as we need (adding debug mode etc)
- there was a suggestion to reuse ovirt-engine-cli ideas and it should
use schema
to determine the API
Nir
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel