November 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1773) Fwd: RGD:: Dev Role Permisssion
by Daniel Belenky (oVirt JIRA) 20 Nov '17

20 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1773?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-1773: --------------------------------------- [~gbenhaim(a)redhat.com] can you please reply on his mail? > Fwd: RGD:: Dev Role Permisssion > ------------------------------- > > Key: OVIRT-1773 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1773 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Daniel Belenky > Assignee: infra > > ---------- Forwarded message ---------- > From: Dhanjal Parth <dparth(a)redhat.com> > Date: Mon, Nov 20, 2017 at 11:37 AM > Subject: RGD:: Dev Role Permisssion > To: infra(a)ovirt.org > Hey! > I wanted to build a patch with custom parameters. And as this page > <http://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/> > suggests I should have the 'dev role' permission to do so. > Can you please help with the same? > Regards > Parth Dhanjal > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > DANIEL BELENKY > RHV DEVOPS > EMEA VIRTUALIZATION R&D > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100072)

1 0

[JIRA] (OVIRT-1773) Fwd: RGD:: Dev Role Permisssion
by Gal Ben Haim (oVirt JIRA) 20 Nov '17

20 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1773?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-1773: -------------------------------- Resolution: Fixed Status: Done (was: To Do) > Fwd: RGD:: Dev Role Permisssion > ------------------------------- > > Key: OVIRT-1773 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1773 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Daniel Belenky > Assignee: infra > > ---------- Forwarded message ---------- > From: Dhanjal Parth <dparth(a)redhat.com> > Date: Mon, Nov 20, 2017 at 11:37 AM > Subject: RGD:: Dev Role Permisssion > To: infra(a)ovirt.org > Hey! > I wanted to build a patch with custom parameters. And as this page > <http://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/> > suggests I should have the 'dev role' permission to do so. > Can you please help with the same? > Regards > Parth Dhanjal > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > DANIEL BELENKY > RHV DEVOPS > EMEA VIRTUALIZATION R&D > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100072)

1 0

[JIRA] (OVIRT-1773) Fwd: RGD:: Dev Role Permisssion
by Gal Ben Haim (oVirt JIRA) 20 Nov '17

20 Nov '17

This is a multi-part message in MIME format... ------------=_1511181205-32438-106 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1773?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-1773: ------------------------------------- I've added the dev role to user "dparth" > Fwd: RGD:: Dev Role Permisssion > ------------------------------- > > Key: OVIRT-1773 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1773 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Daniel Belenky > Assignee: infra > > ---------- Forwarded message ---------- > From: Dhanjal Parth <dparth(a)redhat.com> > Date: Mon, Nov 20, 2017 at 11:37 AM > Subject: RGD:: Dev Role Permisssion > To: infra(a)ovirt.org > Hey! > I wanted to build a patch with custom parameters. And as this page > <http://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/> > suggests I should have the 'dev role' permission to do so. > Can you please help with the same? > Regards > Parth Dhanjal > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > DANIEL BELENKY > RHV DEVOPS > EMEA VIRTUALIZATION R&D > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100072) ------------=_1511181205-32438-106 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1773?page=com.atlassian.jira.… ]</pre> <h3>Gal Ben Haim commented on OVIRT-1773:</h3> <p>I've added the dev role to user “dparth”</p> <blockquote><h3>Fwd: RGD:: Dev Role Permisssion</h3> <pre> Key: OVIRT-1773 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1773 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Daniel Belenky Assignee: infra</pre> <p>---------- Forwarded message ---------- From: Dhanjal Parth <dparth(a)redhat.com> Date: Mon, Nov 20, 2017 at 11:37 AM Subject: RGD:: Dev Role Permisssion To: infra(a)ovirt.org Hey! I wanted to build a patch with custom parameters. And as this page <<a href="http://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/">http://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/</a>> suggests I should have the ‘dev role’ permission to do so. Can you please help with the same? Regards Parth Dhanjal <em>____________________________________________</em>_ Infra mailing list Infra(a)ovirt.org <a href="http://lists.ovirt.org/mailman/listinfo/infra">http://lists.ovirt.org/mailman/listinfo/infra</a> — DANIEL BELENKY RHV DEVOPS EMEA VIRTUALIZATION R&D <<a href="https://red.ht/sig">https://red.ht/sig</a>></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100072)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1511181205-32438-106--

