<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 30, 2012 at 6:23 PM, Michael Halstead <span dir="ltr"><<a href="mailto:michael@yoctoproject.org" target="_blank">michael@yoctoproject.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><div><div class="h5">
<div>On 11/30/2012 12:17 PM, Raymond Danks
wrote:<br>
</div>
<blockquote type="cite">
<div>On 11/30/2012 11:03 AM, Michael
Halstead wrote:<br>
</div>
<blockquote type="cite">
<div>On 11/30/2012 09:26 AM, Bruce
Ashfield wrote:<br>
</div>
<blockquote type="cite"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Fri, Nov 30, 2012 at 12:15 PM,
Saul Wold <span dir="ltr"><<a href="mailto:sgw@linux.intel.com" target="_blank">sgw@linux.intel.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On 11/30/2012 03: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<br>
work.<br>
<br>
</blockquote>
</div>
If everyone is OK with this, I will have Michael
Halstead create a repo, please send him your keys so
that you will have write access to it.<br>
</blockquote>
<div><br>
</div>
<div>This works for me. If Michael already has our keys,
do we need to resend or can</div>
<div>a local copy happen ?</div>
</div>
</div>
</blockquote>
I already have keys for,<br>
<br>
David Nystrom df:2d:b1:59:f3:d7:73:fc:59:36:7b:cf:85:28:a7:50<br>
Bruce Ashfield 4f:93:90:b2:c7:a1:45:21:f2:47:31:6f:60:f9:60:02<br>
<br>
Either of you can currently add <a href="mailto:git@git.yoctoproject.org:meta-virtualization" target="_blank">git@git.yoctoproject.org:meta-virtualization</a>
as a git remote and start the repository. Once we have initial
code and the maintainers and patch submission guidelines in the
readme I can publicly list the new repository.<br>
<br>
I require an ssh public key for Raymond Danks.<br>
</blockquote>
Thanks Michael. I got your response and was able to push meta-xen
to the newly created repository on meta-virtualization. I added
one commit to tweak the README and conf/layer.conf for the new
name.<br>
<blockquote type="cite"> <br>
<br>
We also need a short description for the listing on
<a href="http://git.yoctoproject.org" target="_blank">git.yoctoproject.org</a>. I could be something similar to, but
better than, "Layer enabling virtualization support. "<br>
</blockquote>
How about "Layer enabling hypervisor, virtualization tool stack,
and cloud support."<br>
<br>
</blockquote></div></div>
Sounds good to me. Thank you.<div class="im"><br>
<blockquote type="cite"> Also
- I referenced the mail alias meta-virtualization at yoctoproject
in the README. When you publish this, can we use something like
that as well?<br>
<br>
</blockquote></div>
I can add a private list for <a href="mailto:meta-virtualization@yoctoproject.org" target="_blank">meta-virtualization@yoctoproject.org</a>.
Who shall I add to membership?<div><div class="h5"><br></div></div></div></blockquote><div><br></div><div><br></div><div>At the risk of stating the obvious, I like the idea of a separate list, and would like to be</div>
<div>added. But then again, i can always add myself later as well (assuming the same</div><div>interface as the rest of the lists).</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">
<div text="#000000" bgcolor="#FFFFFF"><div><div class="h5">
<br>
<br>
<pre cols="72">--
Michael Halstead
Yocto Project / Sys Admin</pre>
<br>
<br>
<blockquote type="cite">
Thanks again,<br>
Ray<br>
<blockquote type="cite"> <br>
<pre cols="72">--
Michael Halstead
Yocto Project / Sys Admin</pre>
<br>
<blockquote type="cite">
<div class="gmail_extra">
<div class="gmail_quote">
<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>
Sau!
<div>
<div><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">
<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<br>
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<br>
contributor, perhaps he, if willing, can maintain
the<br>
meta-virtualization layer.<br>
If you want a co/sub-maintainer I'll be happy to
help out.<br>
<br>
<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>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core" target="_blank">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core</a><br>
<br>
</blockquote>
<br>
<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core" target="_blank">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core</a><br>
<br>
<br>
</blockquote>
<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core" target="_blank">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core</a><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>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
<br>
</div></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>