Re: [ovirt-devel] Publicly available REST documentation

On Jan 4, 2017 6:08 PM, "Petr Horacek" wrote: Hello again, built master documentation is available on [1], latest 4.1 and 4.0 tags on [2] and [3] (these two were created manually, automated build will be triggered by a next tag). [1]

Re: [ovirt-devel] Heads-up: moving Libvirt xml creation to the engine

Thanks for feedback, this is WIP, early stage, so your comments and your time to think about it is much appreciated. few comments/arguments/thoughts below On 04 Jan 2017, at 20:01, Yevgeny Zaspitsky wrote: I agree with Piotr: - having engine uses libvirt xml would

Re: [ovirt-devel] Publicly available REST documentation

> On 04 Jan 2017, at 17:08, Petr Horacek wrote: > > Hello again, built master documentation is available on [1], latest > 4.1 and 4.0 tags on [2] and [3] (these two were created manually, > automated build will be triggered by a next tag). Thanks, Petr! I missed that a lot!

Re: [ovirt-devel] Heads-up: moving Libvirt xml creation to the engine

I agree with Piotr: - having engine uses libvirt xml would impose coupling between engine and libvirt (a cross-layers dependency), which currently does not exist. - moreover, engine would be coupled to all versions of libvirt api that it manages - currently each VDSM version knows how

Re: [ovirt-devel] Publicly available REST documentation

On 01/04/2017 05:08 PM, Petr Horacek wrote: > Hello again, built master documentation is available on [1], latest > 4.1 and 4.0 tags on [2] and [3] (these two were created manually, > automated build will be triggered by a next tag). > > [1] http://ovirt.github.io/ovirt-engine-api-model/master/ >

Re: [ovirt-devel] Publicly available REST documentation

Hello again, built master documentation is available on [1], latest 4.1 and 4.0 tags on [2] and [3] (these two were created manually, automated build will be triggered by a next tag). [1] http://ovirt.github.io/ovirt-engine-api-model/master/ [2] http://ovirt.github.io/ovirt-engine-api-model/4.1/

[ovirt-devel] The feature everyone was asking for is finally here...

FYI, After many requests from multiple developers and testers, the oVirt CI added a new simple job that lets you run the full fledged end-to-end oVirt system tests with a click of a button. You can read all the details and how-to in the new oVirt blog [1]. We wanted to allow running oVirt system

Re: [ovirt-devel] Manageiq ova upload is failing

You can only upload the OVA disk and attach it to a VM with 4.1. Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: yd...@redhat.com IRC : ydary On Wed, Jan 4, 2017 at 10:53 AM,

Re: [ovirt-devel] how does findbugs work?

On Wed, Jan 4, 2017 at 10:37 AM, Michal Skrivanek < michal.skriva...@redhat.com> wrote: > > On 21 Dec 2016, at 12:23, Eyal Edri wrote: > > You can see from the output the maven plugin is running [1], > Have you checked the filters that are ignoring 'false positives'? maybe >

Re: [ovirt-devel] [ovirt-users] Lowering the bar for wiki contribution?

On Wed, Jan 4, 2017 at 12:41 PM, Roy Golan wrote: > > > On 4 January 2017 at 12:17, Maor Lipchuk wrote: >> >> >> >> On Wed, Jan 4, 2017 at 11:38 AM, Daniel Erez wrote: >>> >>> >>> >>> On Wed, Jan 4, 2017 at 9:57 AM, Roy Golan

Re: [ovirt-devel] [ovirt-users] Lowering the bar for wiki contribution?

On 4 January 2017 at 12:17, Maor Lipchuk wrote: > > > On Wed, Jan 4, 2017 at 11:38 AM, Daniel Erez wrote: > >> >> >> On Wed, Jan 4, 2017 at 9:57 AM, Roy Golan wrote: >> >>> I'm getting the feeling I'm not alone in this, authoring and

Re: [ovirt-devel] [ovirt-users] Lowering the bar for wiki contribution?

On Wed, Jan 4, 2017 at 11:38 AM, Daniel Erez wrote: > > > On Wed, Jan 4, 2017 at 9:57 AM, Roy Golan wrote: > >> I'm getting the feeling I'm not alone in this, authoring and publishing a >> wiki page isn't as used to be for long time. >> >> I want to suggest

Re: [ovirt-devel] Can't find relative path for class "org.ovirt.engine.api.resource.VmDisksResource", will return null

