All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <meta-virtualization@yoctoproject.org>, <yocto@yoctoproject.org>
Subject: [Announce]: meta-cloud-services and OpenStack integration
Date: Fri, 4 Oct 2013 17:02:22 -0400	[thread overview]
Message-ID: <524F2CDE.1010805@windriver.com> (raw)

Hi all,

I'd like to share some work that we've been doing at Wind River around
cloud and clustering, in particular, bringing the OpenStack Grizzly
release [https://wiki.openstack.org/wiki/ReleaseNotes/Grizzly] to the
OpenEmbedded and Yocto Project ecosystem.

All of the major OpenStack Grizzly components (and their dependencies)
are part of this integration:

   - OpenStack Networking (Quantum)
   - OpenStack Object Storage (Swift)
   - OpenStack Block Storage (Cinder)
   - OpenStack Identity (Keystone)
   - OpenStack Image Service (Glance)
   - OpenStack Dashboard (Horizon)

The following layers have been populated on git.yoctoproject.org:

   git://git.yoctoproject.org/meta-cloud-services
    |
    +- meta-openstack
    +- meta-openstack-compute-deploy
    +- meta-openstack-controller-deploy
    +- meta-openstack-qemu

The READMEs in the various layers have details on the build,
configuration and launch of the reference use case. Improvements
to the documentation are welcome, since assumptions inevitably sneak
in when you least expect it.

The reference use case mentioned above is:

   - Separate control and compute node targets
   - Ability to schedule and launch a guest on the compute node

If you have a powerful enough machine, this reference use case can
be run completely on a single host from within VMs.

Consider this a baseline that pulls together the great work being done
in oe-core, meta-oe, meta-realtime and the Yocto Project. What I've
shared works, but like everything, it needs more eyes, fixes and lots
of collaboration.

Since this is closely related to virtualization, discussions and
patch sharing will take place on meta-virtualization@yoctoproject.org.

We are all looking forward to collaborating and enhancing the
capabilities of Embedded Cloud computing through the broad range of
new platforms and applications available via the Yocto Project.

Upstream OpenStack minor releases, and major releases will be tracked
with the layers, including when the imminent OpenStack Havana release
is stabilized, the recipes will be updated and made available.

 From the Yocto Project point of view, the layers will also be branched
and tagged in coordination with its normal release milestones.

Enjoy.
Bruce

p.s. There are a few recipe updates and patches that are being carried
in this layer to keep things simple, they'll be sent out to their
appropriate homes as soon as possible.


                 reply	other threads:[~2013-10-04 21:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=524F2CDE.1010805@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=meta-virtualization@yoctoproject.org \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.