<div dir="ltr">Any decision made?<div>Are we going to switch to use 3.6 SDK?</div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 10, 2016 at 3:57 PM, Juan Hernández <span dir="ltr"><<a href="mailto:jhernand@redhat.com" target="_blank">jhernand@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 02/10/2016 04:21 PM, Yaniv Kaul wrote:<br>
> Currently, the SDK that Lago uses is (at least on my Fedora):<br>
> ovirt-engine-sdk-python-3.5.1.0-2.fc23.noarch<br>
><br>
> I think we may need to bring in a newer SDK.<br>
> 1. Which one?<br>
<br>
</span>Latest 3.6 that is available. Should be 3.6.0.3 if you have the<br>
oVirt.org repositories correctly configured.<br>
<span class=""><br>
> 2. If master - is it backward compatible to run against 3.x already?<br>
<br>
</span>The master version of the SDK only works with version 4 of the API, and<br>
thus only with master version of the engine. I do not recommend to use<br>
the master version of the SDKs at the moment, as we should do big<br>
changes to them, which will render the migration effort useless.<br>
<br>
The master version of the engine already supports versions 3 and 4 of<br>
the API. You can use version 3.6 of the SDK to talk to version 4 of the<br>
engine if you explicitly request version 3 of the API. To do so,<br>
currently, you will have to use a prefix in the URL:<br>
<br>
api = api.API(<br>
url="<a href="https://whatever/ovirt-engine/api/v3" rel="noreferrer" target="_blank">https://whatever/ovirt-engine/api/v3</a>",<br>
...<br>
)<br>
<br>
Note that using this prefix isn't the recommended way to select the<br>
version of the API, the recommended way is using the HTTP "Version"<br>
header, but there are no released versions of the SDK supporting this<br>
yet. This support will be included in the next released version.<br>
<span class=""><br>
> 3. Can we have them side by side perhaps?<br>
><br>
<br>
</span>It isn't possible to have both SDKs installed in the same machine,<br>
because the name of the RPM is the same. Suggestions to allow that are<br>
welcome. I'm inclined to ship two SDKs in the same RPM, one to talk to<br>
version 3 of the API and another to talk to version 4 of the API.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta<br>
3ºD, 28016 Madrid, Spain<br>
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.<br>
_______________________________________________<br>
lago-devel mailing list<br>
<a href="mailto:lago-devel@ovirt.org">lago-devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/lago-devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/lago-devel</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>Eyal Edri<br>Associate Manager<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div>
</div>