Re: [ovirt-devel] planned Jenkins restart

[Evgheni Dereveanchin]

Maintenance completed, Jenkins is back up and running.
The OS, Jenkins core and all plugins were updated this time:
https://ovirt-jira.atlassian.net/browse/OVIRT-1760

As always - if you see any issues please report them to Jira.

Regards,
Evgheni Dereveanchin

On Wed, Nov 22, 2017 at 12:46 AM, Evgheni Dereveanchin 
wrote:

> Hi everyone,
>
> I'll be performing a planned Jenkins restart within the next hour.
> No new jobs will be scheduled during this maintenance period.
> I will inform you once it is over.
>
> Regards,
> Evgheni Dereveanchin
>



-- 
Regards,
Evgheni Dereveanchin
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] planned Jenkins restart

[Evgheni Dereveanchin]

Hi everyone,

I'll be performing a planned Jenkins restart within the next hour.
No new jobs will be scheduled during this maintenance period.
I will inform you once it is over.

Regards,
Evgheni Dereveanchin
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Question about availability of image-io in ovirt master repo

[Nir Soffer]

On Tue, Nov 21, 2017 at 9:38 PM Idan Shaby  wrote:

> So that what it gives me:
> - el6 - nothing.
> - el7:
> ovirt-imageio-common-0:1.2.0-0.201711211045.gitd4425c0.el7.centos.noarch
> ovirt-imageio-daemon-0:1.2.0-0.201711211045.gitd4425c0.el7.centos.noarch
> ovirt-imageio-proxy-0:1.2.0-0.201711211045.gitd4425c0.el7.centos.noarch
>
> ovirt-imageio-proxy-setup-0:1.2.0-0.201711211045.gitd4425c0.el7.centos.noarch
> - fc27 - nothing.
> - fc26:
> ovirt-imageio-common-0:1.2.0-0.201711211044.gitd4425c0.fc26.noarch
> ovirt-imageio-daemon-0:1.2.0-0.201711211044.gitd4425c0.fc26.noarch
> ovirt-imageio-proxy-0:1.2.0-0.201711211044.gitd4425c0.fc26.noarch
> ovirt-imageio-proxy-setup-0:1.2.0-0.201711211044.gitd4425c0.fc26.noarch
> - fc25:
> ovirt-imageio-common-0:1.2.0-0.201711211044.gitd4425c0.fc25.noarch
> ovirt-imageio-daemon-0:1.2.0-0.201711211044.gitd4425c0.fc25.noarch
> ovirt-imageio-proxy-0:1.2.0-0.201711211044.gitd4425c0.fc25.noarch
> ovirt-imageio-proxy-setup-0:1.2.0-0.201711211044.gitd4425c0.fc25.noarch
> fc24 - nothing.
>
> So I guess it means we don't deliver imageio1.2.0 on el6, fc27 and fc24.
> fc27 should be a problem, right?
>

I hope that tomorrow we will have also fc27 and fcraw, but these are not
supported platforms yet.

Looks like we can require 1.2 in vdsm.


>
> Regards,
> Idan
>
> -- Forwarded message --
> From: Barak Korren 
> Date: Tue, Nov 21, 2017 at 9:27 PM
> Subject: Re: Question about availability of image-io in ovirt master repo
> To: Idan Shaby 
> Cc: infra 
>
>
> On 21 November 2017 at 21:04, Idan Shaby  wrote:
> > Hi,
> >
> > How do I check if our ovirt master repos contain version 1.2.0 of
> > ovirt-imageio-common and ovirt-imageio-daemon?
> > I want to add these requirements to vdsm and I am not sure how to verify
> it.
>
> This searches for a certain package in a certain repo:
>
> repoquery --repofrompath=r,
> http://resources.ovirt.org/repos/ovirt/tested/master/rpm/el7
> --repoid=r
> 
> list '*imageio*'
>

Adding devel, may be useful for people adding dependencies.


>
> You can change the url slightly to check for other distros and oVirt
> versions.
>
> --
> Barak Korren
> RHV DevOps team , RHCE, RHCi
> Red Hat EMEA
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
>
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] oVirt CI now supports Fedora 27 and Fedora Rawhide

[Nir Soffer]

On Tue, Nov 21, 2017 at 6:32 PM Barak Korren  wrote:

> On 21 November 2017 at 18:09, Nir Soffer  wrote:
> > ovirt-imageio builds are fine now on fedora 27 and rawhide (thanks
> Barak!).
> >
> > If the publisher is ok, we will have ovirt-imageio packages that vdsm
> master
> > can consume tomorrow.
> >
> Was there any patch merged after the jobs were created?
>
> If if was about an hour ago, and OST is passing, it should be in
> tested already, no need to wait for the publisher...
>

First merge was at 6:15
https://gerrit.ovirt.org/#/c/83965/


>
>
> --
> Barak Korren
> RHV DevOps team , RHCE, RHCi
> Red Hat EMEA
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] oVirt CI now supports Fedora 27 and Fedora Rawhide

[Barak Korren]

On 21 November 2017 at 18:09, Nir Soffer  wrote:
> ovirt-imageio builds are fine now on fedora 27 and rawhide (thanks Barak!).
>
> If the publisher is ok, we will have ovirt-imageio packages that vdsm master
> can consume tomorrow.
>
Was there any patch merged after the jobs were created?

If if was about an hour ago, and OST is passing, it should be in
tested already, no need to wait for the publisher...


-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] oVirt CI now supports Fedora 27 and Fedora Rawhide

[Nir Soffer]

ovirt-imageio builds are fine now on fedora 27 and rawhide (thanks Barak!).

If the publisher is ok, we will have ovirt-imageio packages that vdsm master
can consume tomorrow.

On Tue, Nov 21, 2017 at 9:52 AM Barak Korren  wrote:

> On 20 November 2017 at 20:23, Nir Soffer  wrote:
> >
> >
> > On Mon, Nov 20, 2017 at 7:16 PM Piotr Kliczewski 
> > wrote:
> >>
> >> On Mon, Nov 20, 2017 at 5:00 PM, Piotr Kliczewski
> >>  wrote:
> >>>
> >>> On Mon, Nov 20, 2017 at 4:57 PM, Barak Korren 
> wrote:
> >>>
> >>> > On 20 November 2017 at 17:09, Piotr Kliczewski 
> >>> > wrote:
> >>> >>
> >>> >> @Barak can we fix it?
> >>> >>
> >>> >
> >>> > Why are you trying to use lago repos in check-patch?
> >>> > There is no cf27/rawhide build of Lago yet, maybe just remove them
> >>> > from the appropriate *.repo files?
> >>> >
> >>>
> >>> repo file reuse, will fix
> >>>
> >>
> >> I removed repos not available on fc27/fcraw and I got failures [1][2]:
> >>
> >> ImportError: No module named ovirt_imageio_common
> >>
> >> I see that [3] repo is not available for fcraw. I see that [4], [5] and
> >> [6] are not available for both.
> >>
> >> It seems that we are not ready for enabling the jobs for both os
> versions.
> >> Maybe we should consider revert of [7].
> >
> > Right, we must enable the fc27 and fcraw in ovirt-imageio first, and
> until
> > the package is published in ovirt repos.
> >
> > Alternatively, we can consume the packages from fc26 repos.
> >
> > My patch for ovirt-imageio was not reviewed yet, hopefully Daniel will
> > review it soon :-)
>
> I disabled the FC27 and FCRAW jobs for vdsm until the 'ovirt-imageio'
> patches are merged and we have FC27/FCRAW builds
>
>
> --
> Barak Korren
> RHV DevOps team , RHCE, RHCi
> Red Hat EMEA
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Adding s390 support to oVirt

[Dan Horák]

On Mon, 20 Nov 2017 09:24:00 +0100
Martin Sivak  wrote:

> Dan Horak used to be part of this project. Lets see if he still
> remembers that.
> 
> Dan: Can you please tell us how the s390 builds in Fedora are/were
> done when no hw was available?

AFAIK Fedora was always building its packages on real mainframe HW,
using a dedicated LPAR on the Red Hat's machine.


Dan
 
> Martin Sivak
> 
> On Sat, Nov 18, 2017 at 12:14 PM, Barak Korren 
> wrote:
> > On 16 November 2017 at 19:38, Martin Sivak 
> > wrote:
> >>> Koji is very opinionated about how RPMs and specfiles should look,
> >>> AFAIK
> >>
> >> Actually, koji does not care much. Fedora packaging rules are
> >> enforced by package reviewers.
> >>
> >>> More specifically, Koji usually assumes the starting point for the
> >>> build process would be a specfile
> >>
> >> This is correct though.
> >>
> >>> Does fedora have an s390x server associated to it?
> >>
> >> They used to have s390 emulators running for that purpose iirc.
> >
> > I wonder if someone could provide more information about this. Is
> > this done via qemu? Or built-in to mock perhaps? It this exists, I
> > can pave the way to enabling s390x build support on oVirt infra.
> >
> >
> > --
> > Barak Korren
> > RHV DevOps team , RHCE, RHCi
> > Red Hat EMEA
> > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Adding s390 support to oVirt

[Dan Horák]

On Mon, 20 Nov 2017 09:16:48 +0100
Christian Borntraeger  wrote:

> 
> 
> On 11/19/2017 09:53 AM, Barak Korren wrote:
> > On 18 November 2017 at 13:14, Barak Korren 
> > wrote:
> >> On 16 November 2017 at 19:38, Martin Sivak 
> >> wrote:
>  Koji is very opinionated about how RPMs and specfiles should
>  look, AFAIK
> >>>
> >>> Actually, koji does not care much. Fedora packaging rules are
> >>> enforced by package reviewers.
> >>>
>  More specifically, Koji usually assumes the starting point for
>  the build process would be a specfile
> >>>
> >>> This is correct though.
> >>>
>  Does fedora have an s390x server associated to it?
> >>>
> >>> They used to have s390 emulators running for that purpose iirc.
> >>
> >> I wonder if someone could provide more information about this. Is
> >> this done via qemu? Or built-in to mock perhaps? It this exists, I
> >> can pave the way to enabling s390x build support on oVirt infra.
> > 
> > There seems to be a 'qemu-system-s390x.x86_64' package avalable for
> > CentOS7 in EPEL, so we might be able to use that to get some
> > emulated s390x Jenkins slaves up. As none of the oVirt infra team
> > members is currently experienced with using this, we would
> > appreciate so help there with:
> 
> qemu s390x emulation does not work with code compiled for z12.
> Would a real virtual machine be what you need?
> The Fedora team DOES have access to a z13. Not sure how much
> resources are available, but can you contact Dan Horak (on cc) if
> there is enough spare capacity.

Christian is right, we have a publicly accessible guest running Fedora
on the Marist College z13 mainframe. It's currently used by ~5 projects
(for example glibc and qemu) as their build and CI host, so adding
another project depends how intensive ovirt's usage would be.


Dan

> 
> 
> 
> > * Figuring out the right libvirt commands to get an s390x VM running
> > on an x86_64 host.
> > * Figuring out the right way to get an OS image for that VM
> > (Probably using virt-install to run the Fedora installer)
> > * Making sure some JVM is available in those VMs
> > 
> > Once we have that, the rest is quite straight forward.
> > 
> > I've created a Jira ticket to map out, discuss and track the
> > required steps: https://ovirt-jira.atlassian.net/browse/OVIRT-1772
> > 
> > WRT the OS we would use, I can see there are s390x Fedora builds
> > available but no CentOS builds, is there ongoing work to remedy
> > this, we'd rather not have to upgrade our Jenkins slaves every 6
> > months...
> > 
> > As a side note - at this time it seems we would have to manually
> > spin up the s390x VMs with libvirt. It would be awesome if oVirt
> > could get support for foreign architecture emulation at some point.
> > 
> 
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel