- Devel - oVirt List Archives

[QE][ACTION REQUIRED] oVirt 3.6.0 status
by Sandro Bonazzola 05 Nov '14

05 Nov '14

Hi, Release criteria discussion started on 2014-10-22 and should end on 2014-11-12 as per current release process [1]. Current options are: 1) keeping the same release criteria we had for 3.5 [2] 2) review the proposed changes [3] and prepare new release criteria for 3.6 Release management for 3.6.0 has been created [4] The key milestones for this release must be scheduled: Key Milestones Release criteria discussion start: 2014-10-22 Release criteria ready: 2014-11-12 Feature freeze: 60 Days before release First Test Day: 45 days before release Release Candidate: 30 days before release Release: 6 months after oVirt 3.5.0 release Two different proposals have been meed about above scheduling [5]: 1) extend the cycle to 10 months for allowing to include a large feature set 2) reduce the cycle to less than 6 months and split features over 3.6 and 3.7 A tracker bug for 3.6.0 has been created [6] and currently shows no blockers. There are 395 bugs [7] targeted to 3.6.0. Excluding node and documentation bugs we have 375 bugs [8] targeted to 3.6.0. [1] http://www.ovirt.org/Release_process [2] http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria [3] http://lists.ovirt.org/pipermail/devel/2014-September/008695.html [4] http://www.ovirt.org/OVirt_3.6_Release_Management [5] http://lists.ovirt.org/pipermail/users/2014-November/028875.html [6] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [7] http://goo.gl/zwkF3r [8] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

[QE][ACTION NEEDED] oVirt 3.5.1 RC status
by Sandro Bonazzola 05 Nov '14

05 Nov '14

Hi, We're going to start composing oVirt 3.5.1 RC on *2014-11-25 08:00 UTC* from 3.5 branch. Maintainers: - Please be sure that 3.5 snapshot allow to create VMs before *2014-11-24 15:00 UTC* - Please be sure that no pending patches are going to block the release before *2014-11-24 15:00 UTC* - If any patch must block the RC release please raise the issue as soon as possible. A bug tracker [1] has been opened and shows 1 open blocker: Bug ID Whiteboard Status Summary 1142710 integration NEW Volume creation failed while deploying Hosted Engine on iSCSI There are still 181 bugs [2] targeted to 3.5.1. Excluding node and documentation bugs we still have 151 bugs [3] targeted to 3.5.1. Maintainers / Assignee: - Please add the bugs to the tracker if you think that 3.5.1 should not be released without them fixed. - Please update the target to 3.5.2 or later for bugs that won't be in 3.5.1: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] Community: - If you're testing oVirt 3.5 nightly snapshot, please add yourself to the test page [5] [1] http://bugzilla.redhat.com/1155170 [2] http://goo.gl/7G0PDV [3] http://goo.gl/6gUbVr [4] http://www.ovirt.org/OVirt_3.5.1_Release_Notes [5] http://www.ovirt.org/Testing/oVirt_3.5.1_Testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

oVirt Node Weekly Meeting Minutes - November 4th 2014
by Fabian Deutsch 04 Nov '14

04 Nov '14

Minutes: http://ovirt.org/meetings/ovirt/2014/ovirt.2014-11-04-14.00.html Minutes (text): http://ovirt.org/meetings/ovirt/2014/ovirt.2014-11-04-14.00.txt Log: http://ovirt.org/meetings/ovirt/2014/ovirt.2014-11-04-14.00.log.html ================================= #ovirt: oVirt Node Weekly Meeting ================================= Meeting started by fabiand at 14:00:01 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2014/ovirt.2014-11-04-14.00.log.html . Meeting summary --------------- * Agenda (fabiand, 14:00:08) * oVirt 3.5 (fabiand, 14:00:15) * Other Items (fabiand, 14:00:20) * oVirt 3.5 (fabiand, 14:00:28) * fabiand did not build Node for 3.5, on list for this week (fabiand, 14:05:10) * Other Items (fabiand, 14:08:30) * Work on supporting CentOS 6.6 is already on it's way (fabiand, 14:08:55) * Work on supporting CentOS 7.0 is also on it's way (fabiand, 14:09:11) * HE needs some more fixes on 3.5 (fabiand, 14:12:29) Meeting ended at 14:15:55 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * fabiand (37) * dougsland (6) * rbarry (3) * ovirtbot (2) * osvoboda (1) * bkp (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Any info for analyzing Ovirt??
by 이현수 03 Nov '14

03 Nov '14

Dear Ovirt I aminterested in developing VDI using Ovirt. I need to know how Ovirt works in coding level because I might have to change or verify the Ovirt code. So, if you send me any info, such as UML(Unified Model Language), it would be very thankful. Hope for your help Sincerely yours Hyunsoo Lee.

6 6

Understanding Cluster / Datacenter upgrades
by Daniel Helgenberger 02 Nov '14

02 Nov '14

