1:14 p.m.
On 11/20/2012 09:09 PM, Morrissey, Christopher wrote:
> -----Original Message-----
> From: Itamar Heim [mailto:iheim@redhat.com]
> Sent: Tuesday, November 20, 2012 2:07 PM
> To: Saggi Mizrahi
> Cc: Morrissey, Christopher; engine-devel(a)ovirt.org
> Subject: Re: [Engine-devel] Registering an existing disk or VM through the
> REST API
>
> On 11/20/2012 05:06 PM, Saggi Mizrahi wrote:
>> Please don't use the REST API it's being deprecated
>> http://gerrit.ovirt.org/#/c/7754/
>>
>> We are in a transition to a stable supported API.
>> Until then please use the XML-RPC API which thought not supported is the
> more stable of the two.
>
> Saggie is talking about the vdsm rest api.
> Chris, I'm pretty sure you are planning to add it to the Engine REST API, to
> allow consuming this verb via an engine UI plugin?
>
Yes, Itamar. George and I were very confused for a while, but as I looked at the patch
pointed to above it appears there is a separate REST API for VDSM. So, just to be clear is
there any separate XML RPC API for the Engine or REST is all there is and no plans to
change in the future?
Engine communicates with VDSM today via XML-RPC.
there was work to move VDSM to a newer API, based on REST.
this was abandoned, and focus is moving to JSON messages based API instead.
(you'd be using this api when your engine side patch will be calling the
VDSM method for domain scan, but the xml-rpc part of it is probably
abstracted in the engine from you).
in any case, this is *all* engine-vdsm side, and unrelated to the Engine
REST API, which there are no plans to deprecate.
>
>>
>> ----- Original Message -----
>>> From: "Christopher Morrissey"
<Christopher.Morrissey(a)netapp.com>
>>> To: engine-devel(a)ovirt.org
>>> Sent: Tuesday, November 20, 2012 9:18:26 AM
>>> Subject: [Engine-devel] Registering an existing disk or VM through the
> REST API
>>>
>>>
>>>
>>>
>>>
>>> Hi All,
>>>
>>>
>>>
>>> As many of you know, we’re working on adding a plugin to oVirt for
>>> NetApp storage controllers. The plugin will allow users to add a new
>>> storage domain and rapidly clone VMs using the native ONTAP APIs.
>>> Our plan is to do this outside of oVirt in a separate engine and
>>> then register the new storage domain or cloned VMs through the REST
>>> API.
>>>
>>>
>>>
>>> I’ve been going through the oVirt code and I’m not able to find a way
>>> to register an existing VM or disk through the REST API. Am I
>>> missing something or is this functionality that needs to be added?
>>> As part of the cloning process we can generate new UUIDs for the
>>> cloned disks and images, but I don’t see a way to get them
>>> recognized by oVirt.
>>>
>>>
>>>
>>> This functionality is very important to moving forward on our plugin
>>> and I can certainly help add this capability if needed.
>>>
>>>
>>>
>>> -Chris
>>>
>>>
>>>
>>> Chris Morrissey
>>>
>>> Software Engineer
>>>
>>> NetApp Inc.
>>>
>>> 919.476.4428
>>>
>>>
>>> _______________________________________________
>>> Engine-devel mailing list
>>> Engine-devel(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>>
>> _______________________________________________
>> Engine-devel mailing list
>> Engine-devel(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>
>