<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 30, 2012 at 12:14 PM, Raymond Danks <span dir="ltr"><<a href="mailto:ray.danks@se-eng.com" target="_blank">ray.danks@se-eng.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 11/30/2012 04:29 AM, David Nyström wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 11/29/2012 02:54 PM, Richard Purdie wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Thu, 2012-11-29 at 06:44 -0700, Raymond Danks wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks for looping me in here David. The initial goal for the meta-xen<br>
layer was in fact to encompass Xen Cloud Platform. As such, the intent<br>
was to contain both hypervisor and user-space applications. Indeed, the<br>
xen distribution itself includes xm/libxl; hypervisor abstraction would<br>
be somewhat tedious in my opinion.<br>
<br>
The layer just received commits for expanding the libvirt build to<br>
support qemu. The commonalities and shared packaged between xen, qemu,<br>
and kvm implementations are such that I would also agree that meta-xen<br>
should be expanded/renamed to encompass all virtualization types; I also<br>
support the move to meta-virtualization.<br>
<br>
</blockquote></blockquote>
<br>
meta-virtualization sounds good, let co-op on this so we don't duplicate work.<br>
</blockquote></div>
Yes. Agreed.<div><div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
As far as a meta-cloud layer is concerned, I'm not sure I am<br>
knowledgeable enough in this area to weigh in. I'm currently<br>
researching a filesystem implementation for OpenStack and have stumbled<br>
across Ceph/RBD and Gluster modules that look promising. On top of this,<br>
XCP is documented to include support for VastSky and can be integrated<br>
with DRBD. And, the storage and hypervisor are only two pieces of the<br>
puzzle for a cloud implementation!<br>
<br>
</blockquote></blockquote>
<br>
Cool !<br>
I know, the meta-"cloud" name is quite/too ambitious, it was not meant to be a one week effort. But why aim low :).<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think I would encourage you to also include OpenStack in a<br>
meta-virtualization layer until it has matured to the point where<br>
abstraction is more warranted.<br>
</blockquote></blockquote>
<br>
Agree.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Since you've already created a presence<br>
at github, would it be possible to rename your layer to<br>
meta-virtualization and absorb the entire meta-xen layer? I can push<br>
any changes for Xen/XCP here, it sounds like it is a central place for<br>
libvirt and could also contain Bruce's kernel modifications.<br>
<br>
Alternatively, I can create a meta-virtualization project. In any case,<br>
those on the To and CC list should receive access to this layer as a<br>
starting point.<br>
<br>
Just my two cents. :)<br>
</blockquote>
<br>
I'd like to offer to host this combined layer (whatever we decide to<br>
call it) on <a href="http://git.yoctoproject.org" target="_blank">git.yoctoproject.org</a> if that would help people and people<br>
are interested. My only concern is in the area of maintainership, we<br>
need to clearly define who maintains what and what the patch submission<br>
process is in the README.<br>
<br>
</blockquote>
<br>
Thanks,<br>
<br>
Sounds good to centralize everything, since Raymond is the majority code contributor, perhaps he, if willing, can maintain the meta-virtualization layer.<br>
If you want a co/sub-maintainer I'll be happy to help out.<br>
<br>
</blockquote></div></div>
Yes. Thanks Richard. I was looking at some of the Yocto projects and the meta-ti stood out as one that might be a model for this. Would it be possible to configure a mailing list for meta-virtualization as well? Once you've got the repo in place I'll push up what's in meta-xen. Maybe David can come behind with what's in meta-cloud. I also saw that Mihai mentioned having a KVM tree that might integrate. Once we've got this setup we should also rename the link on the OE layers index wiki.<br>
<br>
I'm happy with a co-maintainer type setup as well. In fact, I prefer that. I've done work with the xen part of this, but kvm and openstack are still somewhat foreign.<br></blockquote><div><br></div><div>And I've got some cross platform experience with all three, plus kernel parts, so</div>
<div>as required, I'm still offering up my help if no one objects.</div><div><br></div><div>I'll send along my keys once a layer and home have been chosen.</div><div><br></div><div>Cheers,</div><div><br></div><div>
Bruce</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
At any rate, I'll pay closer attention to the lists as they pertain to this layer especially going forward. I think this will work well to combine our efforts here.<br>
<br>
Ray<div class="HOEnZb"><div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Cheers,<br>
<br>
Richard<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.<u></u>openembedded.org</a><br>
<a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core" target="_blank">http://lists.linuxtogo.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openembedded-core</a><br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"<br>
</div>