February 2015 - Devel - oVirt List Archives

Google Summer of Code Reminder
by Brian Proffitt 20 Feb '15

20 Feb '15

If you have any ideas for Google Summer of Code, *now* is the time to get them in. The deadline is 1900 UTC today. We have one project submitted to date, but the more we have, the more slots we should get. Thanks, BKP -- 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

Re: [ovirt-devel] [ovirt-users] Announcing the moVirt Incubator Project!
by Donny D 20 Feb '15

20 Feb '15

----_com.android.email_2495776108079720 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 CiAgICAKVGhhdCBpcyBncmVhdCBwcm9qZWN0LiBUaGlzIG1ha2VzIG1lIHZlcnkgaGFwcHkuwqAK CgpIYXBweSBDb25uZWN0aW5nLiBTZW50IGZyb20gbXkgU3ByaW50IFNhbXN1bmcgR2FsYXh5IFPC riA1CgotLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tCkZyb206IEJyaWFuIFByb2Zm aXR0IDxicHJvZmZpdEByZWRoYXQuY29tPiAKRGF0ZTogMDIvMTcvMjAxNSAgOToxNyBBTSAgKEdN VC0wNzowMCkgClRvOiBib2FyZCA8Ym9hcmRAb3ZpcnQub3JnPiAKQ2M6IGFubm91bmNlQG92aXJ0 Lm9yZywgdXNlcnMgPHVzZXJzQG92aXJ0Lm9yZz4sIGRldmVsQG92aXJ0Lm9yZyAKU3ViamVjdDog W292aXJ0LXVzZXJzXSBBbm5vdW5jaW5nIHRoZSBtb1ZpcnQgSW5jdWJhdG9yIFByb2plY3QhIAoK VGhpcyBtZXNzYWdlIGlzIHRvIGFubm91bmNlIG1vVmlydCBhcyBhIG5ldyBvVmlydCBpbmN1YmF0 b3IgcHJvamVjdCwgYXBwcm92ZWQgYnkgdW5hbmltb3VzIHZvdGUgb2YgdGhlIEJvYXJkIG1haWxp bmcgbGlzdCEKCkRldGFpbHMgYWJvdXQgdGhlIHByb2plY3QgY2FuIGJlIGZvdW5kIGF0CgpodHRw Oi8vd3d3Lm92aXJ0Lm9yZy9Qcm9qZWN0X21vVmlydAoKTW9yZSBpbmZvcm1hdGlvbiBhYm91dCB0 aGUgaW5jdWJhdG9yIGF0IG9WaXJ0IGNhbiBiZSBmb3VuZCBhdAoKaHR0cDovL3d3dy5vdmlydC5v cmcvSW5jdWJhdGluZ19hbl9vVmlydF9TdWJwcm9qZWN0CgpQbGVhc2UgY2hlY2sgb3V0IHRoaXMg cHJvamVjdCBhbmQgc2VlIHdoYXQgeW91IGNhbiBkbyB0byBoZWxwIQoKLS0gCkJyaWFuIFByb2Zm aXR0CgpDb21tdW5pdHkgTGlhaXNvbgpvVmlydApPcGVuIFNvdXJjZSBhbmQgU3RhbmRhcmRzLCBS ZWQgSGF0IC0gaHR0cDovL2NvbW11bml0eS5yZWRoYXQuY29tClBob25lOiArMSA1NzQgMzgzIDlC S1AKSVJDOiBia3AgQCBPRlRDCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fClVzZXJzIG1haWxpbmcgbGlzdApVc2Vyc0BvdmlydC5vcmcKaHR0cDovL2xpc3Rz Lm92aXJ0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3VzZXJzCg== ----_com.android.email_2495776108079720 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0 L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT4KICAgIAo8ZGl2PlRoYXQgaXMgZ3Jl YXQgcHJvamVjdC4gVGhpcyBtYWtlcyBtZSB2ZXJ5IGhhcHB5LiZuYnNwOzwvZGl2PjxkaXY+PGJy PjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXYgaWQ9ImNvbXBvc2VyX3Np Z25hdHVyZSI+PGRpdiBzdHlsZT0iZm9udC1zaXplOjg1JTtjb2xvcjojNTc1NzU3Ij5IYXBweSBD b25uZWN0aW5nLiBTZW50IGZyb20gbXkgU3ByaW50IFNhbXN1bmcgR2FsYXh5IFPCriA1PC9kaXY+ PC9kaXY+PGJyPjxicj4tLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tPGJyPkZyb206 IEJyaWFuIFByb2ZmaXR0ICZsdDticHJvZmZpdEByZWRoYXQuY29tJmd0OyA8YnI+RGF0ZTogMDIv MTcvMjAxNSAgOToxNyBBTSAgKEdNVC0wNzowMCkgPGJyPlRvOiBib2FyZCAmbHQ7Ym9hcmRAb3Zp cnQub3JnJmd0OyA8YnI+Q2M6IGFubm91bmNlQG92aXJ0Lm9yZywgdXNlcnMgJmx0O3VzZXJzQG92 aXJ0Lm9yZyZndDssIGRldmVsQG92aXJ0Lm9yZyA8YnI+U3ViamVjdDogW292aXJ0LXVzZXJzXSBB bm5vdW5jaW5nIHRoZSBtb1ZpcnQgSW5jdWJhdG9yIFByb2plY3QhIDxicj48YnI+VGhpcyBtZXNz YWdlIGlzIHRvIGFubm91bmNlIG1vVmlydCBhcyBhIG5ldyBvVmlydCBpbmN1YmF0b3IgcHJvamVj dCwgYXBwcm92ZWQgYnkgdW5hbmltb3VzIHZvdGUgb2YgdGhlIEJvYXJkIG1haWxpbmcgbGlzdCE8 YnI+PGJyPkRldGFpbHMgYWJvdXQgdGhlIHByb2plY3QgY2FuIGJlIGZvdW5kIGF0PGJyPjxicj5o dHRwOi8vd3d3Lm92aXJ0Lm9yZy9Qcm9qZWN0X21vVmlydDxicj48YnI+TW9yZSBpbmZvcm1hdGlv biBhYm91dCB0aGUgaW5jdWJhdG9yIGF0IG9WaXJ0IGNhbiBiZSBmb3VuZCBhdDxicj48YnI+aHR0 cDovL3d3dy5vdmlydC5vcmcvSW5jdWJhdGluZ19hbl9vVmlydF9TdWJwcm9qZWN0PGJyPjxicj5Q bGVhc2UgY2hlY2sgb3V0IHRoaXMgcHJvamVjdCBhbmQgc2VlIHdoYXQgeW91IGNhbiBkbyB0byBo ZWxwITxicj48YnI+LS0gPGJyPkJyaWFuIFByb2ZmaXR0PGJyPjxicj5Db21tdW5pdHkgTGlhaXNv bjxicj5vVmlydDxicj5PcGVuIFNvdXJjZSBhbmQgU3RhbmRhcmRzLCBSZWQgSGF0IC0gaHR0cDov L2NvbW11bml0eS5yZWRoYXQuY29tPGJyPlBob25lOiArMSA1NzQgMzgzIDlCS1A8YnI+SVJDOiBi a3AgQCBPRlRDPGJyPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fPGJyPlVzZXJzIG1haWxpbmcgbGlzdDxicj5Vc2Vyc0BvdmlydC5vcmc8YnI+aHR0cDovL2xp c3RzLm92aXJ0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3VzZXJzPGJyPjwvYm9keT48L2h0bWw+ ----_com.android.email_2495776108079720--

