Re: [ovirt-users] SKD4

On Sun, Apr 9, 2017 at 1:27 PM, Fabrice Bacchella < fabrice.bacche...@orange.fr> wrote: > > > Le 9 avr. 2017 à 11:25, Yaniv Kaul a écrit : > > > > > However, I tend to agree with closing the bug - I'd create a library > (module) *on top of the SDK* . The comment in the bug is quite clear about >

Re: [ovirt-users] SKD4

> Le 9 avr. 2017 à 11:25, Yaniv Kaul a écrit : > > However, I tend to agree with closing the bug - I'd create a library (module) > *on top of the SDK* . The comment in the bug is quite clear about it: > "The objective of the SDK is to offer the same that the API offers, without > the burden o

Re: [ovirt-users] SKD4

On Sun, Apr 9, 2017 at 12:14 PM, Fabrice Bacchella < fabrice.bacche...@orange.fr> wrote: > > Le 6 avr. 2017 à 17:21, Ondra Machacek a écrit : > > > > On Thu, Apr 6, 2017 at 5:00 PM, Fabrice Bacchella < > fabrice.bacche...@orange.fr> wrote: > >> Ho my good, in ovirtsdk.services.py, for every servi

Re: [ovirt-users] SKD4

Hi Fabrice, I think you got proper explanation from Juan. I think you should indeed consider whether to use the sdk or not, depending on whether it fits your needs. Regards, Oved On Apr 9, 2017 12:14, "Fabrice Bacchella" wrote: Le 6 avr. 2017 à 17:21, Ondra Machacek a écrit : On Thu, Ap

Re: [ovirt-users] SKD4

> Le 6 avr. 2017 à 17:21, Ondra Machacek a écrit : > > > > On Thu, Apr 6, 2017 at 5:00 PM, Fabrice Bacchella > mailto:fabrice.bacche...@orange.fr>> wrote: > Ho my good, in ovirtsdk.services.py , for every > service, there is a different method with a different n

Re: [ovirt-users] SKD4

On Thu, Apr 6, 2017 at 9:19 PM, Fabrice Bacchella < fabrice.bacche...@orange.fr> wrote: > > Le 6 avr. 2017 à 20:06, Yaniv Kaul a écrit : > > > > On Thu, Apr 6, 2017 at 5:30 PM, Fabrice Bacchella < > fabrice.bacche...@orange.fr> wrote: > >> >> > Le 6 avr. 2017 à 16:12, Yaniv Kaul a écrit : >> >>

Re: [ovirt-users] SKD4

> Le 6 avr. 2017 à 20:06, Yaniv Kaul a écrit : > > > > On Thu, Apr 6, 2017 at 5:30 PM, Fabrice Bacchella > mailto:fabrice.bacche...@orange.fr>> wrote: > > > Le 6 avr. 2017 à 16:12, Yaniv Kaul > > a écrit : > > > Seriously though - perhaps you could borrow code from

Re: [ovirt-users] SKD4

> Le 6 avr. 2017 à 17:21, Ondra Machacek a écrit : > > > > On Thu, Apr 6, 2017 at 5:00 PM, Fabrice Bacchella > mailto:fabrice.bacche...@orange.fr>> wrote: > Ho my good, in ovirtsdk.services.py , for every > service, there is a different method with a different n

Re: [ovirt-users] SKD4

On Thu, Apr 6, 2017 at 5:30 PM, Fabrice Bacchella < fabrice.bacche...@orange.fr> wrote: > > > Le 6 avr. 2017 à 16:12, Yaniv Kaul 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

Re: [ovirt-users] SKD4

On Thu, Apr 6, 2017 at 5:00 PM, Fabrice Bacchella < fabrice.bacche...@orange.fr> wrote: > Ho my good, in ovirtsdk.services.py, for every service, there is a > different method with a different name that return a associated service, so > it's not possible to have a generic like: > > def resolve(se

Re: [ovirt-users] SKD4