1 0

[JIRA] (OVIRT-1773) Fwd: RGD:: Dev Role Permisssion
by Daniel Belenky (oVirt JIRA) 20 Nov '17

20 Nov '17

Daniel Belenky created OVIRT-1773: ------------------------------------- Summary: Fwd: RGD:: Dev Role Permisssion Key: OVIRT-1773 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1773 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Daniel Belenky Assignee: infra ---------- Forwarded message ---------- From: Dhanjal Parth <dparth(a)redhat.com> Date: Mon, Nov 20, 2017 at 11:37 AM Subject: RGD:: Dev Role Permisssion To: infra(a)ovirt.org Hey! I wanted to build a patch with custom parameters. And as this page <http://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/> suggests I should have the 'dev role' permission to do so. Can you please help with the same? Regards Parth Dhanjal _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- DANIEL BELENKY RHV DEVOPS EMEA VIRTUALIZATION R&D <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100072)

1 0

[CQ]: 84359, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests
by oVirt Jenkins 20 Nov '17

20 Nov '17

Change 84359,1 (ovirt-engine-api-model) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/84359/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/73/

1 0

oVirt infra daily report - unstable production jobs - 510
by jenkins＠jenkins.phx.ovirt.org 19 Nov '17

19 Nov '17

------=_Part_368_2086638561.1511132402838 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/510//artifact/exported-a… Cheers, Jenkins ------=_Part_368_2086638561.1511132402838 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 19/11/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> ------=_Part_368_2086638561.1511132402838--

1 0

oVirt infra weekly meeting notes 15.11.2017
by Evgheni Dereveanchin 19 Nov '17

19 Nov '17

Hi everyone, Please find the topics of this week's infra meeting below: PHX DC: - HyperConverged - rebuilt with RPMs from Master - nested KVM hook installed - running VMs attached to Staging - Jenkins - upgrade to 2.73.3 planned OVIRT-1760 <https://ovirt-jira.atlassian.net/browse/OVIRT-1760> - optimize Garbage collection to speed up Jenkins OVIRT-1756 <https://ovirt-jira.atlassian.net/browse/OVIRT-1756> - disk extend attempted but has problems OVIRT-1765 <https://ovirt-jira.atlassian.net/browse/OVIRT-1765> - CI slowdown due to some OST jobs not running in RAM OVIRT-1763 <https://ovirt-jira.atlassian.net/browse/OVIRT-1763> - Fedora 27 release - decommission/upgrade most FC25 systems - add FC27 mirror for “updates” repo OVIRT-1708 <https://ovirt-jira.atlassian.net/browse/OVIRT-1708> Action Items: - Try running Jenkins with our plugins on OpenShift - Add fc24+fc25 to Staging Jenkins -- Regards, Evgheni Dereveanchin

2 1

[JIRA] (OVIRT-1772) s390x build support for oVirt infra
by Barak Korren (oVirt JIRA) 19 Nov '17