5 4

Issues with the VM display type value(s)
by Einav Cohen 19 Feb '15

19 Feb '15

Hi, This is about the changes introduced by patch http://gerrit.ovirt.org/#/c/35281 (restapi: adjust api to new graphics representation). There are a couple of issues with the VM's display type value: (1) the "display -> type" value of the VM in the REST API seem to map to different properties based on the VM status. see http://i.imgur.com/Mn1RITW.png: When the VM is Up, the "display -> type" value in the REST API matches the 'Display' value in the GUI. But when the VM is Down, the "display -> type" value in the REST API matches the 'Graphics Protocol' value in the GUI and does not necessarily match the 'Display' value (e.g. in case we invoked 'Run Once' on the VM with a different Console value). Is there a reason for the values in the REST API to not match the ones in the GUI? it's a bit confusing. Maybe need to have two properties in the REST API to match the two displayed values in the GUI: 'Display' (which, IIUC, is the 'run- time' value) and 'Graphics Protocol' (which, IIUC, is the 'configured'/persisted value)? I understand that there may be backward-compatibility issues with naming/terminology, but perhaps we can come up with a solution that will not break the backward compatibility? (2) in patch http://gerrit.ovirt.org/#/c/35281, it seems that the REST API is calling a query *per VM* in order to re-populate the display-related values. This will potentially overload the engine, especially if we are planning to move the GUI to work over the REST API and request VMs every 5 seconds (by default) per client, as we are doing today. Are there any plans to optimize this behavior (e.g. populate the correct display-related values on the db-side, rather than re- populating them on the REST-API side using a per-VM query)? Many thanks in advance. ---- Regards, Einav

