[ovirt-users] SKD4

[Fabrice Bacchella]

> Le 6 avr. 2017 à 15:32, Yaniv Kaul <ykaul at redhat.com> a écrit :
> 
> 
> 
> On Thu, Apr 6, 2017 at 3:58 PM, Fabrice Bacchella <fabrice.bacchella at orange.fr <mailto:fabrice.bacchella at orange.fr>> wrote:
> Yes I'm starting to understand that thinking about migrating code is pointless.
> 
> The old skd3 code is just good to be thrown away. There is no hope thinking about "migrating code". And as it's just a thin layer around REST calls, it's up to us to try to make something usable around that. So I expect a lot of sweat and tears to adapt my existing code.
> 
> Well, yes and no. Yes, it's not smooth, but once you 'get' the idea behind the v4 API philosophy, it's quite easy to write to (at least in Python).

Easy to write code that a well though sdk should have provided.

> Note that right now you can mix between v3 and v4, so you can migrate slowly, function by function.

That's a possible but almost as complicated as rewrite everything in my case.

> 
> 
> Another option that you can consider, if you are re-writing, is automation via Ansible. 
> See https://github.com/ansible/ansible-modules-extras/tree/devel/cloud/ovirt <https://github.com/ansible/ansible-modules-extras/tree/devel/cloud/ovirt> 

A lot of people don't use ansible or use concurrent tools. So no that's not an option.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170406/89015a8c/attachment.html>