reposting to list
---
I know it might seem a bit of a cumbersome process. But installation is relatively simple
nowadays and the API is a lot more stable and safe at the moment.
Because VDSM doesn't keep any information on the host you will end up having to
develop your own solutions to problems already solved by the ovirt-engine.
You only need to use the VDSM API if you write your own management solution. But seeing as
the ovirt-engine is open source there should be no reason not to just write the feature
you need and push it upstream.
----- Original Message -----
From: "Paolo Tonin" <paolo.tonin(a)gmail.com>
To: "Saggi Mizrahi" <smizrahi(a)redhat.com>
Sent: Monday, August 20, 2012 11:33:50 AM
Subject: Re: [vdsm] About vdsm rest api
Yes, because i don't want to install oVirt engine (and subsequely
entire oVirt web interface and DB)
2012/8/20 Saggi Mizrahi <smizrahi(a)redhat.com>:
> Hi, the rest API is going to move to a 2nd tier API very soon.
> There is also a pretty big API restructuring going on so we could
> supply a supported and documented API.
>
> Is there a reason you are not using the ovirt-engine REST-API?
>
> ----- Original Message -----
>> From: "Paolo Tonin" <paolo.tonin(a)gmail.com>
>> To: vdsm-devel(a)lists.fedorahosted.org
>> Sent: Thursday, August 16, 2012 10:00:41 PM
>> Subject: [vdsm] About vdsm rest api
>>
>> Hi all there!
>>
>> Is there any documentation about implemented http rest api in the
>> current version of VDSM (4.10)
>> I would to use vdsm without oVirt packages, actually i'm using
>>
>> # rpm -qa vdsm*
>> vdsm-xmlrpc-4.10.0-0.42.12.el6.noarch
>> vdsm-4.10.0-0.42.12.el6.x86_64
>> vdsm-rest-4.10.0-0.42.12.el6.noarch
>> vdsm-bootstrap-4.10.0-0.42.12.el6.noarch
>> vdsm-python-4.10.0-0.42.12.el6.x86_64
>> vdsm-reg-4.10.0-0.42.12.el6.noarch
>> vdsm-cli-4.10.0-0.42.12.el6.noarch
>>
>> Thanks a lot
>> _______________________________________________
>> vdsm-devel mailing list
>> vdsm-devel(a)lists.fedorahosted.org
>>
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
>>