19 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1772?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1772: -------------------------------- Description: There has been some recent interest in the community lately in building oVirt node components for the s390x architecture. Here is a list of things we would need in order to enable s390x builds: * Bring up some s390x Jenkins slave VMs, this implies: ** Getting s390x VMs up and running ** Getting an operating system for these VMs ** Getting Java running on these VMs, in order to run the Jenkins agent. * Enable '{{mock_runner.sh}}' to create s390x build environments. * Create '{{build-artifacts}}' jobs for s390x The easiest way get s390x slave VMs would be if we could get our hands on some real s390x machines, just like the ppc64le machines we currently have. But this does not seem to be likely to happen. An alternative would be to use some kind of s390x emulation. This kind of emulation seems to be used by the Fedora project for their s390x builds. A version of qemu that supports s390x is available in EPEL in the '{{qemu-system-s390x}}' package. Once installed, the package adds the following libvirt capabilities structure: {code} <guest> <os_type>hvm</os_type> <arch name='s390x'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-s390x</emulator> <machine maxCpus='255'>s390-virtio</machine> <machine canonical='s390-virtio' maxCpus='255'>s390</machine> <machine maxCpus='255'>s390-ccw-virtio</machine> <machine canonical='s390-ccw-virtio' maxCpus='255'>s390-ccw</machine> <domain type='qemu'/> </arch> <features> <cpuselection/> <deviceboot/> <disksnapshot default='on' toggle='no'/> </features> </guest> {code} So it seems we can get s390x VMs running on our x86_64 hardware. The next issue to tackle would be to get an OS running on these VMs. The seems to be a Fedora s390x release but not a CentOS one. Neither of these projects release an s390x cloud image, so we may end up having to make our own using '{{virt-install}}' or try to convince [Richard Jones|mailto:rjones@redhat.com] to make such images available in '{{virt-builder}}'. Once we have VMs up, we need to turn them into Jenkins slaves. Hopefully the s390x Fedora build includes Java so this may be trivial. To get '{{mock_runner.sh}}' support we would need an appropriates '{{mock}}' configuration files. Suitable files for Fedora on s390x package seems to already be shipped with the '{{mock}}' package, so there is not much to do there besides copying the file into our '{{jenkins}}' repo and making the usual adjustments we typically make to enable proxy and mirrors support. Once we have all of that up and running, adding s390x '{{build-artifacts}}' jobs would be trivial, we'll just have to add the right tags in the JJB YAML. was: There has been some recent interest in the community lately in building oVirt node components for the s390x architecture. Here is a list of things we would need in order to enable s390x builds: * Bring up some s390x Jenkins slave VMs, this implies: ** Getting s390x VMs up and running ** Getting an operating system for these VMs ** Getting Java running on these VMs, in order to run the Jenkins agent. * Enable '{{mock_runner.sh}}' to create s390x build environments. * Create '{{build-artifacts}}' jobs for s390x The easiest way get s390x slave VMs would be if we could get our hands on some real s390x machines, just like the ppc64le machines we currently have. But this does not seem to be likely to happen. An alternative would be to use some kind of s390x emulation. This kind of emulation seems to be used by the Fedora project for their s390x builds. A version of qemu that supports s390x is available in EPEL in the '{{qemu-system-s390x}}' package. Once installed, the package adds the following libvirt capabilities structure: {code} <guest> <os_type>hvm</os_type> <arch name='s390x'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-s390x</emulator> <machine maxCpus='255'>s390-virtio</machine> <machine canonical='s390-virtio' maxCpus='255'>s390</machine> <machine maxCpus='255'>s390-ccw-virtio</machine> <machine canonical='s390-ccw-virtio' maxCpus='255'>s390-ccw</machine> <domain type='qemu'/> </arch> <features> <cpuselection/> <deviceboot/> <disksnapshot default='on' toggle='no'/> </features> </guest> {code} So it seems we can get s390x VMs running on our x86_64 hardware. The next issue to tackle would be to get an OS running on these VMs. The seems to be a Fedora s390x release but not a CentOS one. Neither of these projects release an s390x cloud image, so we have end up having to make our own using '{{virt-install}}' or try to convince [Richard Jones|mailto:rjones@redhat.com] to make such images available in '{{virt-builder}}'. Once we have VMs up, we need to turn them into Jenkins slaves. Hopefully the s390x Fedora build includes Java so this may be trivial. To get '{{mock_runner.sh}}' support we would need an appropriates '{{mock}}' configuration files. Suitable files for Fedora on s390x package seems to already be shipped with the '{{mock}}' package, so there is not much to do there besides copying the file into our '{{jenkins}}' repo and making the usual adjustments we typically make to enable proxy and mirrors support. Once we have all of that up and running, adding s390x '{{build-artifacts}}' jobs would be trivial, we'll just have to add the right tags in the JJB YAML. > s390x build support for oVirt infra > ----------------------------------- > > Key: OVIRT-1772 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1772 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: s390x, standard-ci > > There has been some recent interest in the community lately in building oVirt node components for the s390x architecture. > Here is a list of things we would need in order to enable s390x builds: > * Bring up some s390x Jenkins slave VMs, this implies: > ** Getting s390x VMs up and running > ** Getting an operating system for these VMs > ** Getting Java running on these VMs, in order to run the Jenkins agent. > * Enable '{{mock_runner.sh}}' to create s390x build environments. > * Create '{{build-artifacts}}' jobs for s390x > The easiest way get s390x slave VMs would be if we could get our hands on some real s390x machines, just like the ppc64le machines we currently have. But this does not seem to be likely to happen. An alternative would be to use some kind of s390x emulation. This kind of emulation seems to be used by the Fedora project for their s390x builds. A version of qemu that supports s390x is available in EPEL in the '{{qemu-system-s390x}}' package. Once installed, the package adds the following libvirt capabilities structure: > {code} > <guest> > <os_type>hvm</os_type> > <arch name='s390x'> > <wordsize>64</wordsize> > <emulator>/usr/bin/qemu-system-s390x</emulator> > <machine maxCpus='255'>s390-virtio</machine> > <machine canonical='s390-virtio' maxCpus='255'>s390</machine> > <machine maxCpus='255'>s390-ccw-virtio</machine> > <machine canonical='s390-ccw-virtio' maxCpus='255'>s390-ccw</machine> > <domain type='qemu'/> > </arch> > <features> > <cpuselection/> > <deviceboot/> > <disksnapshot default='on' toggle='no'/> > </features> > </guest> > {code} > So it seems we can get s390x VMs running on our x86_64 hardware. The next issue to tackle would be to get an OS running on these VMs. The seems to be a Fedora s390x release but not a CentOS one. Neither of these projects release an s390x cloud image, so we may end up having to make our own using '{{virt-install}}' or try to convince [Richard Jones|mailto:rjones@redhat.com] to make such images available in '{{virt-builder}}'. > Once we have VMs up, we need to turn them into Jenkins slaves. Hopefully the s390x Fedora build includes Java so this may be trivial. > To get '{{mock_runner.sh}}' support we would need an appropriates '{{mock}}' configuration files. Suitable files for Fedora on s390x package seems to already be shipped with the '{{mock}}' package, so there is not much to do there besides copying the file into our '{{jenkins}}' repo and making the usual adjustments we typically make to enable proxy and mirrors support. > Once we have all of that up and running, adding s390x '{{build-artifacts}}' jobs would be trivial, we'll just have to add the right tags in the JJB YAML. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)

