----- Original Message -----
From: "Rafael Martins" <rmartins@redhat.com> To: "Karli Sjöberg" <karli.sjoberg@slu.se> Cc: users@ovirt.org Sent: Monday, November 7, 2016 7:06:33 PM Subject: Re: [ovirt-users] oVirt SDK v4 backwards compatibility
----- Original Message -----
From: "Karli Sjöberg" <karli.sjoberg@slu.se> To: "Rafael Martins" <rmartins@redhat.com> Cc: users@ovirt.org Sent: Monday, November 7, 2016 6:13:33 PM Subject: Re: [ovirt-users] oVirt SDK v4 backwards compatibility
Den 7 nov. 2016 15:53 skrev Rafael Martins <rmartins@redhat.com>:
----- Original Message -----
From: "Karli Sjöberg" <karli.sjoberg@slu.se> To: users@ovirt.org Sent: Monday, November 7, 2016 3:06:10 PM Subject: [ovirt-users] oVirt SDK v4 backwards compatibility
Heya!
Quick question, if I have on my computer installed a newer version Python SDK than what´s installed on the engine (4.0.3 locally and 3.6.X in engine), is it possible to connect?
It is not possible, but you can still install the RPM for the version 3 of the SDK. Please note that the code of the SDK versions is not compatible.
Ok, as I thought. But how does others handle that, like moVirt e.g? Is there a best-practice for backwards compatibility?
moVirt is not using the SDKs, it is talking to API directly. But the general rule for the clients (moVirt but also ManageIQ) works like this: - check the version of the API right at the beginning - according to the found version use either the new or the old api
Right now if you use the old SDK you should be able to "talk" with both 3.6 and 4.0, because 4.0 api provides backward compatibility with 3.6. But I'm not sure if you can rely on this. Juan may have more details for you.
Thanks, Rafael
/K
TIA Karli Sjöberg _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users