- Devel - oVirt List Archives

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

Announcing the moVirt Incubator Project!
by Brian Proffitt 17 Feb '15

17 Feb '15

This message is to announce moVirt as a new oVirt incubator project, approved by unanimous vote of the Board mailing list! Details about the project can be found at http://www.ovirt.org/Project_moVirt More information about the incubator at oVirt can be found at http://www.ovirt.org/Incubating_an_oVirt_Subproject Please check out this project and see what you can do to help! -- 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

python-cpopen
by Sandro Bonazzola 16 Feb '15

16 Feb '15

Hi, I'm looking at python-cpopen package as missing dependency for building VDSM within CentOS Virt SIG. I see that Fedora and EPEL have version 1.3 but I see that our git repository has the following tags: $ git remote -v origin git://gerrit.ovirt.org/cpopen (fetch) origin git://gerrit.ovirt.org/cpopen (push) $ git tag --list 1.3.0 1.3.1 v1.4 We don't have jenkins build for cpopen, we rely on Fedora and EPEL releases. I see also that the tar.gz used for building the Fedora RPM is not matching any of the above tags: http://bronhaim.fedorapeople.org/cpopen-1.3.tar.gz and it doesn't exist anymore. I suggest to build cpopen-1.4 from v1.4 tag and publish the .tar.gz on oVirt site. Then bump version on Fedora and EPEL to 1.4 accordingly. Please keep aligned tags and tarball versions or it will become a nightmare to track issues between them. That said, is v1.4 to be considered as formally released? Should I build from that tag for CentOS Virt SIG? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

oVirt Node weekly meeting
by Fabian Deutsch 16 Feb '15

16 Feb '15

------=_Part_3417252_1759919631.1424096638070 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit The following meeting has been modified: Subject: oVirt Node weekly meeting Organiser: "Fabian Deutsch" <fdeutsch(a)redhat.com> Location: irc://irc.oftc.net#ovirt Time: 4:00:00 PM - 4:30:00 PM GMT +01:00 Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna [MODIFIED] Recurrence : Every Monday No end date Effective 16 Feb, 2015 Invitees: devel(a)ovirt.org *~*~*~*~*~*~*~*~*~* Hey, this is an invitation to the weekly oVirt Node devel meetings. Anyone interested or related to Node development is welcome. ------=_Part_3417252_1759919631.1424096638070 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html><body> <pre style="font-family: monospace; font-size: 14px"> The following meeting has been modified: Subject: oVirt Node weekly meeting Organiser: "Fabian Deutsch" <fdeutsch(a)redhat.com> Location: irc://irc.oftc.net#ovirt Time: 4:00:00 PM - 4:30:00 PM GMT +01:00 Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna [MODIFIED] Recurrence : Every Monday No end date Effective 16 Feb, 2015 Invitees: devel(a)ovirt.org *~*~*~*~*~*~*~*~*~* Hey, this is an invitation to the weekly oVirt Node devel meetings. Anyone interested or related to Node development is welcome.</pre> </body></html> ------=_Part_3417252_1759919631.1424096638070 Content-Type: text/calendar; charset=utf-8; method=REQUEST; name=meeting.ics Content-Transfer-Encoding: 7bit BEGIN:VCALENDAR PRODID:Zimbra-Calendar-Provider VERSION:2.0 METHOD:REQUEST BEGIN:VTIMEZONE TZID:Europe/Berlin BEGIN:STANDARD DTSTART:16010101T030000 TZOFFSETTO:+0100 TZOFFSETFROM:+0200 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU TZNAME:CET END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020000 TZOFFSETTO:+0200 TZOFFSETFROM:+0100 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1SU TZNAME:CEST END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:880f897a-b75e-47b7-abf6-24d1e4894600 RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=MO SUMMARY:oVirt Node weekly meeting DESCRIPTION:Hey\, \n\nthis is an invitation to the weekly oVirt Node devel m eetings. \nAnyone interested or related to Node development is welcome. LOCATION:irc://irc.oftc.net#ovirt ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE:mailto:devel@ ovirt.org ORGANIZER;CN=Fabian Deutsch:mailto:fdeutsch@redhat.com DTSTART;TZID="Europe/Berlin":20150216T160000 DTEND;TZID="Europe/Berlin":20150216T163000 STATUS:CONFIRMED CLASS:PUBLIC X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY TRANSP:OPAQUE LAST-MODIFIED:20150216T142358Z DTSTAMP:20150216T142358Z SEQUENCE:10 BEGIN:VALARM ACTION:DISPLAY TRIGGER;RELATED=START:-PT5M DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR ------=_Part_3417252_1759919631.1424096638070--

1 0

custom exit codes from engine-setup/cleanup
by Yedidyah Bar David 15 Feb '15

15 Feb '15

Hi all, The patch [1] for [2] is mostly ready. The patch [3] for otopi was already merged (by Alon) to master. It includes the following codes: 0 - success 1 - general error - the default if there was an error 2 - initialization error - returned if there was an error while loading plugins, before actually starting to run them These apply to all otopi-based tools. patch [1], not merged yet, currently adds this code, affecting engine-cleanup: 11 - cleanup called without setup. Returned in addition to the existing message: Could not detect a completed product setup Please use the cleanup utility only after a setup or after an upgrade from an older installation. Comments are welcome: What other codes do you want to see? For automated testing or any other use? Do you think we should group them and allocate somehow? Just add a code whenever needed? If last is 'Yes', no need to think very much about the previous ones... [1] http://gerrit.ovirt.org/35503 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1079726 [3] http://gerrit.ovirt.org/35632 Thanks, -- Didi

3 3

why is it called vdsm?
by Greg Sheremeta 13 Feb '15

13 Feb '15

Why is it called vdsm and not something a little more descriptive and project-related, like "ovirt-agent"? Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme(a)redhat.com

4 3