- Infra - oVirt List Archives

Get Involved with oVirt project! Spring edition
by Sandro Bonazzola 30 Mar '16

30 Mar '16

Hi, Have you got some free time and do you want to get involved in oVirt project? Do you like the idea of having fresh disk images of recent distribution in oVirt Glance repository? You can help us by testing existing online images ensuring they works with cloud-init or creating one yourself and report your success to devel(a)ovirt.org. We'll be happy to upload the images once these are ready. Do you like Debian and do you have some programming or packaging skills? Help us getting Vdsm running on it! We work on inclusion of Vdsm into Debian. We need to test and fix Vdsm Debian packages to make them working before the next Debian freeze. You can find all current Debian work (Vdsm and related packages) in Debian git repositories [10]. You can follow the progress and participate on oVirt development mailing list [11]. Here are some bugs you can try to help with: 1159784 ovirt-engine Documentation NEW [RFE] Document when and where new features are available ... 1074301 ovirt-engine-cli RFEs NEW [RFE] ovirt-shell has no man page 772931 ovirt-engine-reports RFEs NEW [RFE] Reports should include the name of the oVirt engine 1120585 ovirt-image-uploader Documentation NEW update image uploader documentation 1120586 ovirt-iso-uploader Documentation NEW update iso uploader documentation 1120588 ovirt-log-collector Documentation NEW update log collector documentation 1237132 ovirt-engine Setup.Engine NEW [TEXT] New package listing of engine-setup when upgrading... 1115059 ovirt-engine General ASSIGNED Incomplete error message when adding VNIC profile to runn... Are you great at packaging software? Do you prefer a distribution which is currently unsupported by oVirt? Do you want to have packages included in your preferred distribution? Help getting oVirt ported there! Fedora: http://lists.ovirt.org/pipermail/devel/2015-September/011426.html CentOS: https://wiki.centos.org/SpecialInterestGroup/Virtualization Gentoo: https://wiki.gentoo.org/wiki/OVirt (GSoC: https://wiki.gentoo.org/wiki/Google_Summer_of_Code/2016/Ideas ) Debian: http://www.ovirt.org/develop/release-management/features/debian-support-for… Archlinux: http://www.ovirt.org/develop/developer-guide/arch-linux/ OpenSUSE: https://build.opensuse.org/project/show/Virtualization:oVirt Do you love "DevOps?", you count stable builds in jenkins ci while trying to fall a sleep? Then oVirt infra team is looking for you!, join the infra team and dive in to do the newest and coolest devops tools today! Here are some of our open tasks you can help with: https://ovirt-jira.atlassian.net/secure/RapidBoard.jspa?rapidView=6 You can also help us by sharing how you use oVirt in your DevOps environment (please use [DevOps] in the subject). You can check out more docs on the DevOps side of oVirt in [12][13] You don't have programming skills, not enough time for DevOps but you want still to contribute? Here are some bugs you can take care of, also without writing a line of code: https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovirt%… Do you prefer to test things? We have some test cases[5] you can try using nightly snapshots[6]. Do you want to contribute test cases? Most of the features[7] included in oVirt are missing a test case, you're welcome to contribute one! Do you want to contribute artworks? oVirt Live backgrounds and covers, release banners, stickers, .... Take a look at Fedora Artworks[9] as an example of what you can do Is this the first time you try to contribute to oVirt project? You can start from here [1][2]! You don't know gerrit very well? You can find some more docs here [3]. Any other question about development? Feel free to ask on devel(a)ovirt.org or on irc channel[4]. You don't really have time / skills for any development / documentation / testing related task? Spread the word[8]! Let us know you're getting involved, present yourself and tell us what you're going to do, you'll be welcome! [1] http://www.ovirt.org/develop/ [2] http://www.ovirt.org/develop/dev-process/working-with-gerrit/ [3] https://gerrit-review.googlesource.com/Documentation [4] http://www.ovirt.org/community/ [5] http://www.ovirt.org/develop/infra/testing/ [6] http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/ [7] http://www.ovirt.org/develop/release-management/features/ [8] http://www.zdnet.com/article/how-much-longer-can-red-hats-ovirt-remain-cove… [9] https://fedoraproject.org/wiki/Artwork#Resources [10] http://git.debian.org [11] http://lists.ovirt.org/mailman/listinfo/devel [12] http://ovirt-infra-docs.readthedocs.org/en/latest/ [13] http://www.ovirt.org/develop/infra/infrastructure-documentation/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[JIRA] (OVIRT-460) set up another slave for ovirt -system-test
by Anatoly (oVirt JIRA) 30 Mar '16

30 Mar '16

Anatoly created OVIRT-460: ----------------------------- Summary: set up another slave for ovirt -system-test Key: OVIRT-460 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-460 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Anatoly Assignee: infra Please bring up srv10 in phx for the node system tests -- This message was sent by Atlassian JIRA (v7.2.0-OD-04-029#72002)

1 0

[ATN] old artifactory server is being shutdown
by Eyal Edri 30 Mar '16

30 Mar '16

FYI, We're shutting down old artifactory.ovirt.org server on alterway02 (isn't being used for a few months now), as we're using the new VM running on PHX. If no issues will arise in the following days the VM will be deleted as part of cleanup and the migration process to PHX. If you encounter any issues in the next few days with Jenkins regarding artifactory, please contact the infra team. /oVirt infra team.

