On Thu, Apr 6, 2017 at 3:58 PM, Fabrice Bacchella <fabrice.bacchella@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). Note that right now you can mix between v3 and v4, so you can migrate slowly, function by function.

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 

Y.



Le 6 avr. 2017 à 14:23, Yaniv Kaul <ykaul@redhat.com> a écrit :

There is documentation online (and within the project).

There are tens of examples in the RPM (and online).

HTH,
Y.

On Thu, Apr 6, 2017 at 12:22 PM, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:
I trying to migrate my python code from sdk3 to sdk4, is there any migration doc, documentation help about that ? Even google is unable to find anything relevant about that.

_______________________________________________
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