Here are example logs with running and stopping one vm:
# tail -f /var/log/vdsm/vdsm.log | grep health
Thread-13::DEBUG::2016-01-14
19:42:04,625::health::84::health::(_check) Checking health
Thread-13::DEBUG::2016-01-14
19:42:04,651::health::86::health::(_check) Collected 25 objects
> On Jan 14, 2016, at 6:38 PM, Nir Soffer wrote:
>
> Hi all,
>
> Continuing the leak investigation Francesco and Milan are working on,
> I posted this patch, adding leak health monitoring to vdsm [1]. This patch
> currently monitor collectible objects, and we may add other
Hi all,
Continuing the leak investigation Francesco and Milan are working on,
I posted this patch, adding leak health monitoring to vdsm [1]. This patch
currently monitor collectible objects, and we may add other interesting
stuff later if needed.
To enable the monitor, you must set:
[devel]
On Tue, Dec 22, 2015 at 12:04 PM, Dan Kenigsberg wrote:
> On Tue, Dec 22, 2015 at 09:59:20AM +0200, Barak Korren wrote:
> > > Please remove it - unless you have plans to revert the
> > > automation/*-based approach.
> >
> > Since I don't know who wrote it, and what useful bits
Hi,
we are going to merge patches which drop EAP 6 support [1] and require
WildFly 10 / EAP 7 [2] for oVirt engine master on Monday January 18th
at 10:00 CET.
This is a huge step as we will finally be able to use all new features
provided by WildFly 10 (J2EE 7, Java 8, RESTEasy 3, ActiveMQ
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-$BRANCH", i.e.
> "ovirt-node-master" or "ovirt-node-3.6".
>
>
On Thu, Jan 14, 2016 at 2:26 PM, 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
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