On 02/10/2016 04:21 PM, Yaniv Kaul wrote:
> Currently, the SDK that Lago uses is (at least on my Fedora):
> ovirt-engine-sdk-python-3.5.1.0-2.fc23.noarch
>
> I think we may need to bring in a newer SDK.
> 1. Which one?

Latest 3.6 that is available. Should be 3.6.0.3 if you have the
oVirt.org repositories correctly configured.

> 2. If master - is it backward compatible to run against 3.x already?

The master version of the SDK only works with version 4 of the API, and
thus only with master version of the engine. I do not recommend to use
the master version of the SDKs at the moment, as we should do big
changes to them, which will render the migration effort useless.

The master version of the engine already supports versions 3 and 4 of
the API. You can use version 3.6 of the SDK to talk to version 4 of the
engine if you explicitly request version 3 of the API. To do so,
currently, you will have to use a prefix in the URL:

  api = api.API(
    url="https://whatever/ovirt-engine/api/v3",
    ...
  )

Note that using this prefix isn't the recommended way to select the
version of the API, the recommended way is using the HTTP "Version"
header, but there are no released versions of the SDK supporting this
yet. This support will be included in the next released version.

> 3. Can we have them side by side perhaps?
>

It isn't possible to have both SDKs installed in the same machine,
because the name of the RPM is the same. Suggestions to allow that are
welcome. I'm inclined to ship two SDKs in the same RPM, one to talk to
version 3 of the API and another to talk to version 4 of the API.

--
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
_______________________________________________
lago-devel mailing list
lago-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/lago-devel