[ovirt-devel] Fwd: [CentOS-devel] LinchPin v1.0.3 (bugfix) has been released

This new version supports oVirt topologies and VMs: http://linchpin.readthedocs.io/en/develop/topologies_ovirt.html?highlight=ovirt -- Forwarded message -- From: Clint Savage Date: 2017-09-12 22:12 GMT+02:00 Subject: [CentOS-devel] LinchPin v1.0.3 (bugfix) has

Re: [ovirt-devel] ovirt-system-tests run specific scenario/debugging

Im attempting to run via the lago commands re Barak's suggestion, but I'm running into ssh timeouts (as it seems like maybe a failing deployment) myoung at dev-vm in ~/repos/github/ovirt-system-tests/vagrant on master* $ lago deploy @ Deploy environment: # [Thread-2] Deploy VM

Re: [ovirt-devel] Why do we recommend to send a patch initially as draft?

On Mon, Sep 18, 2017 at 3:42 PM, Roy Golan wrote: > > On Mon, 18 Sep 2017 at 22:30 Yaniv Kaul wrote: > >> Here[1]: >> "Anyone can send a patch >> > That's no longer true. We have a whitelist. [2][3] > Initially a patch should be sent as draft" >> > I think

Re: [ovirt-devel] OVN provider's firewalld services deployment during engine setup

On Mon, Sep 18, 2017 at 4:16 PM, Yedidyah Bar David wrote: > (Re-opening an old thread) > > On Mon, Jun 19, 2017 at 9:53 AM, Yedidyah Bar David wrote: >> On Mon, Jun 19, 2017 at 9:45 AM, Dan Kenigsberg wrote: >>> On Sun, Jun 18, 2017 at 5:18

Re: [ovirt-devel] Why do we recommend to send a patch initially as draft?

On Mon, 18 Sep 2017 at 22:30 Yaniv Kaul wrote: > Here[1]: > "Anyone can send a patch > Initially a patch should be sent as draft" > > A draft is hidden from the public, why is it better to send as such? > I see few advantages and they all drawn from the assumption the initial

[ovirt-devel] Why do we recommend to send a patch initially as draft?

Here[1]: "Anyone can send a patch Initially a patch should be sent as draft" A draft is hidden from the public, why is it better to send as such? TIA, Y. [1] https://www.ovirt.org/develop/dev-process/working-with-gerrit/ ___ Devel mailing list

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt HE master ] [ 17/09/17 ] [ engine-setup ]

On Mon, Sep 18, 2017 at 4:33 PM, Simone Tiraboschi wrote: > > > On Mon, Sep 18, 2017 at 12:09 PM, Simone Tiraboschi > wrote: > >> >> >> On Sun, Sep 17, 2017 at 11:14 AM, Eyal Edri wrote: >> >>> >>> >>> On Sun, Sep 17, 2017 at 11:50

Re: [ovirt-devel] [vdsm] s390 draft patches submitted for review

On 09/18/2017 05:31 PM, Viktor Mihajlovski wrote: Hi, I have submitted a topic branch containing the changes necessary to enable support for the s390 arch in VDSM and would appreciate your feedback, not only for the code, but also on the procedure: 1. I've submitted the patches as draft,

[ovirt-devel] [vdsm] s390 draft patches submitted for review

Hi, I have submitted a topic branch containing the changes necessary to enable support for the s390 arch in VDSM and would appreciate your feedback, not only for the code, but also on the procedure: 1. I've submitted the patches as draft, following the suggestions on the homepage. Not sure

[ovirt-devel] Hyperconverged Guide links broken

Hi, can you please fix the Hyperconverged Guide? All the pages under https://www.ovirt.org/documentation/gluster-hyperconverged/ have broken links. Started fixing the first page here: https://github.com/oVirt/ovirt-site/pull/1220 Thanks to "investigator" on #ovirt channel for reporting this. --

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt HE master ] [ 17/09/17 ] [ engine-setup ]

On Mon, Sep 18, 2017 at 12:09 PM, Simone Tiraboschi wrote: > > > On Sun, Sep 17, 2017 at 11:14 AM, Eyal Edri wrote: > >> >> >> On Sun, Sep 17, 2017 at 11:50 AM, Yaniv Kaul wrote: >> >>> >>> >>> On Sun, Sep 17, 2017 at 11:47 AM, Eyal Edri

Re: [ovirt-devel] OVN provider's firewalld services deployment during engine setup

(Re-opening an old thread) On Mon, Jun 19, 2017 at 9:53 AM, Yedidyah Bar David wrote: > On Mon, Jun 19, 2017 at 9:45 AM, Dan Kenigsberg wrote: >> On Sun, Jun 18, 2017 at 5:18 PM, Yaniv Kaul wrote: >>> >>> >>> On Sun, Jun 18, 2017 at 2:17

Re: [ovirt-devel] Error in running engine-setup

Thanks, I have updated it.But also deleting 10-setup-database.conf also worked. Regards, Shubham On Mon, Sep 18, 2017 at 5:23 PM, Greg Sheremeta wrote: > sudo dnf update otopi -y > > -- Forwarded message -- > From: Simone Tiraboschi >

[ovirt-devel] [ANN] oVirt 4.1.6 Release is now available

The oVirt Project is pleased to announce the availability of oVirt 4.1.6 release, as of September 18th, 2017 This update is the sixth in a series of stabilization updates to the 4.1 series. 4.1.6 brings 23 enhancements and 100 bugfixes, including 53 high or urgent severity fixes, on top of oVirt

Re: [ovirt-devel] Error in running engine-setup

On Sun, Sep 17, 2017 at 7:32 PM, shubham dubey wrote: > Thanks for the solution. > I will look into that bug. > > We already fixed it, you should simply update otopi package on your devel system. > Regards, > Shubham > > On Sun, Sep 17, 2017 at 8:05 PM, Benny Zlotnik

Re: [ovirt-devel] qemu-kvm-ev-2.9.0-16.el7_4.5.1 now available for testing

> On 14 Sep 2017, at 15:23, Sandro Bonazzola wrote: > > > > 2017-09-14 14:43 GMT+02:00 Michal Skrivanek >: > >> On 12 Sep 2017, at 12:37, Sandro Bonazzola >

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt HE master ] [ 17/09/17 ] [ engine-setup ]

On 09/18/2017 11:12 AM, Simone Tiraboschi wrote: > > > On Mon, Sep 18, 2017 at 12:09 PM, Simone Tiraboschi > > wrote: > > > > On Sun, Sep 17, 2017 at 11:14 AM, Eyal Edri > wrote: > > > >

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt HE master ] [ 17/09/17 ] [ engine-setup ]

On Mon, Sep 18, 2017 at 12:09 PM, Simone Tiraboschi wrote: > > > On Sun, Sep 17, 2017 at 11:14 AM, Eyal Edri wrote: > >> >> >> On Sun, Sep 17, 2017 at 11:50 AM, Yaniv Kaul wrote: >> >>> >>> >>> On Sun, Sep 17, 2017 at 11:47 AM, Eyal Edri

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt HE master ] [ 17/09/17 ] [ engine-setup ]

On Sun, Sep 17, 2017 at 11:14 AM, Eyal Edri wrote: > > > On Sun, Sep 17, 2017 at 11:50 AM, Yaniv Kaul wrote: > >> >> >> On Sun, Sep 17, 2017 at 11:47 AM, Eyal Edri wrote: >> >>> Hi, >>> >>> It looks like HE suite ( both 'master' and '4.1' )

Re: [ovirt-devel] Adding s390 support to oVirt

On 18.09.2017 10:36, Barak Korren wrote: > On 18 September 2017 at 10:30, Viktor Mihajlovski > wrote: >> Hi, >> >> as a heads up: I'd like to contribute some basic support for the s390 >> architecture to oVirt. For that purpose I'll post some patches to >> gerrit,

Re: [ovirt-devel] Fwd: CellTable replaced

On Sun, Sep 17, 2017 at 11:48 AM, Yaniv Kaul wrote: > > > On Sun, Sep 17, 2017 at 11:38 AM, Shani Leviim wrote: > >> Hi, >> It seems that after changing the data grid on Storage > Disks > Export, >> the table's size doesn't fit to its content. >> Also,

Re: [ovirt-devel] Adding s390 support to oVirt

On 18 September 2017 at 10:30, Viktor Mihajlovski wrote: > Hi, > > as a heads up: I'd like to contribute some basic support for the s390 > architecture to oVirt. For that purpose I'll post some patches to > gerrit, mostly for the following repositories: VDSM, >

[ovirt-devel] Adding s390 support to oVirt

Hi, as a heads up: I'd like to contribute some basic support for the s390 architecture to oVirt. For that purpose I'll post some patches to gerrit, mostly for the following repositories: VDSM, ovirt-engine-api-model and ovirt-engine. There might be some collateral patches that need to go into