oVirt infra daily report - unstable production jobs - 510
by jenkins＠jenkins.phx.ovirt.org
------=_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...
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--
6 years, 10 months
[JIRA] (OVIRT-1772) s390x build support for oVirt infra
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1772?page=com.atlassian.jir... ]
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)
6 years, 10 months
[JIRA] (OVIRT-1772) s390x build support for oVirt infra
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1772?page=com.atlassian.jir... ]
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)
6 years, 10 months
[JIRA] (OVIRT-1772) s390x build support for oVirt infra
by Barak Korren (oVirt JIRA)
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)
6 years, 10 months