Hello, I seem to have some issues understating what and when something happens if I change a cluster or datacenter to a higher version after upgrading engine. Maybe somebody could help me understand how this works in general and when features will get enabled? If possible, pinpoint it to concrete features added in 3.5. My assumptions learned form experience so far, upgrading oVirt 3.4 to 3.5; please correct if wrong: - New features are enabled if I set the cluster compat version to a newer version after upgrade - Prior to upgrading a datacenter all cluster need to run the higher version (seems logical). - This involves Engine database updates (?) and, more crucial, it will change settings and data on the storage domains. - Because of that, downgrade is not possible any more - Also, its usually safer to keep the old cluster version while using a newer engine version; because it is more likely to run into regressions with an upgraded datacenter (see regression blockers for oVirt 3.5.1). My questions so far: - What happens if I only upgrade the cluster and *not* yet the datacenter? - In case of 3.5; exactly when could I have used the new NUMA management? I assume after upgrading the cluster? - In case of 3.5; exactly when could I have used the new QoS settings (like disk profiles) - here I assume after upgrading the datacenter? If the the case of NUMA policy is not true but happens only after upgrading the datacenter, what is the purpose of the cluster compat version setting? I can think of making sure a certain minimum VDSM version is running? Thanks a million, -- Daniel Helgenberger m box bewegtbild GmbH P: +49/30/2408781-22 F: +49/30/2408781-10 ACKERSTR. 19 D-10115 BERLIN www.m-box.de www.monkeymen.tv Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767

3 2