1 0

[JIRA] (OVIRT-1772) s390x build support for oVirt infra
by Barak Korren (oVirt JIRA) 19 Nov '17

19 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1772?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1772: -------------------------------- Description: There has been some recent interest in the community lately in building oVirt node components for the s390x architecture. Here is a list of things we would need in order to enable s390x builds: * Bring up some s390x Jenkins slave VMs, this implies: ** Getting s390x VMs up and running ** Getting an operating system for these VMs ** Getting Java running on these VMs, in order to run the Jenkins agent. * Enable '{{mock_runner.sh}}' to create s390x build environments. * Create '{{build-artifacts}}' jobs for s390x The easiest way get s390x slave VMs would be if we could get our hands on some real s390x machines, just like the ppc64le machines we currently have. But this does not seem to be likely to happen. An alternative would be to use some kind of s390x emulation. This kind of emulation seems to be used by the Fedora project for their s390x builds. A version of qemu that supports s390x is available in EPEL in the '{{qemu-system-s390x}}' package. Once installed, the package adds the following libvirt capabilities structure: {code} <guest> <os_type>hvm</os_type> <arch name='s390x'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-s390x</emulator> <machine maxCpus='255'>s390-virtio</machine> <machine canonical='s390-virtio' maxCpus='255'>s390</machine> <machine maxCpus='255'>s390-ccw-virtio</machine> <machine canonical='s390-ccw-virtio' maxCpus='255'>s390-ccw</machine> <domain type='qemu'/> </arch> <features> <cpuselection/> <deviceboot/> <disksnapshot default='on' toggle='no'/> </features> </guest> {code} So it seems we can get s390x VMs running on our x86_64 hardware. The next issue to tackle would be to get an OS running on these VMs. The seems to be a Fedora s390x release but not a CentOS one. Neither of these projects release an s390x cloud image, so we have end up having to make our own using '{{virt-install}}' or try to convince [Richard Jones|mailto:rjones@redhat.com] to make such images available in '{{virt-builder}}'. Once we have VMs up, we need to turn them into Jenkins slaves. Hopefully the s390x Fedora build includes Java so this may be trivial. To get '{{mock_runner.sh}}' support we would need an appropriates '{{mock}}' configuration files. Suitable files for Fedora on s390x package seems to already be shipped with the '{{mock}}' package, so there is not much to do there besides copying the file into our '{{jenkins}}' repo and making the usual adjustments we typically make to enable proxy and mirrors support. Once we have all of that up and running, adding s390x '{{build-artifacts}}' jobs would be trivial, we'll just have to add the right tags in the JJB YAML. was: There has been some recent interest in the community lately in building oVirt node components for the s390x architecture. Here is a list of things we would need in order to enable s390x builds: * Bring up some s390x Jenkins slave VMs, this implies: ** Getting s390x VMs up and running ** Getting an operating system for these VMs ** Getting Java running on these VMs, in order to run the Jenkins agent. * Enable '{{mock_runner.sh}}' to create s390x build environments. * Create '{{build-artifacts}}' jobs for s390x The easiest way get s390x slave VMs would be if we could get our hands on some real s390x machines, just like the ppc64le machines we currently have. But this does not seem to be likely to happen. An alternative would be to use some kind of s390x emulation. This kind of emulation seems to be used by the Fedora project for their s390x builds. A version of qemu that supports s390x is available in EPEL in the '{{qemu-system-s390x}}' package. Once installed, the package adds the following libvirt capabilities structure: {code} <guest> <os_type>hvm</os_type> <arch name='s390x'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-s390x</emulator> <machine maxCpus='255'>s390-virtio</machine> <machine canonical='s390-virtio' maxCpus='255'>s390</machine> <machine maxCpus='255'>s390-ccw-virtio</machine> <machine canonical='s390-ccw-virtio' maxCpus='255'>s390-ccw</machine> <domain type='qemu'/> </arch> <features> <cpuselection/> <deviceboot/> <disksnapshot default='on' toggle='no'/> </features> </guest> {code} So it seems we can get s390x VMs running on our x86_64 hardware. The next issue to tackle would be to get an OS running on these VMs. The seems to be a Fedora s390x release but not a CentOS one. Neither of these projects release an s390x cloud image, so we have end up having to make our own using '{{virt-install}}' or try to convince [Richard Jones|mailto:rjones@redhat.com] to make such images available in '{{virt-builder}}'. Once we have VMs up, we need to turn them into Jenkins slaves, hopefully the s390x Fedora build includes Java, so this me be trivial. To get '{{mock_runner.sh}}' support we would need an appropriates '{{mock}}' configuration files. Suitable files for Fedora on s390x package seems to already be shipped with the '{{mock}}' package, so there is not much to do there besides copying the file into our '{{jenkins}}' repo and making the usual adjustments we typically make to enable proxy and mirrors support. Once we have all of that up and running, adding s390x '{{build-artifacts}}' jobs would be trivial, we'll just have to add the right tags in the JJB YAML. > s390x build support for oVirt infra > ----------------------------------- > > Key: OVIRT-1772 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1772 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: s390x, standard-ci > > There has been some recent interest in the community lately in building oVirt node components for the s390x architecture. > Here is a list of things we would need in order to enable s390x builds: > * Bring up some s390x Jenkins slave VMs, this implies: > ** Getting s390x VMs up and running > ** Getting an operating system for these VMs > ** Getting Java running on these VMs, in order to run the Jenkins agent. > * Enable '{{mock_runner.sh}}' to create s390x build environments. > * Create '{{build-artifacts}}' jobs for s390x > The easiest way get s390x slave VMs would be if we could get our hands on some real s390x machines, just like the ppc64le machines we currently have. But this does not seem to be likely to happen. An alternative would be to use some kind of s390x emulation. This kind of emulation seems to be used by the Fedora project for their s390x builds. A version of qemu that supports s390x is available in EPEL in the '{{qemu-system-s390x}}' package. Once installed, the package adds the following libvirt capabilities structure: > {code} > <guest> > <os_type>hvm</os_type> > <arch name='s390x'> > <wordsize>64</wordsize> > <emulator>/usr/bin/qemu-system-s390x</emulator> > <machine maxCpus='255'>s390-virtio</machine> > <machine canonical='s390-virtio' maxCpus='255'>s390</machine> > <machine maxCpus='255'>s390-ccw-virtio</machine> > <machine canonical='s390-ccw-virtio' maxCpus='255'>s390-ccw</machine> > <domain type='qemu'/> > </arch> > <features> > <cpuselection/> > <deviceboot/> > <disksnapshot default='on' toggle='no'/> > </features> > </guest> > {code} > So it seems we can get s390x VMs running on our x86_64 hardware. The next issue to tackle would be to get an OS running on these VMs. The seems to be a Fedora s390x release but not a CentOS one. Neither of these projects release an s390x cloud image, so we have end up having to make our own using '{{virt-install}}' or try to convince [Richard Jones|mailto:rjones@redhat.com] to make such images available in '{{virt-builder}}'. > Once we have VMs up, we need to turn them into Jenkins slaves. Hopefully the s390x Fedora build includes Java so this may be trivial. > To get '{{mock_runner.sh}}' support we would need an appropriates '{{mock}}' configuration files. Suitable files for Fedora on s390x package seems to already be shipped with the '{{mock}}' package, so there is not much to do there besides copying the file into our '{{jenkins}}' repo and making the usual adjustments we typically make to enable proxy and mirrors support. > Once we have all of that up and running, adding s390x '{{build-artifacts}}' jobs would be trivial, we'll just have to add the right tags in the JJB YAML. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)

