Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "David Nyström" <david.nystrom@enea.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches,
	discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: meta-cloud layer
Date: Thu, 29 Nov 2012 09:41:56 +0100	[thread overview]
Message-ID: <50B71FD4.3090304@enea.com> (raw)
In-Reply-To: <CADkTA4P8=aLSXNTAENp+WW7xX+ttYAPhPufRE=+yn9KXOY8Sag@mail.gmail.com>

Adding Ray Danks to CC.

Ray, how do you want to go forward with the meta-xen layer ?

 From my perspective, having the actual hypervisor technology abstracted
from the userspace virtualization stuff is preferable. So a user could 
pick-and-place hypervisor layer/s depending on needs. (And good for 
use-case benchmarks as well).

libvirt package and others are smart enough to autodetect underlying 
hypervisor tech capabilities, and should work out-of-the-box from that 
aspect.

As to where all this will finally end up, anything goes as far as I'm 
concerned. I'll continue working in meta-cloud for now, until consensus 
is reached on the final whereabouts for the virtualization specific recipes.

If anyone want to join me on github, send me an email.

Best Regards,
David


On 11/28/2012 06:25 PM, Bruce Ashfield wrote:
> On Wed, Nov 28, 2012 at 11:22 AM, Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
>
>> On Wed, 2012-11-28 at 17:10 +0100, David Nyström wrote:
>>> Hello everyone,
>>>
>>> I'm working on getting a minimal Yocto/oe-core based OpenStack setup
>>> running with the meta-cloud layer, with bits and pieces "borrowed" from
>>> the meta-xen layer.
>>
>> Great news!
>>
>> It might be worth growing meta-xen into a meta-virtualisation layer
>> since kvm, openstack and xen all seem to be sharing a lot of pieces.
>> This depends on the maintainers but it would seem to be logical rather
>> than many small interdependent layers.
>>
>
> FWIW. I'd like to see this as well, and can contribute/help where possible.
> I
> was considering a meta-ovs (Open Virtualization Solutions), but if there are
> already plans afoot for a meta-virtualization, then anything I did could be
> pushed down keeping any other layers small.
>
> In particular I'm keen to drive some common kernel configuration, and work
> on consolidating kernel features in trees versus having a whole set of out
> of
> tree modules with better tie in's to userspace enabling features
> dynamically.
>
> So I'll keep an eye out for things as well and help where possible.
>
> Cheers,
>
> Bruce
>
>
>>
>>> Still in its infancy, and lots of stuff is still missing and/or not
>>> working properly.
>>>
>>> Have a look if your interested, not much to see yet though.
>>>
>>> https://github.com/nysan/meta-cloud.git
>>>
>>> Any thoughts on floating layer ML:s, i.e. an ML for so called
>>> "out-of-tree" layers ?  Or is the common thought that all new recipes
>>> should eventually go into oe-core ?
>>
>> The Yocto Project has been using the Yocto list for that and
>> OpenEmbedded has openembedded-devel. Its not expected for everything to
>> end up in OE-Core, quite the opposite.
>>
>> Cheers,
>>
>> Richard
>>
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>
>
>



  reply	other threads:[~2012-11-29  8:56 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 [this message]
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
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=50B71FD4.3090304@enea.com \
    --to=david.nystrom@enea.com \
    --cc=bruce.ashfield@gmail.com \
    --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