3 4

oVirt 3.6.0 release schedule update
by Sandro Bonazzola 19 Feb '15

19 Feb '15

Hi, here is the proposed schedule for oVirt 3.6.0. These are tentative planning dates and may change: 2015-04-22 - Feature Submission Closed 2015-05-06 - Alpha Release 2015-05-12 - Alpha Release Test Day 2015-06-16 - Feature freeze - Stable branch 2015-07-15 - Beta Release 2015-07-20 - Beta Release Test Day 2015-08-03 - String Freeze 2015-08-19 - Release Candidate 2015-08-24 - Release Candidate Test Day 2015-09-16 - Release Release management page has been updated accordingly: http://www.ovirt.org/OVirt_3.6_Release_Management oVirt Google Calendar has been updated accordingly: ICAL: https://www.google.com/calendar/ical/ppqtk46u9cglj7l987ruo2l0f8%40group.cal… XML: https://www.google.com/calendar/feeds/ppqtk46u9cglj7l987ruo2l0f8%40group.ca… HTML: https://www.google.com/calendar/embed?src=ppqtk46u9cglj7l987ruo2l0f8%40grou… Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

oVirt Node Weekly Meeting Minutes -- 2015-02-16
by Fabian Deutsch 19 Feb '15

19 Feb '15

Minutes: http://ovirt.org/meetings/ovirt/2015/ovirt.2015-02-16-15.00.html Minutes (text): http://ovirt.org/meetings/ovirt/2015/ovirt.2015-02-16-15.00.txt Log: http://ovirt.org/meetings/ovirt/2015/ovirt.2015-02-16-15.00.log.html ================================= #ovirt: oVirt Node Weekly Meeting ================================= Meeting started by fabiand at 15:00:02 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2015/ovirt.2015-02-16-15.00.log.html . Meeting summary --------------- * Agenda (fabiand, 15:00:10) * oVirt 3.5 (fabiand, 15:00:14) * oVirt 3.6 planning (fabiand, 15:00:27) * Other Items (fabiand, 15:00:32) * oVirt 3.5 (fabiand, 15:00:40) * oVirt 3.5 is there (fabiand, 15:03:57) * Official ISO builds are pending (fabiand, 15:04:04) * Idea: Only provide stable Jenkins builds. (fabiand, 15:04:13) * Limit releases to tarballs (fabiand, 15:04:23) * Build rpms and iso in jenkins (fabiand, 15:04:34) * ACTION: tlitovsk to review existnig jobs and clean them up (fabiand, 15:06:24) * ACTION: tlitovsk to create job pulling in stable packages (fabiand, 15:06:32) * oVirt 3.6 planning (fabiand, 15:06:54) * Node team decided to drop the custom installer and custom setup TUI (fabiand, 15:10:00) * Replacements will be anaconda (for installation) and cockpit (for administration) (fabiand, 15:10:20) * Moving to a minimal kickstart approach (fabiand, 15:11:20) * ACTION: tlitovsk to open a feature page for the Cockpit feature (fabiand, 15:16:35) * Other Items (fabiand, 15:17:42) Meeting ended at 15:19:54 UTC. Action Items ------------ * tlitovsk to review existnig jobs and clean them up * tlitovsk to create job pulling in stable packages * tlitovsk to open a feature page for the Cockpit feature Action Items, by person ----------------------- * tlitovsk * tlitovsk to review existnig jobs and clean them up * tlitovsk to create job pulling in stable packages * tlitovsk to open a feature page for the Cockpit feature * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * fabiand (61) * tlitovsk (5) * bkp (3) * ovirtbot (2) * rbarry (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

