[ovirt-devel] oVirt Node Next - Sprint 2 Summary

Hey, during our second sprint, lasting 3 weeks, ending on January 15, the Node team worked on the following items: Add ovirt-release-host-node --- This subpackage of ovirt-release now has all teh dependencies which are expected to be available on node. In

[ovirt-devel] vdsm] tag and branch ovirt 3.6.2 RC3

Hi, Sorry for the short notice of this email. the state of branch ovirt-3.6 is as follows tag sha subject bug target release

[ovirt-devel] oVirt 3.6.2 RC3 build starting

Fyi oVirt products maintainers, An oVirt build for an official release is going to start right now. If you're a maintainer for any of the projects included in oVirt distribution and you have changes in your package ready to be released please: - bump version and release to be GA ready - tag your

[ovirt-devel] Jenkins overload and cancellation of ~1000 jobs

Hi everyone, Earlier today there was a huge load peak in jenkins that ended up with a job queue > 1000, we just removed from the queue most of the jobs to avoid stop servicing other projects (like for example the jobs related to releases and similar). That means that a lot of patches (mostly

[ovirt-devel] Hello statement on Ovirt VM.

 Here is South Korea. Current through the ovirt engin you try to install the VM after creating Mint OS. Not install the screen moves during setup, it will stop as it is. We will let you know you do not have the support for possibly is Once from ovirt engin mint os. Website address of mint OS

[ovirt-devel] [vdsm] New schema format proposal

I would like to propose new format for schema that we use in vdsm. I started to work on a patch [1] where I explore how the new file should look like. I have couple of goals which I would like to achieve by doing this transformation: 1. I would like to use this file to verify engine code.

Re: [ovirt-devel] [vdsm] New schema format proposal

> On Jan 19, 2016, at 10:45 AM, Piotr Kliczewski > wrote: > > I would like to propose new format for schema that we use in vdsm. I > started to work on a patch [1] where I explore how the new file should > look like. I have couple of goals which I would like to

Re: [ovirt-devel] vdsm] tag and branch ovirt 3.6.2 RC3

Done. Pushed branch ovirt-3.6.2. Also, tagged v4.17.18 from that branch The only change since previous tag (4.17.17) is tag v4.17.18 Tagger: Francesco Romani Date: Tue Jan 19 13:08:36 2016 +0100 oVirt 3.6.2 RC3 commit 4b350cf86537f48cdbe4bbd5993bc4d761990aa1 Author:

[ovirt-devel] Vdsm sync 19/1

Hi all, (Participated: Piotr, Francesco, Adam, Nir, Edy and I) We discussed about the following topics: Python3 - terminating contextmanager is ready https://gerrit.ovirt.org/51407 - this allows us to remove deathSignal usages and safely kill processes on failures. Francesco already covered

Re: [ovirt-devel] Missing admin permissions.

On Tuesday, January 19, 2016 09:50:44 AM Fred Rolland wrote: > I think this should help: > https://www.mail-archive.com/devel%40ovirt.org/msg05152.html > Strange that the admin@internal didn't get this by default, but after adding that following the mail in the archive, I can once again create

[ovirt-devel] [vdsm][virt] what's new in virt (20160119)

Hi all, Here it is a new weekly summary about what's going on on virt's world (VDSM edition). Since last week we made some good progress, thanks to all the reviewer and to all the maintainers which helped; patches are receiving attention and are under active work, so this is a boring report :)

Re: [ovirt-devel] No more "vds group" in master code , instead please use "cluster"

Hi all Please note that there is still a problem on engine-setup I have already a fixing draft [1] Meanwhile, until this is verified and merged please do before engine-setup from dbscripts/upgrade dir psql -U engine -f 04_00_0210_add_vds_group_view.sql Thanks and sorry for that, this will