Le 6 avr. 2017 =C3=A0 15:32, Yaniv Kaul <ykaul@redhat.com> a =C3=A9crit = : =20 =20 =20 On Thu, Apr 6, 2017 at 3:58 PM, Fabrice Bacchella = <fabrice.bacchella@orange.fr <mailto:fabrice.bacchella@orange.fr>> = wrote: Yes I'm starting to understand that thinking about migrating code is =
=20 The old skd3 code is just good to be thrown away. There is no hope =
--Apple-Mail=_0D1EAE83-E7CC-445A-919C-CCDFCBE51B20 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 pointless. 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.
=20 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.
=20 =20 Another option that you can consider, if you are re-writing, is = automation via Ansible.=20 See = https://github.com/ansible/ansible-modules-extras/tree/devel/cloud/ovirt = <https://github.com/ansible/ansible-modules-extras/tree/devel/cloud/ovirt>= =20
A lot of people don't use ansible or use concurrent tools. So no that's = not an option. --Apple-Mail=_0D1EAE83-E7CC-445A-919C-CCDFCBE51B20 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div = class=3D"">Le 6 avr. 2017 =C3=A0 15:32, Yaniv Kaul <<a = href=3D"mailto:ykaul@redhat.com" class=3D"">ykaul@redhat.com</a>> a = =C3=A9crit :</div><br class=3D"Apple-interchange-newline"><div = class=3D""><div dir=3D"ltr" class=3D""><br class=3D""><div = class=3D"gmail_extra"><br class=3D""><div class=3D"gmail_quote">On Thu, = Apr 6, 2017 at 3:58 PM, Fabrice Bacchella <span dir=3D"ltr" = class=3D""><<a href=3D"mailto:fabrice.bacchella@orange.fr" = target=3D"_blank" class=3D"">fabrice.bacchella@orange.fr</a>></span> = wrote:<br class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0px= 0px 0px 0.8ex;border-left:1px solid = rgb(204,204,204);padding-left:1ex"><div style=3D"word-wrap:break-word" = class=3D"">Yes I'm starting to understand that thinking about migrating = code is pointless.<div class=3D""><br class=3D""></div><div class=3D"">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.</div></div></blockquote><div class=3D""><br class=3D""></div><div = class=3D"">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).</div></div></div></div></div></blockquote><div><br = class=3D""></div>Easy to write code that a well though sdk should have = provided.</div><div><br class=3D""><blockquote type=3D"cite" = class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div = class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D""> Note = that right now you can mix between v3 and v4, so you can migrate slowly, = function by function.</div></div></div></div></div></blockquote><div><br = class=3D""></div><div>That's a possible but almost as complicated as = rewrite everything in my case.</div><div><br class=3D""></div><blockquote = type=3D"cite" class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div = class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D""><br = class=3D""></div><div class=3D""><br class=3D""></div><div = class=3D"">Another option that you can consider, if you are re-writing, = is automation via Ansible. </div><div class=3D"">See <a = href=3D"https://github.com/ansible/ansible-modules-extras/tree/devel/cloud= /ovirt" = class=3D"">https://github.com/ansible/ansible-modules-extras/tree/devel/cl= oud/ovirt</a> </div></div></div></div></div></blockquote><br = class=3D""></div><div>A lot of people don't use ansible or use = concurrent tools. So no that's not an option.</div><br = class=3D""></body></html>= --Apple-Mail=_0D1EAE83-E7CC-445A-919C-CCDFCBE51B20--