1 0

[ATN] [ACTION REQUIRED] Tweaking engine CI flow
by Roy Golan 30 Mar '16

30 Mar '16

Hi all, Eyal and I sat together to analyse and tweak the engine CI and this is what we came up with: - dao test excludes updated - exclude dal/src/main/bundles from invoking dao tests A trivial update of validation messages without any db change would trigger dao test without any need. This is one less job run for lots of patches. This change is effective now. - Spare CI re-run on trivial rebases Gerrit trigger supports suppressing itself if the change to the tree was trivial. Most of the waste of resources(time and IO :) ) is around rebasing a change and waiting for CI to rerun. if Change1 is ci+1 and Change2 is ci+1 the chances that they will break CI together is very small and taking that risk is most probably worth it due to the huge resources waste This change isn't effective yet - *Please reply here* if you agree or not to make this change available. All of this is 'master' - 3.6 will follow if we will agree on activating that change. Thanks, Roy

4 6

[JIRA] (OVIRT-459) create ovirt-system-tests feature page on ovirt.org
by Yaniv Kaul (oVirt JIRA) 30 Mar '16

30 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-459?page=com.atlassian.jira.p… ] Yaniv Kaul commented on OVIRT-459: ---------------------------------- Ideally, yes. I'd separate the test plan (which I hope QE would add a bit) and a simple positive test case to see if we can test this functionality in ovirt-system-tests. > create ovirt-system-tests feature page on ovirt.org > ---------------------------------------------------- > > Key: OVIRT-459 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-459 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > > We need to have a single page on ovirt.org to concentrate all ovirt-system-tests docs and plans per ovirt version. > Ideally we'll want a test plan attached to each feature page in oVirt 4.0 to start with. > [~ykaul] what do you think? -- This message was sent by Atlassian JIRA (v7.2.0-OD-04-029#72002)

1 0

jenkins logs and ovirt-engine_master_upgrade-from-master_el7_merged
by Yedidyah Bar David 30 Mar '16

30 Mar '16

Hi all, On Tue, Mar 29, 2016 at 11:12 PM, Jenkins CI <gerrit2(a)gerrit.ovirt.org> wrote: > Jenkins CI has posted comments on this change. > > Change subject: packaging: spec: Fix deps for ovirt-engine-tools-backup > ...................................................................... > > > Patch Set 2: > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me… : FAILURE This failed due to [1]. Above run 2500 contained the fix, but still failed. Why? Because it started from a broken build. The fix only fixes upgrades from good builds to good builds. I tried to follow the console logs of various runs of this job and have some questions: 1. How do we decide what version to upgrade *from*? 2. I suspect that we pick the last "good" version, with some definition of good, but by the time I am looking at this, there are already newer runs that succeeded, but all those before 2500 failed. Can't see in the web interface older non-failed ones. 3. Also searched my mail and could not find a report. When do we send email? To whom? Is there an archive somewhere? Not that important, now that all is fixed. Asking mainly for my own understanding. [1] https://bugzilla.redhat.com/1321249 > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge… : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_merged/1537… : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-el7-x86_64/21… : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_unit-tests_merged/15408/ : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc23-x86_64/1… : SUCCESS > > -- > To view, visit https://gerrit.ovirt.org/55287 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-MessageType: comment > Gerrit-Change-Id: I2772037157f2f1ba77b3be96c6375558fe3d6582 > Gerrit-PatchSet: 2 > Gerrit-Project: ovirt-engine > Gerrit-Branch: master > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-HasComments: No -- Didi

2 3

No jobs triggered for this event
by Martin Perina 30 Mar '16

30 Mar '16

Hi, could you please take a look at the patch [1]? For some reason unknown to me any build job cannot be trigered for the patch neither automatically nor manually. Thanks Martin [1] https://gerrit.ovirt.org/55407

2 2

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 2346 - Failure!
by jenkins＠ovirt.org 30 Mar '16

30 Mar '16

------=_Part_255_1325727796.1458935120059 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge… Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge… Build Number: 2346 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/54228 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #2346 [Jakub Niedermertl] core: Console stealing fix [Sandro Bonazzola] otopi: add standard ci on master ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_255_1325727796.1458935120059--

1 45

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 2432 - Failure!
by jenkins＠ovirt.org 30 Mar '16

30 Mar '16

------=_Part_134_507391851.1458644250067 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me… Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me… Build Number: 2432 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/55011 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #2432 [Tomas Jelinek] webadmin: the HA flag was not shown in the edit instance type ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_134_507391851.1458644250067--

2 75

[JIRA] (OVIRT-456) Build oVirt 3.6.5 RC1
by sbonazzo (oVirt JIRA) 29 Mar '16

29 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-456?page=com.atlassian.jira.p… ] sbonazzo updated OVIRT-456: --------------------------- Assignee: sbonazzo (was: infra) Status: Accepted (was: New) > Build oVirt 3.6.5 RC1 > --------------------- > > Key: OVIRT-456 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-456 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: sbonazzo > Priority: Highest > -- This message was sent by Atlassian JIRA (v7.2.0-OD-04-029#72002)

1 0