Re: [vdsm] Task and other resource leak problem

2012-04-09 Thread Ayal Baron
- Original Message - > > Guys, > > I'm investigating about resource leak problem about task,job,storage > pool,storage domain.I don't know very deep about the whole scheme, > hope someone can tell if what I found is a problem or not. > > task manager thread pool > self.tasks = {} self.

[vdsm] Task and other resource leak problem

2012-04-09 Thread Royce Lv
Guys, I'm investigating about resource leak problem about task,job,storage pool,storage domain.I don't know very deep about the whole scheme, hope someone can tell if what I found is a problem or not. task managerthread pool self.tasks = {}self.__tasks = Queue

[vdsm] Test that broken upstream

2012-04-09 Thread Saggi Mizrahi
Upstream will not currently build because of the following patch: commit 1d4f220616ca6fc014bbdfef7b826a16ed608ddf Author: y kaplan Date: Thu Apr 5 18:02:40 2012 +0300 Added guestIFTests Change-Id: I8b5138296c098826f149c26d38fd2bfce8794fe4 Reviewed-on: http://gerrit.ovirt.org/3

Re: [vdsm] upstream/downstream compat

2012-04-09 Thread Ryan Harper
* Dan Kenigsberg [2012-04-09 04:21]: > On Fri, Apr 06, 2012 at 09:58:09AM -0500, Ryan Harper wrote: > > I've submitted some changes to start some of the work of removing the > > RHEV/RHEVM names throughout the vdsm code. In one of the patches, > > there's a good discussion on compatibility with d

Re: [vdsm] [Engine-devel] Is there a preferred workflow when adding additional error messages to VDSM _and_ Engine?

2012-04-09 Thread Livnat Peer
On 07/04/12 18:10, Lee Yarwood wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello all, > > I'm currently working on a patch to correct the logic used by vdsm when > reviewing the logical and physical block size of physical volumes [1]. > Once/If this is approved I'd like to look i

Re: [vdsm] upstream/downstream compat

2012-04-09 Thread Dan Kenigsberg
On Fri, Apr 06, 2012 at 09:58:09AM -0500, Ryan Harper wrote: > I've submitted some changes to start some of the work of removing the > RHEV/RHEVM names throughout the vdsm code. In one of the patches, > there's a good discussion on compatibility with downstream[1] > And I wanted to continue that o