Thanks Juan. Opening. On Wed, Jan 04 2017, Juan Hernández wrote: > On 01/04/2017 10:09 AM, Pavel Zhukov wrote: >> >> Hello, >> >> In ovirt-system-tests results I can see engine log is flooded with messages >> like: >> 147: 40147:2017-01-03 21:45:13,837-05 ERROR >>

Re: [ovirt-devel] Lowering the bar for wiki contribution?

On Wed, Jan 4, 2017 at 9:57 AM, Roy Golan wrote: > I'm getting the feeling I'm not alone in this, authoring and publishing a > wiki page isn't as used to be for long time. > > I want to suggest a bit lighter workflow: > > 1. Everyone can merge their page - (it's a wiki) >

Re: [ovirt-devel] Lowering the bar for wiki contribution?

On 4 January 2017 at 11:06, Nir Soffer wrote: > On Wed, Jan 4, 2017 at 10:51 AM, Barak Korren wrote: > > On 4 January 2017 at 09:57, Roy Golan wrote: > >> I'm getting the feeling I'm not alone in this, authoring and publishing > a > >>

Re: [ovirt-devel] Can't find relative path for class "org.ovirt.engine.api.resource.VmDisksResource", will return null

On 01/04/2017 10:09 AM, Pavel Zhukov wrote: > > Hello, > > In ovirt-system-tests results I can see engine log is flooded with messages > like: > 147: 40147:2017-01-03 21:45:13,837-05 ERROR > [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-22) [] Can't > find relative path

[ovirt-devel] Can't find relative path for class "org.ovirt.engine.api.resource.VmDisksResource", will return null

Hello, In ovirt-system-tests results I can see engine log is flooded with messages like: 147: 40147:2017-01-03 21:45:13,837-05 ERROR [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-22) [] Can't find relative path for class "org.ovirt.engine.api.resource.VmDisksResource",

Re: [ovirt-devel] Lowering the bar for wiki contribution?

On Wed, Jan 4, 2017 at 10:51 AM, Barak Korren wrote: > On 4 January 2017 at 09:57, Roy Golan wrote: >> I'm getting the feeling I'm not alone in this, authoring and publishing a >> wiki page isn't as used to be for long time. > > Maybe we're using the wrong

Re: [ovirt-devel] Manageiq ova upload is failing

On Wed, Jan 4, 2017 at 9:39 AM, Piotr Kliczewski wrote: > On Wed, Jan 4, 2017 at 6:51 AM, Michal Skrivanek > wrote: > >> On 03 Jan 2017, at 23:59, Piotr Kliczewski > wrote: > >> > >> All, > >> > >> I want to upload

Re: [ovirt-devel] Lowering the bar for wiki contribution?

On 4 January 2017 at 09:57, Roy Golan wrote: > I'm getting the feeling I'm not alone in this, authoring and publishing a > wiki page isn't as used to be for long time. Maybe we're using the wrong tool for the job? The site is intentionally not a wiki to allow OSAS some

Re: [ovirt-devel] Manageiq ova upload is failing

On Wed, Jan 4, 2017 at 6:51 AM, Michal Skrivanek wrote: >> On 03 Jan 2017, at 23:59, Piotr Kliczewski >> wrote: >> >> All, >> >> I want to upload manageiq ova from [1] when I attempted to do it I see: >> >> on the engine side: >> >> 2017-01-03

Re: [ovirt-devel] how does findbugs work?

> On 21 Dec 2016, at 12:23, Eyal Edri wrote: > > You can see from the output the maven plugin is running [1], > Have you checked the filters that are ignoring 'false positives'? maybe those > needs to be updated? > > The are in the 'exclude-filters.xml' files under each

Re: [ovirt-devel] Lowering the bar for wiki contribution?

On Wed, Jan 4, 2017 at 9:57 AM, Roy Golan wrote: > I'm getting the feeling I'm not alone in this, authoring and publishing a > wiki page isn't as used to be for long time. > Indeed. Several changes in the process have made it more difficult than it probably should be. > > I

Re: [ovirt-devel] Lowering the bar for wiki contribution?

On Wed, Jan 4, 2017 at 8:57 AM, Roy Golan wrote: > I'm getting the feeling I'm not alone in this, authoring and publishing a > wiki page isn't as used to be for long time. > > I want to suggest a bit lighter workflow: > > 1. Everyone can merge their page - (it's a wiki) >

Re: [ovirt-devel] Lowering the bar for wiki contribution?

On 04/01/17 09:57 +0200, Roy Golan wrote: I'm getting the feeling I'm not alone in this, authoring and publishing a wiki page isn't as used to be for long time. I want to suggest a bit lighter workflow: 1. Everyone can merge their page - (it's a wiki) Same as with (public and open) code, no