CI and infra request
by David Caro 18 Feb '15

18 Feb '15

--lEGEL1/lMxI0MVQ2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! I'd like to make a request to all the ovirt developers ad contributors regarding the CI and infra of the project. As you know, the environment is not as stable as it should, and at the infra team we don't have enough manpower to maintain it by ourselves [1], so I'm asking you for help, the main ways that you can help us is: * Notifying us of any unattended errors in the tests if they look infra rel= ated - You can open tickets to trac here [2] * Helping troubleshoot non-working jobs * Helping migrate jobs to yaml [3] * Helping migrate jobs to the new automation structure [4] [1] Doing a rough quick ugly math, yesterday we ran 3508 builds of around 4= 59 different jobs, on 27 slaves, and we don't have anyone 100% dedicated to it (I'm the infra member that can spend more time there, and it's not all of i= t). [2] https://fedorahosted.org/ovirt/ [3] http://gerrit.ovirt.org/#/admin/projects/jenkins [4] http://gerrit.ovirt.org/#/c/37653/ Thanks! --=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro(a)redhat.com Web: www.redhat.com RHT Global #: 82-62605 --lEGEL1/lMxI0MVQ2 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU2dzdAAoJEEBxx+HSYmnDF+cH/RDkhNoE/lOnmWiwC++kzoYz NopISSdv4UjqBYtN38Tr8tPVFK4ngdslsB7LhJbI0nLSGXqPDhDsqbRmabhPzSHG yRe+Ivi5MpczjuroszmDP6vSe8oatMNovCAsx88G723NP1bT9hjF7r6ZQFcg7xI5 3pk8BcZ4Q4dGoMoBaVuuMCgUPSsdhpDTGUoEVR4xZmiNrzakN5CyvQ60hSuweCAe ZRAfGCqGWBRv9gHn6mKgrL6EEAyGJAbhjpq879/SgK4/+gD0qzw6tU36VgCwVb9U prPF0fOviewcFErxmPA1xSbxYuHHoI9M1lQskhSsDIST+34k5vbkoTUBaVNbMxA= =6Kwa -----END PGP SIGNATURE----- --lEGEL1/lMxI0MVQ2--

3 2

ovirt-guest-agent: Hardcoded uid/gid: okay to remove?
by Cameron Norman 18 Feb '15

18 Feb '15

Hello, In the RPM and debian packaging for ovirt-guest-agent, the UID/GID numbers are hardcoded. I need to remove this to fix a policy violation in Debian. What are the implications of making the uid/gid's dynamically allocated, i.e. why were they hardcoded in the first place? Thank you all, -- Cameron Norman

2 1

Engine on Fedora 21
by Adam Litke 18 Feb '15

18 Feb '15

