[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? TIA Karli Sjöberg ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] oVirt SDK v4 backwards compatibility
- Original Message - > From: "Karli Sjöberg" > 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. > 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
Re: [ovirt-users] oVirt SDK v4 backwards compatibility
Den 7 nov. 2016 15:53 skrev Rafael Martins : > > - Original Message - > > From: "Karli Sjöberg" > > 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? /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
Re: [ovirt-users] oVirt SDK v4 backwards compatibility
- Original Message - > From: "Karli Sjöberg" > To: "Rafael Martins" > 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 : > > > > - Original Message - > > > From: "Karli Sjöberg" > > > 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? 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
Re: [ovirt-users] oVirt SDK v4 backwards compatibility
- Original Message - > From: "Rafael Martins" > To: "Karli Sjöberg" > 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" > > To: "Rafael Martins" > > 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 : > > > > > > - Original Message - > > > > From: "Karli Sjöberg" > > > > 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 > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] oVirt SDK v4 backwards compatibility
On Tue, 2016-11-08 at 02:20 -0500, Tomas Jelinek wrote: > > - Original Message - > > From: "Rafael Martins" > > To: "Karli Sjöberg" > > 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" > > > To: "Rafael Martins" > > > 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 : > > > > > > > > ----- Original Message - > > > > > From: "Karli Sjöberg" > > > > > 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 Ah, I see. OK, that answers my question pretty clearly, correct me if I'm wrong; for anyone who wishes to write something in python, you have two SDK's installed (or, talk to the API directly) and check the API version to determine which SDK you should use? Is there a standard ("correct") way of checking the API version? /K > > > > > 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 > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] oVirt SDK v4 backwards compatibility
On 11/07/2016 07:06 PM, Rafael Martins wrote: > - Original Message - >> From: "Karli Sjöberg" >> To: "Rafael Martins" >> 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 : >>> >>> - Original Message - >>>> From: "Karli Sjöberg" >>>> 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? > > 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. > It is important to understand the following: * There are two different versions of the API: version 3 and version 4. * Version 3 of the engine implements only version 3 of the API. * Version 4 of the engine implements versions 3 and 4 of the API. This is the current situation. In version 4.2 we will probably drop suport for version 3 of the API completely. * Version 3 of the SDK implements only version 3 of the SDK. The name of the package is "ovirt-engine-sdk-python". * Version 4 of the SDK implements only version 4 of the SDK. The name of the package is "python-ovirt-engine-sdk4". In your specific use case, version 4.0.3 of the "python-ovirt-engine-sdk4" package can't talk to version 3.6.X of the engine. But as Rafael says, you can install version 3 of the SDK, the "ovirt-engine-sdk-python" package, and then it will version 3.6.X of the engine. -- 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. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users