On 03/04/2012 04:51 PM, Dan Kenigsberg wrote:
On Thu, Mar 01, 2012 at 09:38:41AM +0200, Michael Pasternak wrote:
> On 03/01/2012 07:44 AM, Deepak C Shetty wrote:
>> On 02/29/2012 08:38 PM, Michael Pasternak wrote:
>> I would like to see something similar for VDSM cli (vdsClient) :)
> if VDSM api will expose RSDL (RESTful service description language), we could
> generate SDK  for it and then very same cli can be used against this sdk
>  our ovirt-engine-sdk  is auto-generated from RSDL exposed in ovirt-engine-api
>  http://www.ovirt.org/wiki/SDK
REST API for Vdsm is in the works, http://gerrit.ovirt.org/2021
but I am not sure that mixing the layers and having one cli to Engine and Vdsm
it's not mixing of two CLIs, if vdsm will expose RSDL, will be generated vdsm sdk,
i.e cli will be completely different as it will work against vdsm sdk,
all I'm saying that if vdsm will expose RSDL, it will get sdk/cli for free ...
In fact, I would guess that Engine would not be surprised if you
spring a VM below its feet, or migrate an existing VM.
That's why vdsClient is considered and test and debug tool.
RedHat, ENG-Virtualization R&D