- Devel - oVirt List Archives

broken build list?
by Greg Sheremeta 26 May '15

26 May '15

Any interest in creating a "broken build" list? I frequently run across jobs failing (findbugs, upgrade, etc.) that aren't related to the patches I post, and I'm never sure whether the responsible person knows about it, whether it's being worked on, etc. I think many of us feel that way -- and, most times, we just wait and try again later. The idea is that all broken builds can be posted about on this dedicated list for higher visibility and knowledge. Then we can be more proactive about fixing them. Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme(a)redhat.com

4 7

Postponing 3.5.3 RC2 to tomorrow
by Sandro Bonazzola 26 May '15

26 May '15

Hi, our Jenkins slaves are currently suffering DNS issues so I won't be able to build 3.5.3 RC3 today. Infra is already investigating and the issue will hopefully be fixed by tomorrow. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Upgrade shipped Quartz to 2.2(.1)?
by Martin Sivak 25 May '15

25 May '15

Hi, would it be possible to upgrade the Quartz we ship with ovirt-engine to 2.2.1? It adds support for EJB injections in the jobs and it would make sense now since we are starting to use injections all over the place. Also ovirt-optimizer has been bundling it for this reason and the upgrade would allow me to drop the bundled version and use the one we have global for oVirt. -- Martin Sivák msivak(a)redhat.com Red Hat Czech RHEV-M SLA / Brno, CZ

2 2

Stable 3.6 Repo
by Christopher Pereira 25 May '15

25 May '15

Hi Sandro, We will start testing 3.6 Alpha. Are the Nightly Snapshots equivalent to the 3.6-pre releases or should we setup a special 3.6-pre repo? It would be nice to have a 3.6 yum repo always pointing to the latests (stablest) 3.6 release (alpha, beta, ...).

2 3

new machine types in master/3.6
by Michal Skrivanek 25 May '15

25 May '15

Hi, heads-up for new machine types introduced in 3.6 soon for Fedora we're going to bump up to pc-2.1 machine type. Make sure you're running qemu 2.1+ (you should if you're using ovirt's repo) for CentOS/RHEL we're changing to pc-i440fx-rhel7.2.0. You'd need to use recent builds of qemu 2.3 which is not yet in any CentOS/RHEL nor our ovirt repo. Sandro, we'd need to add that. Thanks, michal

2 1

mom refactoring/improvements
by Michal Skrivanek 25 May '15

25 May '15

Hi, due to the recent issue with MOM performance(well, overall node performance) Francesco proposed quite a few improvements in the code[1] attempting to reduce the number of threads and cache results from vdsm, as well as steps to separate mom from vdsm process (and use json-rpc) please review and comment, this should get in rather soon... Thanks, michal [1] https://gerrit.ovirt.org/#/c/41224 and follow-ups

1 0

[oVirt 3.6 Localization Question #7] "ACTION_TYPE_FAILED_CANNOT_REMOVE_STILL_USED_MAC_POOL"
by Yuko Katabami 25 May '15

25 May '15

This is a multi-part message in MIME format. --------------030201030507080506040109 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, I have another question I would like to ask: *File:***AppErrors *Resource ID:***ACTION_TYPE_FAILED_CANNOT_REMOVE_STILL_USED_MAC_POOL *String:***Cannot ${action} ${type}. Several ${entities} (${DATACENTERS_USING_MAC_POOL_COUNTER}) are using this ${type}: ${DATACENTERS_USING_MAC_POOL} - Please remove it from all ${entities} that are using it and try again. *Question:* In the last sentence, is "it" referring to "MAC Pool"? Thank you, Yuko --------------030201030507080506040109 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi all, I have another question I would like to ask: File: AppErrors Resource ID: ACTION_TYPE_FAILED_CANNOT_REMOVE_STILL_USED_MAC_POOL String: Cannot ${action} ${type}. Several ${entities} (${DATACENTERS_USING_MAC_POOL_COUNTER}) are using this ${type}: ${DATACENTERS_USING_MAC_POOL}  - Please remove it from all ${entities} that are using it and try again. Question: In the last sentence, is "it" referring to "MAC Pool"? Thank you, Yuko <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </body> </html> --------------030201030507080506040109--

3 6

[ovirt-users] oVirt 3.6 new feature: Affinity Group Enforcement Service
by Tomer Saban 25 May '15

25 May '15

Greetings users and developers, I'm developing a new feature "Affinity Rules Enforcement Service"; In summary, =========== If an anti-affinity policy is applied to VMs that are currently running on the same hypervisor, the engine will not automatically migrate one of them off once the policy is applied. The Affinity Rules Enforcement Service will periodically check that affinity rules are being enforced and will migrate VMs if necessary in order to comply with those rules. You're welcome to review the feature page: http://www.ovirt.org/Affinity_Group_Enforcement_Service The feature page is responding to RFE https://bugzilla.redhat.com/show_bug.cgi?id=1112332 Your comments appreciated. Thanks, Tomer

2 2

[oVirt 3.6 Localization Question #16] "Volume is destination for geo-replication."
by Yuko Katabami 21 May '15

21 May '15

This is a multi-part message in MIME format. --------------090605000403020604070303 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I am really sorry that I sent my last email with a wrong string included in the subject. This is the correct one. ----------------------------------------------------------------------------------- Hi all, Another question has been raised by a translator. Could you please help us? *File:*** ApplicationConstants *Resource ID:***geoRepSlaveVolumeToolTip *String:*** Volume is destination for geo-replication. *Question: *Could it be 'Volume in/of destination for geo-replication' instead? (or more like "This volume will be the destination for geo-replication", as it is a tooltip, describing the GUI Label) Kind regards, Yuko --------------090605000403020604070303 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body text="#000000" bgcolor="#FFFFFF"> I am really sorry that I sent my last email with a wrong string included in the subject. This is the correct one. ----------------------------------------------------------------------------------- Hi all, Another question has been raised by a translator. Could you please help us? File: ApplicationConstants Resource ID: geoRepSlaveVolumeToolTip String: Volume is destination for geo-replication. Question: Could it be 'Volume in/of destination for geo-replication' instead? (or more like "This volume will be the destination for geo-replication", as it is a tooltip, describing the GUI Label) Kind regards, Yuko </body> </html> --------------090605000403020604070303--

2 3

[ANN] oVirt 3.6.0 First Alpha Release is now available for testing
by Sandro Bonazzola 21 May '15

21 May '15

The oVirt Project is pleased to announce the availability of the first Alpha release of oVirt 3.6 for testing, as of May 20, 2015. oVirt is an open source alternative to VMware vSphere, and provides an excellent KVM management interface for multi-node virtualization. The Alpha release is available now for Fedora 20, Red Hat Enterprise Linux 6.6, CentOS 6.6 (or similar) and Red Hat Enterprise Linux 7.1, CentOS 7.1 (or similar). The Alpha release can also be deployed on Hypervisor Hosts running Fedora 21 and Fedora 22. This Alpha release of oVirt includes numerous bug fixes. See the release notes [1] for an initial list of the new features and bugs fixed. Please refer to release notes [1] for Installation / Upgrade instructions. A new oVirt Live ISO and Node ISO will be available soon[2]. Please note that mirrors[3] may need usually one day before being synchronized. Please refer to the release notes for known issues in this release. [1] http://www.ovirt.org/OVirt_3.6_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

4 4