Request for 3 PPC64 vm slaves for Jenkins
Hi, PPC64 support is going to be introduced as new feature in oVirt 3.4.0. So we should start delivering PPC64 packages for arch dependent packages for both EL6 and Fedora. VMs may be small enough since they should only build nightly vdsm and ovirt-host-deploy-offline: 1 core, 512Mb ram, 10Gb disk Software needed: minimal install + vdsm and ovirt-host-deploy-offline build deps. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Mon, Feb 10, 2014 at 08:12:35AM +0100, Sandro Bonazzola wrote:
PPC64 support is going to be introduced as new feature in oVirt 3.4.0. So we should start delivering PPC64 packages for arch dependent packages for both EL6 and Fedora. VMs may be small enough since they should only build nightly vdsm and ovirt-host-deploy-offline: 1 core, 512Mb ram, 10Gb disk Software needed: minimal install + vdsm and ovirt-host-deploy-offline build deps.
Since we only have x86 hardware which run oVirt. Does it have to be a PPC64 VM because I don't think we can host that right now.
Il 10/02/2014 23:15, Ewoud Kohl van Wijngaarden ha scritto:
On Mon, Feb 10, 2014 at 08:12:35AM +0100, Sandro Bonazzola wrote:
PPC64 support is going to be introduced as new feature in oVirt 3.4.0. So we should start delivering PPC64 packages for arch dependent packages for both EL6 and Fedora. VMs may be small enough since they should only build nightly vdsm and ovirt-host-deploy-offline: 1 core, 512Mb ram, 10Gb disk Software needed: minimal install + vdsm and ovirt-host-deploy-offline build deps.
Since we only have x86 hardware which run oVirt. Does it have to be a PPC64 VM because I don't think we can host that right now.
AFAIK we can run qemu-system-ppc64 also on x86_64. Or am I missing something?
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Il 11/02/2014 08:12, Sandro Bonazzola ha scritto:
Il 10/02/2014 23:15, Ewoud Kohl van Wijngaarden ha scritto:
On Mon, Feb 10, 2014 at 08:12:35AM +0100, Sandro Bonazzola wrote:
PPC64 support is going to be introduced as new feature in oVirt 3.4.0. So we should start delivering PPC64 packages for arch dependent packages for both EL6 and Fedora. VMs may be small enough since they should only build nightly vdsm and ovirt-host-deploy-offline: 1 core, 512Mb ram, 10Gb disk Software needed: minimal install + vdsm and ovirt-host-deploy-offline build deps.
Since we only have x86 hardware which run oVirt. Does it have to be a PPC64 VM because I don't think we can host that right now.
AFAIK we can run qemu-system-ppc64 also on x86_64. Or am I missing something?
Alternative is cross compile for ppc64 from x86_64.
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Tue, Feb 11, 2014 at 08:12:45AM +0100, Sandro Bonazzola wrote:
Il 10/02/2014 23:15, Ewoud Kohl van Wijngaarden ha scritto:
On Mon, Feb 10, 2014 at 08:12:35AM +0100, Sandro Bonazzola wrote:
PPC64 support is going to be introduced as new feature in oVirt 3.4.0. So we should start delivering PPC64 packages for arch dependent packages for both EL6 and Fedora. VMs may be small enough since they should only build nightly vdsm and ovirt-host-deploy-offline: 1 core, 512Mb ram, 10Gb disk Software needed: minimal install + vdsm and ovirt-host-deploy-offline build deps.
Since we only have x86 hardware which run oVirt. Does it have to be a PPC64 VM because I don't think we can host that right now.
AFAIK we can run qemu-system-ppc64 also on x86_64. Or am I missing something?
Can we also do this with oVirt as host? Ideally I'd prefer not having to manually host a VM but have oVirt take care of it. Could a VDSM hook possibly solve this if not built in?
------=_Part_1883921_1034057780.1392192482799 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Maybe aline can help here? as you can see we also need POWER pc slaves, so if you can contribute a server which we can run ppc vms on, it will be great both for kimchi and oVirt. Eyal. ----- Original Message -----
From: "Ewoud Kohl van Wijngaarden" <ewoud+ovirt@kohlvanwijngaarden.nl> To: infra@ovirt.org Sent: Wednesday, February 12, 2014 2:13:48 AM Subject: Re: Request for 3 PPC64 vm slaves for Jenkins
On Tue, Feb 11, 2014 at 08:12:45AM +0100, Sandro Bonazzola wrote:
Il 10/02/2014 23:15, Ewoud Kohl van Wijngaarden ha scritto:
On Mon, Feb 10, 2014 at 08:12:35AM +0100, Sandro Bonazzola wrote:
PPC64 support is going to be introduced as new feature in oVirt 3.4.0. So we should start delivering PPC64 packages for arch dependent packages for both EL6 and Fedora. VMs may be small enough since they should only build nightly vdsm and ovirt-host-deploy-offline: 1 core, 512Mb ram, 10Gb disk Software needed: minimal install + vdsm and ovirt-host-deploy-offline build deps.
Since we only have x86 hardware which run oVirt. Does it have to be a PPC64 VM because I don't think we can host that right now.
AFAIK we can run qemu-system-ppc64 also on x86_64. Or am I missing something?
Can we also do this with oVirt as host? Ideally I'd prefer not having to manually host a VM but have oVirt take care of it. Could a VDSM hook possibly solve this if not built in? _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
------=_Part_1883921_1034057780.1392192482799 Content-Type: message/rfc822 Content-Disposition: attachment Return-Path: infra-bounces@ovirt.org Received: from zmta06.collab.prod.int.phx2.redhat.com (LHLO zmta06.collab.prod.int.phx2.redhat.com) (10.5.81.13) by zmail17.collab.prod.int.phx2.redhat.com with LMTP; Mon, 10 Feb 2014 07:07:51 -0500 (EST) Received: from zmta06.collab.prod.int.phx2.redhat.com (localhost [127.0.0.1]) by zmta06.collab.prod.int.phx2.redhat.com (Postfix) with ESMTP id B074416581C; Mon, 10 Feb 2014 07:07:51 -0500 (EST) Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by zmta06.collab.prod.int.phx2.redhat.com (Postfix) with ESMTP id 7C9A1165856; Mon, 10 Feb 2014 07:07:51 -0500 (EST) Received: from mx1.redhat.com (ext-mx15.extmail.prod.ext.phx2.redhat.com [10.5.110.20]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s1AC7lxm024467; Mon, 10 Feb 2014 07:07:47 -0500 Received: from lists.ovirt.org (lists.ovirt.org [173.255.252.138]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s1AC7khH021468; Mon, 10 Feb 2014 07:07:46 -0500 Received: from lists.ovirt.org (localhost [IPv6:::1]) by lists.ovirt.org (Postfix) with ESMTP id E2450C1A6; Mon, 10 Feb 2014 07:07:45 -0500 (EST) X-Original-To: infra@ovirt.org Delivered-To: infra@ovirt.org Received: from e24smtp01.br.ibm.com (e24smtp01.br.ibm.com [32.104.18.85]) by lists.ovirt.org (Postfix) with ESMTP id 05E43C119 for <infra@ovirt.org>; Mon, 10 Feb 2014 07:07:42 -0500 (EST) Received: from /spool/local by e24smtp01.br.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <infra@ovirt.org> from <alinefm@linux.vnet.ibm.com>; Mon, 10 Feb 2014 10:07:40 -0200 Received: from d24dlp02.br.ibm.com (9.18.248.206) by e24smtp01.br.ibm.com (10.172.0.143) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Mon, 10 Feb 2014 10:07:39 -0200 Received: from d24relay03.br.ibm.com (d24relay03.br.ibm.com [9.13.184.25]) by d24dlp02.br.ibm.com (Postfix) with ESMTP id 12F121DC0063 for <infra@ovirt.org>; Mon, 10 Feb 2014 07:07:36 -0500 (EST) Received: from d24av04.br.ibm.com (d24av04.br.ibm.com [9.8.31.97]) by d24relay03.br.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s1AC6vDq16318652 for <infra@ovirt.org>; Mon, 10 Feb 2014 10:06:58 -0200 Received: from d24av04.br.ibm.com (localhost [127.0.0.1]) by d24av04.br.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s1AC7ZsI011571 for <infra@ovirt.org>; Mon, 10 Feb 2014 10:07:35 -0200 Received: from [9.8.1.1] ([9.8.1.1]) by d24av04.br.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s1AC7YLu011551 for <infra@ovirt.org>; Mon, 10 Feb 2014 10:07:34 -0200 Message-ID: <52F8C106.1090303@linux.vnet.ibm.com> Date: Mon, 10 Feb 2014 10:07:34 -0200 From: Aline Manera <alinefm@linux.vnet.ibm.com> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: infra@ovirt.org Subject: About Kimchi X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 14021012-1524-0000-0000-000008CF29E9 X-BeenThere: infra@ovirt.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "List for ovirt.org infrastructure team" <infra.ovirt.org> List-Unsubscribe: <http://lists.ovirt.org/mailman/options/infra>, <mailto:infra-request@ovirt.org?subject=unsubscribe> List-Archive: <http://lists.ovirt.org/pipermail/infra/> List-Post: <mailto:infra@ovirt.org> List-Help: <mailto:infra-request@ovirt.org?subject=help> List-Subscribe: <http://lists.ovirt.org/mailman/listinfo/infra>, <mailto:infra-request@ovirt.org?subject=subscribe> Content-Type: multipart/mixed; boundary="===============0463499158==" Sender: infra-bounces@ovirt.org Errors-To: infra-bounces@ovirt.org X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22 This is a multi-part message in MIME format. --===============0463499158== Content-Type: multipart/alternative; boundary="------------040003060708000808000500" This is a multi-part message in MIME format. --------------040003060708000808000500 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, As I promised in last scrum meeting I am sending this note to introduce Kimchi and myself. Who is Aline? I am software engineer at IBM LTC (Linux Technology Center) and also Kimchi maintainer. What is Kimchi? (https://github.com/kimchi-project/kimchi) Kimchi is an HTML5 based management tool for KVM. It is designed to make it as easy as possible to get started with KVM and create your first guest. Kimchi is supported in RHEL, Fedora, openSUSE and Ubuntu and also in all main browsers: Firefox, Chrome, IE and the mobile ones (Chrome, Safari) And test Kimchi in all those distributions takes too much time. Because that we want to use Jenkins. So we can set up a virtual machine with each distribution, run unit tests, build, install kimchi and run some tests after it. It can be done for each patch sent to review and also nightly builds. I am trying to figure out if it is possible to IBM provide us some slave servers. At the moment I don't have any update about that. But if we're lucky, probably the machines will be POWER (any problem with that?) I will try to always join the infrastructure scrum meeting so I can help on that. Regards, Aline Manera --------------040003060708000808000500 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> <font face="DejaVu Sans Mono">Hi all,<br> <br> As I promised in last scrum meeting I am sending this note to introduce Kimchi and myself.<br> <br> Who is Aline?<br> I am software engineer at IBM LTC (Linux Technology Center) and also Kimchi maintainer.<br> <br> What is Kimchi? (</font><font face="DejaVu Sans Mono"><a class="moz-txt-link-freetext" href="https://github.com/kimchi-project/kimchi">https://github.com/kimchi-project/kimchi</a>)<br> </font>Kimchi is an HTML5 based management tool for KVM.<br> It is designed to make it as easy as possible to get started with KVM and create your first guest.<br> <br> Kimchi is supported in RHEL, Fedora, openSUSE and Ubuntu and also in all main browsers: Firefox, Chrome, IE and the mobile ones (Chrome, Safari)<br> <br> And test Kimchi in all those distributions takes too much time.<br> Because that we want to use Jenkins.<br> So we can set up a virtual machine with each distribution, run unit tests, build, install kimchi and run some tests after it.<br> It can be done for each patch sent to review and also nightly builds.<br> <br> I am trying to figure out if it is possible to IBM provide us some slave servers.<br> At the moment I don't have any update about that. But <span id="result_box" class="short_text" lang="en"><span class="hps">if</span> <span class="hps">we're lucky</span></span>, probably the machines will be POWER (any problem with that?)<br> <br> I will try to always join the infrastructure scrum meeting so I can help on that.<br> <br> Regards,<br> Aline Manera<br> </body> </html> --------------040003060708000808000500-- --===============0463499158== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra --===============0463499158==-- ------=_Part_1883921_1034057780.1392192482799--
On 02/12/2014 06:08 AM, Eyal Edri wrote:
Maybe aline can help here? as you can see we also need POWER pc slaves, so if you can contribute a server which we can run ppc vms on, it will be great both for kimchi and oVirt.
Hi all, I am going through the legal stuffs to get POWER machines from IBM available to ovirt community. But in this first attempt, I am trying to get POWER vms and not a host POWER machine. Sandro, Eyal: Do POWER vms work fine for your proposals? Or you need a host POWER machine?
Eyal.
----- Original Message -----
From: "Ewoud Kohl van Wijngaarden" <ewoud+ovirt@kohlvanwijngaarden.nl> To: infra@ovirt.org Sent: Wednesday, February 12, 2014 2:13:48 AM Subject: Re: Request for 3 PPC64 vm slaves for Jenkins
Il 10/02/2014 23:15, Ewoud Kohl van Wijngaarden ha scritto:
On Mon, Feb 10, 2014 at 08:12:35AM +0100, Sandro Bonazzola wrote:
PPC64 support is going to be introduced as new feature in oVirt 3.4.0. So we should start delivering PPC64 packages for arch dependent packages for both EL6 and Fedora. VMs may be small enough since they should only build nightly vdsm and ovirt-host-deploy-offline: 1 core, 512Mb ram, 10Gb disk Software needed: minimal install + vdsm and ovirt-host-deploy-offline build deps. Since we only have x86 hardware which run oVirt. Does it have to be a PPC64 VM because I don't think we can host that right now. AFAIK we can run qemu-system-ppc64 also on x86_64. Or am I missing something? Can we also do this with oVirt as host? Ideally I'd prefer not having to manually host a VM but have oVirt take care of it. Could a VDSM hook
On Tue, Feb 11, 2014 at 08:12:45AM +0100, Sandro Bonazzola wrote: possibly solve this if not built in? _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Il 12/02/2014 12:46, Aline Manera ha scritto:
On 02/12/2014 06:08 AM, Eyal Edri wrote:
Maybe aline can help here? as you can see we also need POWER pc slaves, so if you can contribute a server which we can run ppc vms on, it will be great both for kimchi and oVirt.
Hi all,
I am going through the legal stuffs to get POWER machines from IBM available to ovirt community. But in this first attempt, I am trying to get POWER vms and not a host POWER machine.
Sandro, Eyal: Do POWER vms work fine for your proposals? Or you need a host POWER machine?
For build purpose, VMs are enough thanks. I'm not sure about the testing for Francesco Romani, maybe he'll reply
Eyal.
----- Original Message -----
From: "Ewoud Kohl van Wijngaarden" <ewoud+ovirt@kohlvanwijngaarden.nl> To: infra@ovirt.org Sent: Wednesday, February 12, 2014 2:13:48 AM Subject: Re: Request for 3 PPC64 vm slaves for Jenkins
Il 10/02/2014 23:15, Ewoud Kohl van Wijngaarden ha scritto:
On Mon, Feb 10, 2014 at 08:12:35AM +0100, Sandro Bonazzola wrote:
PPC64 support is going to be introduced as new feature in oVirt 3.4.0. So we should start delivering PPC64 packages for arch dependent packages for both EL6 and Fedora. VMs may be small enough since they should only build nightly vdsm and ovirt-host-deploy-offline: 1 core, 512Mb ram, 10Gb disk Software needed: minimal install + vdsm and ovirt-host-deploy-offline build deps. Since we only have x86 hardware which run oVirt. Does it have to be a PPC64 VM because I don't think we can host that right now. AFAIK we can run qemu-system-ppc64 also on x86_64. Or am I missing something? Can we also do this with oVirt as host? Ideally I'd prefer not having to manually host a VM but have oVirt take care of it. Could a VDSM hook
On Tue, Feb 11, 2014 at 08:12:45AM +0100, Sandro Bonazzola wrote: possibly solve this if not built in? _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Aline Manera" <alinefm@linux.vnet.ibm.com>, "Eyal Edri" <eedri@redhat.com>, "Ewoud Kohl van Wijngaarden" <ewoud+ovirt@kohlvanwijngaarden.nl> Cc: infra@ovirt.org, "Francesco Romani" <fromani@redhat.com> Sent: Wednesday, February 12, 2014 1:05:50 PM Subject: Re: Request for 3 PPC64 vm slaves for Jenkins
Il 12/02/2014 12:46, Aline Manera ha scritto:
On 02/12/2014 06:08 AM, Eyal Edri wrote:
Maybe aline can help here? as you can see we also need POWER pc slaves, so if you can contribute a server which we can run ppc vms on, it will be great both for kimchi and oVirt.
Hi all,
I am going through the legal stuffs to get POWER machines from IBM available to ovirt community. But in this first attempt, I am trying to get POWER vms and not a host POWER machine.
Sandro, Eyal: Do POWER vms work fine for your proposals? Or you need a host POWER machine?
For build purpose, VMs are enough thanks. I'm not sure about the testing for Francesco Romani, maybe he'll reply
Hi, for me it's enough to have a qemu-system-ppc64 run, any way is fine. The reason I'm asking is just to exercise he PPC64 changes recently added on VDSM, and of course catch as early as possible differences between x86_64 and PPC64 hosts. An example to issue I'd like to prevent in the future: http://gerrit.ovirt.org/#/c/24332/ Thanks and best regards, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani
Il 12/02/2014 01:13, Ewoud Kohl van Wijngaarden ha scritto:
On Tue, Feb 11, 2014 at 08:12:45AM +0100, Sandro Bonazzola wrote:
Il 10/02/2014 23:15, Ewoud Kohl van Wijngaarden ha scritto:
On Mon, Feb 10, 2014 at 08:12:35AM +0100, Sandro Bonazzola wrote:
PPC64 support is going to be introduced as new feature in oVirt 3.4.0. So we should start delivering PPC64 packages for arch dependent packages for both EL6 and Fedora. VMs may be small enough since they should only build nightly vdsm and ovirt-host-deploy-offline: 1 core, 512Mb ram, 10Gb disk Software needed: minimal install + vdsm and ovirt-host-deploy-offline build deps.
Since we only have x86 hardware which run oVirt. Does it have to be a PPC64 VM because I don't think we can host that right now.
AFAIK we can run qemu-system-ppc64 also on x86_64. Or am I missing something?
Can we also do this with oVirt as host? Ideally I'd prefer not having to manually host a VM but have oVirt take care of it. Could a VDSM hook possibly solve this if not built in?
Never tested such configuration. CCing VDSM developers about this.
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
participants (5)
-
Aline Manera -
Ewoud Kohl van Wijngaarden -
Eyal Edri -
Francesco Romani -
Sandro Bonazzola