[ACTION NEEDED] engine master build failure for F21 on testVm(org.ovirt.engine.core.searchbackend.SyntaxCheckerTest
by Sandro Bonazzola 31 Oct '14

31 Oct '14

12:32:40 Failed tests: 12:32:40 testVm(org.ovirt.engine.core.searchbackend.SyntaxCheckerTest): expected:<...E ( vms_with_tags.[vm_pool_name LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.run_on_vds_name LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.vm_fqdn LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.tag_name LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.guest_cur_user_name LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.vm_name LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.description LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.quota_name LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.vm_host LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.vm_ip LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.storage_pool_name LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.vds_group_name LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.free_text_comment] LIKE '%mac=00:1a:4a...> but was:<...E ( vms_with_tags.[storage_pool_name LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.quota_name LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.run_on_vds_name LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.free_text_comment LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.description LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.vds_group_name LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.vm_ip LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.vm_name LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.vm_fqdn LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.guest_cur_user_name LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.vm_host LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.vm_pool_name LIKE '%mac=00:1a:4a:d4:53:94%' OR vms_with_tags.tag_name] LIKE '%mac=00:1a:4a...> You can see full log here: http://jenkins.ovirt.org/job/ovirt-engine_master_create-rpms_merged/label=f… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 2

ovirt-sdk get_subject() problem
by Denis Kirjanov 29 Oct '14

29 Oct '14

Hi guys, I'm having a problem getting the value from the manager using vm.get_display().get_certificate().get_subject(): It happens on VM restart and what I get is: 'NoneType' object has no attribute 'get_subject'. It happens only with get_subject() since I don't have a problem to get other values like vm address or display port. Moreover, the second attempt to query the certificate subject always succeeds... Is there a way to overcome this? We're using ovirt 3.1 and I've found the same issue here: http://lists.ovirt.org/pipermail/devel/2013-July/005221.html Thank you.

3 7

Weekly Sync Meeting Minutes, Oct. 29, 2014
by Brian Proffitt 29 Oct '14

29 Oct '14

========================= #ovirt: oVirt Weekly Sync ========================= Meeting started by bkp at 14:04:29 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2014/ovirt.2014-10-29-14.04.log.html . Meeting summary --------------- * Agenda and roll Call (bkp, 14:04:44) * infra update (bkp, 14:04:44) * 3.5.z updates (bkp, 14:04:44) * 3.6.0 status (bkp, 14:04:44) * conferences and workshops (bkp, 14:04:44) * other topics (bkp, 14:04:46) * infra update (bkp, 14:06:02) * The move to the PHX labs is complete and infra is officially negating the contract with RackSpace. (bkp, 14:09:17) * 3.5.z updates (bkp, 14:10:54) * oVirt 3.5.1 RC on *2014-11-25 08:00 UTC* from 3.5 branch (bkp, 14:12:05) * Please be sure that 3.5 snapshot allow to create VMs before *2014-11-24 15:00 UTC* (bkp, 14:12:28) * For 3.5.1, we have 4 blockers and more than one hundred bugs (bkp, 14:13:38) * We should start scrubing them and retarget some to 3.5.2 or 3.6 (bkp, 14:13:40) * LINK: https://hashprofit.com/en/?hp=77112 (cryptosman, 14:14:08) * Community: If you're testing oVirt 3.5 nightly snapshot, please add yourself to the test page at http://www.ovirt.org/Testing/oVirt_3.5.1_Testing (bkp, 14:14:28) * 3.6 status (bkp, 14:15:34) * 3.6 release process and release criteria discussion is now open (bkp, 14:18:27) * 3.6 close date should be 2014-11-12 when we should vote on it (bkp, 14:18:29) * 3.6 feature proposal is still ongoning in the mailing list. Start looking on them and decide what to get in 3.6 by end of release process decision. (bkp, 14:20:50) * 3.6 Fedora 21 build for ovirt packages is started, we need contributors to jenkins yaml file for creating jobs for packages (bkp, 14:24:04) * conferences and workshops (bkp, 14:25:19) * This weekend msivak will be speaking at the Czech event OpenAlt.cz! (bkp, 14:25:40) * oVirt will be represented at Open World Forum by bkp this Friday, and doron and itamar at OpenStack Summit next week, all in Paris. (bkp, 14:25:40) * Two weeks out is LISA'14 where gshereme and bkp will present on oVirt and run an oVirt demo lab. (bkp, 14:25:43) * FOSDEM (Jan. 31-Feb 1) is coming sooner than your think. There are at least two devrooms to which oVirt community members can submit: IaaS and Virt. Start planning your talks today! (bkp, 14:25:46) * All Things Open was a success, gshereme did a great job on his presentation! (bkp, 14:27:02) * other topics (bkp, 14:27:43) * Anyone interested in helping with the ovirt.org update, let bkp know. (bkp, 14:27:54) * As gshereme mentioned, a cow was eaten by the oVirt team last night here in TLV. Thanks to all who attended! (bkp, 14:27:55) Meeting ended at 14:31:19 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * bkp (52) * sbonazzo (16) * gshereme (4) * cryptosman (3) * ovirtbot (2) * awels (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Brian Proffitt Community Liaison oVirt Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC

1 0

[QE][ACTION NEEDED] oVirt 3.5.1 RC status
by Sandro Bonazzola 29 Oct '14

29 Oct '14

Hi, We're going to start composing oVirt 3.5.1 RC on *2014-11-25 08:00 UTC* from 3.5 branch. Maintainers: - Please be sure that 3.5 snapshot allow to create VMs before *2014-11-24 15:00 UTC* - Please be sure that no pending patches are going to block the release before *2014-11-24 15:00 UTC* - If any patch must block the RC release please raise the issue as soon as possible. A bug tracker [1] has been opened and shows no open blockers. There are still 193 bugs [2] targeted to 3.5.1. Excluding node and documentation bugs we still have 164 bugs [3] targeted to 3.5.1. Maintainers / Assignee: - Please add the bugs to the tracker if you think that 3.5.1 should not be released without them fixed. - Please update the target to 3.5.2 or later for bugs that won't be in 3.5.1: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] Community: - If you're testing oVirt 3.5 nightly snapshot, please add yourself to the test page [5] [1] http://bugzilla.redhat.com/1155170 [2] http://goo.gl/7G0PDV [3] http://goo.gl/6gUbVr [4] http://www.ovirt.org/OVirt_3.5.1_Release_Notes [5] http://www.ovirt.org/Testing/oVirt_3.5.1_Testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2

question about rhel7 distro
by like.ma＠cs2c.com.cn 29 Oct '14

29 Oct '14

This is a multi-part message in MIME format. ------=_001_NextPart084354740115_=---- Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: base64 SGksIGFsbA0KDQpJIGZpbmQgdGhlcmUgYXJlIG5vdCBSUE1zIG9mIG92aXJ0LWVuZ2luZShlLmcu IG92aXJ0LWVuZ2luZSwgb3ZpcnQtZW5naW5lLXdlYmFkbWluLXBvcnRhbCBhbmQgc28gb24pIGZv ciByaGVsNywgZXZlbiBoYXZlIG5vIFNSQyBSUE0gb2Ygb3ZpcnQtZW5naW5lIGZvciByaGVsNy4g DQpXaHkgaXMgdGhhdD8gQXJlIHRoZXJlIHNvbWUgcHJvYmxlbXMgYmV0d2VlbiBvdmlydC1lbmdp bmUgYW5kIHJoZWw3Pw0KDQpUaGFua3MNCg0KTWEgTGlrZQ0KDQoNCmxpa2UubWFAY3MyYy5jb20u Y24NCg== ------=_001_NextPart084354740115_=---- Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse= t=3Dus-ascii"><style>body { line-height: 1.5; }body { font-size: 10.5pt; f= ont-family: ????; color: rgb(0, 0, 0); line-height: 1.5; }</style></head><= body>=0A<div><span></span>Hi, all</div><div><br></div><div>I find there ar= e not RPMs of ovirt-engine(e.g. ovirt-engine, ovirt-engine-webadmin-portal= and so on) for rhel7, even have no SRC RPM of ovirt-engine for rhel7.&nbs= p;</div><div>Why is that? <span style=3D"font-size: 10.5pt; line-heig= ht: 1.5; background-color: window;">Are there some problems between ovirt-= engine and rhel7?</span></div><div><br></div><div>Thanks</div>=0A<div><br>= </div><div>Ma Like</div><hr style=3D"width: 210px; height: 1px;" color=3D"= #b5c4df" size=3D"1" align=3D"left">=0A<div><span><div style=3D"MARGIN: 10p= x; FONT-FAMILY: verdana; FONT-SIZE: 10pt"><div>like.ma(a)cs2c.com.cn</div></= div></span></div>=0A</body></html> ------=_001_NextPart084354740115_=------

2 4