Re: [ovirt-devel] Vdsm api package

Il 29/Mar/2016 20:12, "Nir Soffer" ha scritto: > > On Tue, Mar 29, 2016 at 9:09 PM, Sandro Bonazzola wrote: > > > > Il 29/Mar/2016 20:02, "Nir Soffer" ha scritto: > >> > >> Hi all, > >> > >> In the Vdsm call, we discussed a way to

Re: [ovirt-devel] new internal stable modules + proposal

On 29/03/16 20:36 +0300, Nir Soffer wrote: On Tue, Mar 29, 2016 at 7:44 PM, Martin Polednik wrote: On 29/03/16 11:12 -0400, Francesco Romani wrote: Hi, in the last Vdsm developer call we agreed to promote a few modules in the common repository. The common repository

Re: [ovirt-devel] Vdsm api package

On Tue, Mar 29, 2016 at 9:08 PM, Adam Litke wrote: > On 29/03/16 21:01 +0300, Nir Soffer wrote: >> >> Hi all, >> >> In the Vdsm call, we discussed a way to expose vdsm errors to its clients >> (e.g, engine, hosted engine agent/setup). >> >> The idea is to have a vdsmapi

Re: [ovirt-devel] Vdsm api package

On Tue, Mar 29, 2016 at 9:09 PM, Sandro Bonazzola wrote: > > Il 29/Mar/2016 20:02, "Nir Soffer" ha scritto: >> >> Hi all, >> >> In the Vdsm call, we discussed a way to expose vdsm errors to its clients >> (e.g, engine, hosted engine agent/setup). >> >>

Re: [ovirt-devel] Vdsm api package

Il 29/Mar/2016 20:02, "Nir Soffer" ha scritto: > > Hi all, > > In the Vdsm call, we discussed a way to expose vdsm errors to its clients > (e.g, engine, hosted engine agent/setup). > > The idea is to have a vdsmapi package, holding: > - errors.py - all public errors > -

Re: [ovirt-devel] Vdsm api package

On 29/03/16 21:01 +0300, Nir Soffer wrote: Hi all, In the Vdsm call, we discussed a way to expose vdsm errors to its clients (e.g, engine, hosted engine agent/setup). The idea is to have a vdsmapi package, holding: - errors.py - all public errors - events.py - all events sent by vdsm -

Re: [ovirt-devel] new internal stable modules + proposal

On Tue, Mar 29, 2016 at 7:44 PM, Martin Polednik wrote: > On 29/03/16 11:12 -0400, Francesco Romani wrote: >> >> Hi, >> >> in the last Vdsm developer call we agreed to promote a few modules in the >> common repository. >> The common repository provides the additional

Re: [ovirt-devel] new internal stable modules + proposal

On 29/03/16 11:12 -0400, Francesco Romani wrote: Hi, in the last Vdsm developer call we agreed to promote a few modules in the common repository. The common repository provides the additional guarantees over regular modules in lib/vdsm/ - stable API - (thus) safe to use across verticals the

Re: [ovirt-devel] [vdsm] new internal stable modules + proposal

- Original Message - > From: "Nir Soffer" > To: "Francesco Romani" > Cc: "devel" > Sent: Tuesday, March 29, 2016 6:00:56 PM > Subject: Re: [ovirt-devel] [vdsm] new internal stable modules + proposal > > On Tue, Mar 29, 2016 at

Re: [ovirt-devel] [vdsm] new internal stable modules + proposal

On Tue, Mar 29, 2016 at 6:12 PM, Francesco Romani wrote: > Hi, > > in the last Vdsm developer call we agreed to promote a few modules in the > common repository. > The common repository provides the additional guarantees over regular modules > in lib/vdsm/ > > - stable API >

[ovirt-devel] [vdsm] new internal stable modules + proposal

Hi, in the last Vdsm developer call we agreed to promote a few modules in the common repository. The common repository provides the additional guarantees over regular modules in lib/vdsm/ - stable API - (thus) safe to use across verticals the planned moves are: lib/vdsm/schedule.py ->

Re: [ovirt-devel] Hello and a question about QEMU log

Hi, The libvirt team would be better equipped to address that question, as that functionality is actually a part of that project. Their contact information can be found here: https://libvirt.org/contact.html. -Phillip Bailey On Sun, Mar 27, 2016 at 10:04 PM, zhukaijie wrote:

[ovirt-devel] Failing to run ovirt-system-tests using lago due to missing rpms

Hi, Anyone encountered these errors when running 3.6 basic suite on RHEL 7.2? * STDERR Error: Package: ovirt-engine-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-iso-uploader >= 3.6.0 Error: Package: ovirt-engine-3.6.4.1-1.el6.noarch (localsync) Requires: slf4j >=

Re: [ovirt-devel] Engine 3.6.5 has been branched out

- Original Message - > From: "Tal Nisan" > To: "devel" > Sent: Tuesday, March 29, 2016 2:03:48 PM > Subject: [ovirt-devel] Engine 3.6.5 has been branched out > > A new branch ovirt-engine-3.6.5 has been branched out from the > ovirt-engine-3.6 branch

Re: [ovirt-devel] [VDSM] Vdsm build requires now python 3 on EL7

On Tue, Mar 29, 2016 at 3:47 PM, Vinzenz Feenstra wrote: > > On Mar 29, 2016, at 3:42 PM, Martin Perina wrote: > > > > On Tue, Mar 29, 2016 at 3:35 PM, Sandro Bonazzola > wrote: > >> >> >> On Tue, Mar 29, 2016 at 3:21 PM, Nir Soffer

Re: [ovirt-devel] [VDSM] Vdsm build requires now python 3 on EL7

On Tue, Mar 29, 2016 at 03:35:13PM +0200, Sandro Bonazzola wrote: > On Tue, Mar 29, 2016 at 3:21 PM, Nir Soffer wrote: > > > Hi all, > > > > Since commit f247a0cff310 (el7: require newly available > > python34-nose), building vdsm > > requires Python 3 on EL7. > > > >

Re: [ovirt-devel] [VDSM] Vdsm build requires now python 3 on EL7

> On Mar 29, 2016, at 3:42 PM, Martin Perina wrote: > > > > On Tue, Mar 29, 2016 at 3:35 PM, Sandro Bonazzola > wrote: > > > On Tue, Mar 29, 2016 at 3:21 PM, Nir Soffer

Re: [ovirt-devel] [VDSM] Vdsm build requires now python 3 on EL7

On Tue, Mar 29, 2016 at 3:35 PM, Sandro Bonazzola wrote: > > > On Tue, Mar 29, 2016 at 3:21 PM, Nir Soffer wrote: > >> Hi all, >> >> Since commit f247a0cff310 (el7: require newly available >> python34-nose), building vdsm >> requires Python 3 on EL7. >>

Re: [ovirt-devel] [VDSM] Vdsm build requires now python 3 on EL7

On Tue, Mar 29, 2016 at 3:21 PM, Nir Soffer wrote: > Hi all, > > Since commit f247a0cff310 (el7: require newly available > python34-nose), building vdsm > requires Python 3 on EL7. > > Unfortunately, it seems that ovirt-release-master that should add all > the dependencies >