1 0

[JIRA] (OVIRT-1772) s390x build support for oVirt infra
by Barak Korren (oVirt JIRA) 19 Nov '17

19 Nov '17

Barak Korren created OVIRT-1772: ----------------------------------- Summary: s390x build support for oVirt infra Key: OVIRT-1772 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1772 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra There has been some recent interest in the community lately in building oVirt node components for the s390x architecture. Here is a list of things we would need in order to enable s390x builds: * Bring up some s390x Jenkins slave VMs, this implies: ** Getting s390x VMs up and running ** Getting an operating system for these VMs ** Getting Java running on these VMs, in order to run the Jenkins agent. * Enable '{{mock_runner.sh}}' to create s390x build environments. * Create '{{build-artifacts}}' jobs for s390x The easiest way get s390x slave VMs would be if we could get our hands on some real s390x machines, just like the ppc64le machines we currently have. But this does not seem to be likely to happen. An alternative would be to use some kind of s390x emulation. This kind of emulation seems to be used by the Fedora project for their s390x builds. A version of qemu that supports s390x is available in EPEL in the '{{qemu-system-s390x}}' package. Once installed, the package adds the following libvirt capabilities structure: {code} <guest> <os_type>hvm</os_type> <arch name='s390x'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-s390x</emulator> <machine maxCpus='255'>s390-virtio</machine> <machine canonical='s390-virtio' maxCpus='255'>s390</machine> <machine maxCpus='255'>s390-ccw-virtio</machine> <machine canonical='s390-ccw-virtio' maxCpus='255'>s390-ccw</machine> <domain type='qemu'/> </arch> <features> <cpuselection/> <deviceboot/> <disksnapshot default='on' toggle='no'/> </features> </guest> {code} So it seems we can get s390x VMs running on our x86_64 hardware. The next issue to tackle would be to get an OS running on these VMs. The seems to be a Fedora s390x release but not a CentOS one. Neither of these projects release an s390x cloud image, so we have end up having to make our own using '{{virt-install}}' or try to convince [Richard Jones|mailto:rjones@redhat.com] to make such images available in '{{virt-builder}}'. Once we have VMs up, we need to turn them into Jenkins slaves, hopefully the s390x Fedora build includes Java, so this me be trivial. To get '{{mock_runner.sh}}' support we would need an appropriates '{{mock}}' configuration files. Suitable files for Fedora on s390x package seems to already be shipped with the '{{mock}}' package, so there is not much to do there besides copying the file into our '{{jenkins}}' repo and making the usual adjustments we typically make to enable proxy and mirrors support. Once we have all of that up and running, adding s390x '{{build-artifacts}}' jobs would be trivial, we'll just have to add the right tags in the JJB YAML. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)

1 0