Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "David Nyström" <david.c.nystrom@gmail.com>
To: Michael Halstead <michael@yoctoproject.org>
Cc: oe-core layer <openembedded-core@lists.openembedded.org>
Subject: Re: meta-cloud layer
Date: Sat, 01 Dec 2012 21:43:48 +0100	[thread overview]
Message-ID: <50BA6C04.9040900@gmail.com> (raw)
In-Reply-To: <50B93FFB.9050505@yoctoproject.org>

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





  parent reply	other threads:[~2012-12-01 20:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28 16:10 meta-cloud layer David Nyström
2012-11-28 16:22 ` Richard Purdie
2012-11-28 17:25   ` Bruce Ashfield
2012-11-29  8:41     ` David Nyström
2012-11-29 10:05       ` Prica, Mihai
2012-11-29 13:44       ` Raymond Danks
2012-11-29 13:54         ` Richard Purdie
2012-11-30 11:29           ` David Nyström
2012-11-30 17:14             ` Raymond Danks
2012-11-30 17:25               ` Bruce Ashfield
2012-11-30 17:15             ` Saul Wold
2012-11-30 17:26               ` Bruce Ashfield
2012-11-30 18:03                 ` Michael Halstead
2012-11-30 20:17                   ` Raymond Danks
2012-11-30 23:23                     ` Michael Halstead
2012-12-01 17:30                       ` Bruce Ashfield
2012-12-01 17:41                         ` Philip Balister
2012-12-01 20:43                       ` David Nyström [this message]
2012-12-03 15:20                         ` Prica, Mihai
2012-12-03 16:00                           ` Saul Wold
2012-12-03 16:04                             ` Michael Halstead
2012-12-03 16:27                               ` Raymond Danks

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50BA6C04.9040900@gmail.com \
    --to=david.c.nystrom@gmail.com \
    --cc=michael@yoctoproject.org \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox