<div dir="ltr"><div><div>Ooh, this is like music to my ears.<br><br></div>If the oVirt-project needs some POWER-hardware as Jenkinsslaves, buildhosts etc, I can surely arrange that.<br><br></div>/Alexander Rydekull<br></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 21, 2013 at 5:33 PM, Leonardo Bianconi <span dir="ltr"><<a href="mailto:leonardo.bianconi@eldorado.org.br" target="_blank">leonardo.bianconi@eldorado.org.br</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
We are planning to deliver support for PPC64 in 4 phases. We will manage to deliver a set of patches at the end of each phase.<br>
<br>
Phase 1<br>
<br>
Change oVirt to handle other architectures by encapsulating all the architecture specific code and queries about the capabilities of the hypervisor into a new class called ArchStrategy (based on the Strategy Design Pattern). Every operation involving clusters and hosts will be validated by this new class. Some hard-coded parameters are going to be replaced by queries in the backend in order to accommodate the support for new architectures into the engine.<br>
<br>
<br>
Phase 2<br>
<br>
Currently, each host hypervisor capabilities are obtained using hard-coded data structures. These structures will be replaced either by some form of integration with libosinfo or by reading internal configuration files describing these capabilities. It will be handled after Roy's patch.<br>
<br>
<br>
Phase 3<br>
<br>
The code for providing the support for IBM POWER systems will be added. The encapsulation done in the previous phase will reduce the effort to include this feature into the engine. The other changes that will be introduced in this phase include:<br>
<br>
- Modifications in the frontend to avoid running a VM created on a POWER host in a x86-64 host (and vice-versa),<br>
- All the dynamically provided capacities of the first phase will be implemented according to the capacities of the QEMU/KVM on POWER<br>
- The POWER processors will be available as an option in the list of processor names (this will imply in significant changes in the backend)<br>
<br>
<br>
Phase 4<br>
<br>
Adapt secondary features to polish the support for POWER:<br>
<br>
- OVF import and export of VMs running in POWER hosts<br>
- Dynamic searches capable of finding hosts, pools, vms and clusters according to their architectures<br>
<br>
<br>
Is there any ongoing oVirt architecture refactoring ? (that may conflict with Phase 1, for instance)<br>
<br>
Any comments ?<br>
<br>
Regards,<br>
Vitor (<a href="mailto:vitor.lima@eldorado.org.br">vitor.lima@eldorado.org.br</a>) / Leonardo (<a href="mailto:leonardo.bianconi@eldorado.org.br">leonardo.bianconi@eldorado.org.br</a>)<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
-----Original Message-----<br>
From: Dave Neary [mailto:<a href="mailto:dneary@redhat.com">dneary@redhat.com</a>]<br>
Sent: quarta-feira, 15 de maio de 2013 12:25<br>
To: Leonardo Bianconi<br>
Cc: <a href="mailto:arch@ovirt.org">arch@ovirt.org</a>; Adam Litke<br>
Subject: Re: oVirt on IBM POWER (PPC64) - new feature contributors<br>
<br>
Hi,<br>
<br>
On 05/14/2013 08:05 PM, Leonardo Bianconi wrote:<br>
> We would like to introduce ourselves: Leonardo Bianconi and Vitor Lima.<br>
<br>
Welcome!<br>
<br>
> We would like to work on the features "Engine support for PPC64" (<a href="http://wiki.ovirt.org/Features/Engine_support_for_PPC64" target="_blank">http://wiki.ovirt.org/Features/Engine_support_for_PPC64</a>) and the "Vdsm for PPC64" (<a href="http://wiki.ovirt.org/Features/Vdsm_for_PPC64" target="_blank">http://wiki.ovirt.org/Features/Vdsm_for_PPC64</a>). This work has already been started by some developers at IBM.<br>
<br>
<snip><br>
<br>
> About libosinfo:<br>
> =============<br>
><br>
> In the previous discussion about this topic (<a href="http://lists.ovirt.org/pipermail/arch/2012-November/000976.html" target="_blank">http://lists.ovirt.org/pipermail/arch/2012-November/000976.html</a>), occurred in November 2012, it was suggested that integrating the libosinfo into the engine would be a better way to handle the differences between the architectures that would be supported in the future.<br>
><br>
> Is this approach still valid? If so, when will it be available? It seems to be a dependency for oVirt "Engine_support_for_PPC64" feature implementation.<br>
<br>
<br>
This is great news. I don't know who, specifically, has been working on this issue in IBM - perhaps Adam Litke (CCed) can update you on the progress that has been made.<br>
<br>
Cheers,<br>
Dave.<br>
<br>
--<br>
Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - <a href="http://community.redhat.com" target="_blank">http://community.redhat.com</a><br>
Ph: <a href="tel:%2B33%209%2050%2071%2055%2062" value="+33950715562">+33 9 50 71 55 62</a> / Cell: <a href="tel:%2B33%206%2077%2001%2092%2013" value="+33677019213">+33 6 77 01 92 13</a><br>
_______________________________________________<br>
Arch mailing list<br>
<a href="mailto:Arch@ovirt.org">Arch@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/arch" target="_blank">http://lists.ovirt.org/mailman/listinfo/arch</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>/Alexander Rydekull
</div>