Re: [ovirt-devel] Vdsm - 6 years (in 10 minutes)

On 01/09/2017 10:40 AM, Yaniv Bronheim wrote: craziness .. cool thing though Indeed, cool! On Mon, Jan 9, 2017 at 5:08 PM, Nir Soffer mailto:nsof...@redhat.com>> wrote: Hi all, Please enjoy this visualization of vdsm development since 2011: https://www.youtube.com/watch?v=U

Re: [ovirt-devel] Announcing Rafael Martins as ovirt*uploader and ovirt-log-collector maintainer

On 08/04/2016 08:11 AM, Sandro Bonazzola wrote: Hi, Rafael Martins has contributed several bug fixes and improvements to ovirt-iso-uploader, ovirt-image-uploader and ovirt-log-collector. He took a major role in the projects and he's currently default assignee for bugs related to these projects.

Re: [ovirt-devel] gerrit.ovirt.org projects

Hi, On 05/17/2016 07:49 AM, Shlomo Ben David wrote: Hi, I have a question about projects on gerrit.ovirt.org . I'm working on cleaning up the gerrit.ovirt.org and updating the replication process to github, I've noticed that the projects bel

Re: [ovirt-devel] VARIANT_ID usage - with our without oVirt version?

On 01/14/2016 08:26 AM, Moti Asayag wrote: On Wed, Jan 13, 2016 at 5:17 PM, Fabian Deutsch > wrote: Hey, we've now merged a patch [0] to use and populate the VARIANT and VARIANT_ID fields on Node. Currently the value is something like "ovirt-node

Re: [ovirt-devel] [vdsm] merge rights on master branch

On 11/17/2015 05:47 AM, Dan Kenigsberg wrote: Nir Soffer has been contributing to Vdsm for more than two years now. Beyond his storage-related expertise, he is well-known for his thorough code reviews and his pains when the master branch is broken. It's time for him to take even bigger responsi

Re: [ovirt-devel] Registration duplication?

On 07/22/2015 09:42 AM, Fabian Deutsch wrote: Hey, I've seen that some new code landed to support Engine registration using the generic registration approach. But it seem that we now have two implementations: 1. vdsm-tool register [0] 2. ovirt-register [1] To reduce code duplication I'd sugge

Re: [ovirt-devel] oVirt node 3.6 and CPU load indefinitely stuck on 100% while vdsmd indefinitely tries to restart

On 06/01/2015 03:56 AM, Simone Tiraboschi wrote: - Original Message - From: "Douglas Schilling Landgraf" To: "Simone Tiraboschi" , devel@ovirt.org Cc: "Fabian Deutsch" Sent: Saturday, May 30, 2015 11:28:38 PM Subject: Re: oVirt node 3.6 and CPU load in

Re: [ovirt-devel] oVirt node 3.6 and CPU load indefinitely stuck on 100% while vdsmd indefinitely tries to restart

On 05/29/2015 06:44 AM, Simone Tiraboschi wrote: Hi, I tried to have hosted-engine deploying the engine appliance over oVirt node. I think it will be quite a common scenario. I tried with an oVirt node build from yesterday. Unfortunately I'm not able to conclude the setup cause oVirt node got t

[ovirt-devel] (glusterfs) No nightly rpms builds available at 20-May-2015

Hi, Looks like the nightly builds job for glusterfs didn't complete at 20 May. Does anyone can help to trigger a new job please? oVirt Node build adds the nightly builds of gluster as repository. http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs/epel-6-x86_64/glusterfs-3.8de

Re: [ovirt-devel] Possible documentation fixes - advice needed

Hello Gina, On 05/20/2015 03:33 PM, Gina Likins wrote: Hi all- I am new to this, so please bear with me. I was researching oVirt, looking for information on "developer guidelines," and I found some, but they weren't all connected or linked iin from the same page. I think I can fix that (and

Re: [ovirt-devel] Greg Sheremeta is now an ovirt-engine UI maintainer

On 03/26/2015 09:20 AM, Vojtech Szocs wrote: Congrats Greg! :) Indeed, Congrats Greg! Well deserved. :-) Vojtech - Original Message - From: "Einav Cohen" To: "Lior Vernia" , "Alona Kaplan" , "Daniel Erez" , "Gilad Chaplik" , "Tomas Jelinek" , "Vojtech Szocs" , "Alexander Wels" ,

[ovirt-devel] vdsm-4.16.4-0 is available (ovirt-3.5.0 rc2)

Hi, As requested, below the urls for the new VDSM build. f19: http://koji.fedoraproject.org/koji/taskinfo?taskID=7565788 f20: http://koji.fedoraproject.org/koji/taskinfo?taskID=7565817 el6: http://koji.fedoraproject.org/koji/taskinfo?taskID=7565880 el7: http://koji.fedoraproject.org/koji/taskinf

Re: [ovirt-devel] Why there is no "Ovirt Engine" register item on Ovirt Node

On 08/13/2014 05:12 AM, yangtao wrote: Hi Fabian, How to build build plugin and use the kickstart provided in that plugin? What's more, I use 3.1.0 master version to build. The ovirt node master version doesn't include the VSDM plugin, right? Hi Tao, In the below link there are steps how t

Re: [ovirt-devel] vdsm-4.14.11-2 New build for ovirt-3.4

On 07/24/2014 04:39 AM, ybronhei wrote: On 07/23/2014 06:21 PM, Douglas Schilling Landgraf wrote: On 07/23/2014 05:25 AM, ybronhei wrote: On 07/23/2014 12:21 PM, Dan Kenigsberg wrote: On Wed, Jul 23, 2014 at 12:50:07AM +0300, ybronhei wrote: Hey all, New build of vdsm for ovirt-3.4 is

Re: [ovirt-devel] vdsm-4.14.11-2 New build for ovirt-3.4

On 07/23/2014 05:25 AM, ybronhei wrote: On 07/23/2014 12:21 PM, Dan Kenigsberg wrote: On Wed, Jul 23, 2014 at 12:50:07AM +0300, ybronhei wrote: Hey all, New build of vdsm for ovirt-3.4 is available: f20 - http://koji.fedoraproject.org/koji/taskinfo?taskID=7178863 f19 - http://koji.fedoraproje

Re: [ovirt-devel] python-ioprocess for el7?

On 07/12/2014 11:54 PM, Douglas Schilling Landgraf wrote: On 07/11/2014 07:46 AM, Dan Kenigsberg wrote: On Thu, Jul 10, 2014 at 05:01:21PM -0400, Adam Litke wrote: Hi, I am looking for python-ioprocess RPMs (new enough for latest vdsm requirements). Can anyone point me in the right direction

Re: [ovirt-devel] python-ioprocess for el7?

On 07/11/2014 07:46 AM, Dan Kenigsberg wrote: On Thu, Jul 10, 2014 at 05:01:21PM -0400, Adam Litke wrote: Hi, I am looking for python-ioprocess RPMs (new enough for latest vdsm requirements). Can anyone point me in the right direction? Thanks! Looking at https://admin.fedoraproject.org/upd

[ovirt-devel] python-pthreading 0.1.3-2

Hi, python-pthreading 0.1.3-2 is available to test. Please help giving karmas to achieve this version to stable branch as soon as possible. Changes included: - monkey_patch: Fail if it is too late to monkey-patch - Add the missing locked() interface F19: https://admin.fedoraproject.org/updat

[ovirt-devel] oVirt 3.5 test day 1 results

Hi, This time I have tested the below RFE: [RFE] Change the "Slot" field to "Service Profile" when cisco_ucs is selected as the fencing type. https://bugzilla.redhat.com/show_bug.cgi?id=1090803 Test Data === Running oVirt 3.5 with Power Management enabled in hosts when selecting Type

Re: [ovirt-devel] latest python-lxml python-ethtool break VDSM on f19

Hi, On 05/19/2014 01:47 PM, Douglas Schilling Landgraf wrote: On 05/12/2014 03:46 AM, Antoni Segura Puimedon wrote: - Original Message - From: "Roy Golan" To: devel@ovirt.org, "Yaniv Bronheim" , "Francesco Romani" Cc: "Gianluca Cecchi"

Re: [ovirt-devel] Fwd: Re: Mass bug: packages should not auto-enable systemd units

On 04/30/2014 05:32 PM, Dan Kenigsberg wrote: On Wed, Apr 30, 2014 at 07:57:32PM +0200, Vinzenz Feenstra wrote: Due to some confusion around how alternatives worked, I screwed up the list of packages here. I've updated it below. I'll give it a few more days before filing the actual bugs. On

Re: [Devel] Vdsm functional tests

On 04/07/2014 05:04 AM, Dan Kenigsberg wrote: On Sun, Apr 06, 2014 at 11:47:26PM -0400, Douglas Schilling Landgraf wrote: On 04/03/2014 12:24 PM, Dan Kenigsberg wrote: On Thu, Apr 03, 2014 at 12:31:44PM -0400, Douglas Schilling Landgraf wrote: On 04/03/2014 11:08 AM, Dan Kenigsberg wrote

Re: [Devel] Vdsm functional tests

On 04/03/2014 12:24 PM, Dan Kenigsberg wrote: On Thu, Apr 03, 2014 at 12:31:44PM -0400, Douglas Schilling Landgraf wrote: On 04/03/2014 11:08 AM, Dan Kenigsberg wrote: Functional tests are intended to verify that a running Vdsm instance does what it should, when treated as a black box, over

Re: [Devel] Vdsm functional tests

On 04/03/2014 11:08 AM, Dan Kenigsberg wrote: Functional tests are intended to verify that a running Vdsm instance does what it should, when treated as a black box, over its public API. They should be comprehensive and representative of a typical field usage of Vdsm. It is a sin to break such a