On Thu, Apr 6, 2017 at 9:19 PM, Fabrice Bacchella <
fabrice.bacchella(a)orange.fr> wrote:
Le 6 avr. 2017 à 20:06, Yaniv Kaul <ykaul(a)redhat.com> a écrit :
On Thu, Apr 6, 2017 at 5:30 PM, Fabrice Bacchella <
fabrice.bacchella(a)orange.fr> wrote:
>
> > Le 6 avr. 2017 à 16:12, Yaniv Kaul <ykaul(a)redhat.com> a écrit :
>
> > Seriously though - perhaps you could borrow code from our Ansible
> module? See[1].
> >
>
> If the code already exists, why it's not already in the sdk instead of
> having to dig throw external code ?
It's a good question, which I've asked as well in the past. The reason is
that it's above the SDK, not part of the SDK.
But that doesn't matter - we really ought to have a module/library on top
of the SDK, that can be shared.
For example, between ovirt-system-tests, Ansible, oVirtBackup[1] and
several others who write on top of our SDK.
We just never got to generalise it enough and split it. You are welcome to
begin this work - I believe it has value.
(It's also a good Google Summer of Code project - I'll see if I can update
that page on
ovirt.org).
I have already started it for sdk3, I will need to restart if almost from
scratch to sdk4:
https://github.com/fbacchella/ovirtcmd and need to right
a lot of very basic code.
Well, if you are talking about a CLI, I've started one for SDK4[1]. It
exactly suffers from what I describe above - due to lack of a library on
top of the SDK I'm quite wastefully re-writing what others (for example,
the Ansible module) have probably done already.
But other than that, and the fact I stopped the effort, it's a very cool
CLI, I encourage you to check it out and perhaps pick it and do a better
job than me.
Y.
[1]
https://github.com/mykaul/ovirt4cli