Hi all, Today I tried running engine on my Fedora 21 laptop. I tried two approaches for deploying jboss: using the ovirt-jboss-as package, and by downloading and unpacking jboss-7.1.1 into /usr/share as I have done in the past. engine-setup runs without errors but when I try to start engine the application does not seem to deploy in jboss and there are no errors reported (engine.log is empty). Is there a reasonable expectation that I should be able to get this working on F21 or am I wasting my time? Does anyone have any ideas on how I can resolve the startup issues? See logs attached... -- Adam Litke

7 16

[QE][ACTION REQUIRED] oVirt 3.6.0 status
by Sandro Bonazzola 18 Feb '15

18 Feb '15

Hi, here's an update on 3.6 status on integration / rel-eng side ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [1] and reviewed by maintainers. Finished the review process, the remaining key milestones for this release will be scheduled. For reference, external project schedules we're tracking are: Fedora 22: 2015-05-19 Fedora 20 End Of Life:2015-06-19 (1 month after Fedora 22 release) Foreman 1.8.0: 2015-04-01 GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 QEMU 2.3.0: 2015-03-27 The tracker bug for 3.6.0 [2] currently shows no blockers. There are 552 bugs [3] targeted to 3.6.0. Excluding node and documentation bugs we have 510 bugs [4] targeted to 3.6.0. NEW ASSIGNED POST Total docs 11 0 0 11 gluster 28 2 1 31 i18n 2 0 0 2 infra 82 10 4 96 integration 56 5 4 65 network 30 2 9 41 node 25 3 3 31 ppc 0 0 1 1 sla 56 3 1 60 spice 1 0 0 1 storage 75 4 5 84 ux 36 1 3 40 virt 74 6 9 89 Total 476 36 40 552 oVirt Live for 3.6 has been rebased on EL7. Nightly builds are available here: http://jenkins.ovirt.org/job/ovirt_live_create_iso/ [1] http://goo.gl/9X3G49 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [3] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_release%3A3.6.0%… [4] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[QE][ACTION NEEDED] oVirt 3.5.2 RC status - branching
by Sandro Bonazzola 18 Feb '15

18 Feb '15

Hi, We're going to start composing oVirt 3.5.2 RC on *2015-02-25 08:00 UTC* from 3.5 branch. In order to stabilize the release a new branch ovirt-engine-3.5.2 will be created from the same git hash used for composing the RC. Maintainers: - Please be sure that 3.5 snapshot allow to create VMs before *2015-02-24 15:00 UTC* - Please be sure that no pending patches are going to block the release before *2015-02-24 15:00 UTC* - If any patch must block the RC release please raise the issue as soon as possible. A release management entry has been added for tracking the schedule of 3.5.2 [0] A bug tracker [1] has been created and currently has one open blocker. Bug ID Whiteboard Status Summary 1161012 infra POST task cleaning utility should erase commands that have running tasks Yair, can you please provide ETA for this? There are still 46 bugs [2] targeted to 3.5.2. Excluding node and documentation bugs we still have 37 bugs [3] targeted to 3.5.2. Whiteboard NEW ASSIGNED POST Total 0 1 0 1 docs 1 0 0 1 gluster 4 0 1 5 infra 2 2 3 7 integration 9 0 0 9 network 0 1 0 1 node 4 0 1 5 ppc 0 0 1 1 sla 4 0 0 4 storage 8 0 0 8 ux 1 0 0 1 virt 1 0 2 3 Total 34 4 8 46 Maintainers / Assignee: - Please add the bugs to the tracker if you think that 3.5.2 should not be released without them fixed. - Please update the target to 3.5.3 or later for bugs that won't be in 3.5.2: 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] [0] http://www.ovirt.org/OVirt_3.5.z_Release_Management#oVirt_3.5.2 [1] http://bugzilla.redhat.com/1186161 [2] http://goo.gl/crVJPH [3] http://goo.gl/2qTZZU [4] http://www.ovirt.org/OVirt_3.5.2_Release_Notes [5] http://www.ovirt.org/Testing/oVirt_3.5.2_Testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0