On 6 April 2017 at 18:00, Fabrice Bacchella wrote: > Ho my good, in ovirtsdk.services.py, for every service, there is a different > method with a different name that return a associated service, so it's not > possible to have a generic like: > > def resolve(service, ...): > id = . > return se

Re: [ovirt-users] SKD4

Ho my good, in ovirtsdk.services.py, for every service, there is a different method with a different name that return a associated service, so it's not possible to have a generic like: def resolve(service, ...): id = . return service.service(id) because the generic call ser

Re: [ovirt-users] SKD4

> Le 6 avr. 2017 à 16:12, Yaniv Kaul a écrit : > > > > On Thu, Apr 6, 2017 at 4:49 PM, Fabrice Bacchella > mailto:fabrice.bacche...@orange.fr>> wrote: > >> Le 6 avr. 2017 à 15:32, Yaniv Kaul > > a écrit : >> >> >> >> On Thu, Apr 6, 2017 at 3:58 PM, Fabrice Bacchel

Re: [ovirt-users] SKD4

> Le 6 avr. 2017 à 16:12, Yaniv Kaul 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 ? ___ Us

Re: [ovirt-users] SKD4

On Thu, Apr 6, 2017 at 5:02 PM, Fabrice Bacchella < fabrice.bacche...@orange.fr> wrote: > > > Le 6 avr. 2017 à 15:47, Yaniv Kaul a écrit : > > > > > > > Perhaps in your case. Here[1] is an example of the ovirt system tests, > which were only partially converted (work in progress...) to v4 API. >

Re: [ovirt-users] SKD4

On Thu, Apr 6, 2017 at 4:49 PM, Fabrice Bacchella < fabrice.bacche...@orange.fr> wrote: > > Le 6 avr. 2017 à 15:32, Yaniv Kaul a écrit : > > > > On Thu, Apr 6, 2017 at 3:58 PM, Fabrice Bacchella < > fabrice.bacche...@orange.fr> wrote: > >> Yes I'm starting to understand that thinking about migrat

Re: [ovirt-users] SKD4

> Le 6 avr. 2017 à 15:47, Yaniv Kaul a écrit : > > > Perhaps in your case. Here[1] is an example of the ovirt system tests, which > were only partially converted (work in progress...) to v4 API. yes that really related to my use case. Another problem that I have with lack of documentation,

Re: [ovirt-users] SKD4

> Le 6 avr. 2017 à 15:32, Yaniv Kaul a écrit : > > > > On Thu, Apr 6, 2017 at 3:58 PM, Fabrice Bacchella > mailto:fabrice.bacche...@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. Th

Re: [ovirt-users] SKD4

On Thu, Apr 6, 2017 at 4:41 PM, Fabrice Bacchella < fabrice.bacche...@orange.fr> wrote: > > Le 6 avr. 2017 à 15:32, Yaniv Kaul a écrit : > > > > On Thu, Apr 6, 2017 at 3:58 PM, Fabrice Bacchella < > fabrice.bacche...@orange.fr> wrote: > >> Yes I'm starting to understand that thinking about migrat

Re: [ovirt-users] SKD4

> Le 6 avr. 2017 à 15:32, Yaniv Kaul a écrit : > > > > On Thu, Apr 6, 2017 at 3:58 PM, Fabrice Bacchella > mailto:fabrice.bacche...@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. Th

Re: [ovirt-users] SKD4

On Thu, Apr 6, 2017 at 3:58 PM, Fabrice Bacchella < fabrice.bacche...@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 t

Re: [ovirt-users] SKD4

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 exp

Re: [ovirt-users] SKD4

There is documentation online (and within the project). See http://ovirt.github.io/ovirt-engine-api-model/master/ There are tens of examples in the RPM (and online). See https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples HTH, Y. On Thu, Apr 6, 2017 at 12:22 PM, Fabrice Bacchella

[ovirt-users] SKD4

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