Re: meta-cloud layer

[Saul Wold <sgw@linux.intel.com>]

On 12/03/2012 07:20 AM, Prica, Mihai wrote:
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of David Nyström
> Sent: Saturday, December 01, 2012 10:44 PM
> To: Michael Halstead
> Cc: oe-core layer
> Subject: Re: [OE-core] meta-cloud layer
>
> On 12/01/2012 12:23 AM, Michael Halstead wrote:
>> On 11/30/2012 12:17 PM, Raymond Danks wrote:
>>> On 11/30/2012 11:03 AM, Michael Halstead wrote:
>>>> On 11/30/2012 09:26 AM, Bruce Ashfield wrote:
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Nov 30, 2012 at 12:15 PM, Saul Wold <sgw@linux.intel.com
>>>>> <mailto:sgw@linux.intel.com>> wrote:
>>>>>
>>>>>       On 11/30/2012 03:29 AM, David Nyström wrote:
>>>>>
>>>>>           On 11/29/2012 02:54 PM, Richard Purdie wrote:
>>>>>
>>>>>               On Thu, 2012-11-29 at 06:44 -0700, Raymond Danks wrote:
>>>>>
>>>>>                   Thanks for looping me in here David. The initial
>>>>>                   goal for the meta-xen
>>>>>                   layer was in fact to encompass Xen Cloud Platform.
>>>>>                    As such, the intent
>>>>>                   was to contain both hypervisor and user-space
>>>>>                   applications.  Indeed, the
>>>>>                   xen distribution itself includes xm/libxl;
>>>>>                   hypervisor abstraction would
>>>>>                   be somewhat tedious in my opinion.
>>>>>
>>>>>                   The layer just received commits for expanding the
>>>>>                   libvirt build to
>>>>>                   support qemu.  The commonalities and shared packaged
>>>>>                   between xen, qemu,
>>>>>                   and kvm implementations are such that I would also
>>>>>                   agree that meta-xen
>>>>>                   should be expanded/renamed to encompass all
>>>>>                   virtualization types; I also
>>>>>                   support the move to meta-virtualization.
>>>>>
>>>>>
>>>>>           meta-virtualization sounds good, let co-op on this so we
>>>>>           don't duplicate
>>>>>           work.
>>>>>
>>>>>       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.
>>>>>
>>>>>
>>>>> This works for me. If Michael already has our keys, do we need to
>>>>> resend or can a local copy happen ?
>>>> I already have keys for,
>>>>
>>>> David Nystrom df:2d:b1:59:f3:d7:73:fc:59:36:7b:cf:85:28:a7:50
>>>> Bruce Ashfield  4f:93:90:b2:c7:a1:45:21:f2:47:31:6f:60:f9:60:02
>>>>
>>>> Either of you can currently add
>>>> git@git.yoctoproject.org:meta-virtualization 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.
>>>>
>>>> I require an ssh public key for Raymond Danks.
>>> 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.
>>>>
>>>>
>>>> We also need a short description for the listing on
>>>> git.yoctoproject.org. I could be something similar to, but better
>>>> than, "Layer enabling virtualization support. "
>>> How about "Layer enabling hypervisor, virtualization tool stack, and
>>> cloud support."
>>>
>> Sounds good to me. Thank you.
>>> 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?
>>>
>> I can add a private list for meta-virtualization@yoctoproject.org. Who
>> shall I add to membership?
>>
>>
>> I would like to be added, since it seems I can't add myself at
>> https://lists.yoctoproject.org/listinfo
>>
>> Best Regards,
>> David
>
> I would like to be added as well to the private list.
>
Just to be clear to all this is not a private list, there was some issue 
I think with getting it initialized, it is visiable and available to all 
from the https://lists.yoctoproject.org/listinfo URL, and it is getting 
added to the main list of Mailing lists today.

Sorry for any confusion.

Sau!


> Thanks,
> Mihai
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>