OpenStack status
by Pádraig Brady
Hi,
Here is the latest Fedora OpenStack status report:
https://fedoraproject.org/wiki/OpenStack_status_report_2012-09-28
Historical archives are here:
http://fedoraproject.org/wiki/OpenStack_status_reports
Cheers,
Pádraig.
(appended below for convenience)
= Distro News =
== Folsom Fedora 18 test days ==
Coinciding with the Folsom and Fedora 18 releases, we ran two
[https://fedoraproject.org/wiki/Test_Day:2012-09-18_OpenStack Fedora Folsom test days]
on Sep 18th and 25th aligned around the Folsom-3 and Folsom-rc1 releases respectively.
Cinder and Heat are new components compared to the last test day,
and new tests have been included for quantum and swift.
This is a good place to start to get a quick hands on overview of OpenStack.
== OpenStack Installer ==
Derek Higgins has been working on an [https://github.com/derekhiggins/os-installer OpenStack installer],
that supports distributed and scripted installs.
== OpenStack side Repositories ==
To augment the [https://apps.fedoraproject.org/packages/s/openstack official Fedora OpenStack packages],
we've made an [http://repos.fedorapeople.org/repos/openstack/ OpenStack side repository] available giving
more flexibility with which OpenStack version is installed on a particular distribution.
Included there for example are the trunk chasing RPMs from the [http://smokestack.openstack.org/about smokestack] project.
== Fedora OpenStack patch management ==
With such a vibrant project as OpenStack, efficient patch management is imperative.
The Fedora OpenStack packages largely automate the patch management process through git,
and this process is now documented at the [http://fedora-openstack.github.com/ landing page for fedora-openstack] which is
the github organisation used to share these patch management trees.
= Project News =
== Folsom Released ==
Foslom was released on Sep 27th.
Mark McLoughlin prepared [https://lists.launchpad.net/openstack/msg17006.html stats on who contributed]
where you can drill down to details on review and bug handling stats too.
Also referenced there is the pretty [http://bitergia.com/public/previews/2012_09_pre-folsom_openstack/ bitergia analysis of Folsom commits]
where Red Hat features prominently.
== OpenStack Foundation ==
The [http://www.openstack.org/foundation/ OpenStack Foundation] was launched on 19-09-2012
and there were a few associated elections.
* [https://lists.launchpad.net/openstack/msg16722.html Project Technical Leads for Grizzly]
* [http://lists.openstack.org/pipermail/openstack-announce/2012-September/00... Technical committee elected members]
* [http://lists.openstack.org/pipermail/foundation/2012-August/001066.html Individual Board Members]
* [http://lists.openstack.org/pipermail/foundation/2012-August/001065.html Gold Board Members]
== OpenStack Summit ==
The main [http://openstacksummitfall2012.sched.org/ OpenStack conference and OpenStack design summit] are coincident.
Summarised below are presentations and proposals from Red Hat employees.
=== Main conference presentations ===
* Mark McLoughlin and Thierry Carez - [http://openstacksummitfall2012.sched.org/event/b616388023e820ced9c09dc384... From tactical to strategic contributions]
* Steven Dake - [http://openstacksummitfall2012.sched.org/event/f5101a8e719a56fcd895f6461b... Heat: A template based orchestration engine for OpenStack]
* Perry Myers - [http://openstacksummitfall2012.sched.org/event/23f5f2f25702e93bff3ccf9613... OpenStack Distributions: How they will shape the future of OpenStack innovation]
=== Design summit proposals ===
* Mark McLoughlin
** Stable branch status and plans
** Oslo status and plans
** nova - making sense of the config options
** Review of python dependencies
* Dan Prince
** Make PostgreSQL a first class citizen
** SmokeStack as a multi-distro test system
* Steven Dake
** heat - Orchestration API - Technical discussion of openstack-specific orchestration API
** heat - Roadmap discussion - Short (5 mins) description of current unsolved roadmap items with open brainstorm design session about future roadmap items in 2013
* Angus Salkeld
** Cloudwatch for OpenStack - Describe CloudWatch and how to make it a reality for OpenStack
* Russell Bryant
** nova - bug handling status and plans
** nova - remove direct database access from compute nodes
* Adam Young
** keystone - PKI status and plans
** keystone - LDAP and Active Directory integration
* Robert Kukura
** quantum - Modular L2 Plugin and Agent
* Gary Kotton
** quantum - rosetta-plugin
== Red Hat contributions ==
Alan Pevec and Mark McLoughlin worked on [https://review.openstack.org/#/c/10579/ improvements to paste config],
supporting less coupled config, which was added to Nova, Glance and Cinder.
Russell Bryant completed the [https://blueprints.launchpad.net/nova/+spec/no-db-messaging no-db-messaging] work in Nova.
Angus Salkeld has worked on merging a bunch of core service infrastructure
into openstack-common.
Adam Young has been working on PKI token revocation support.
There is too much to track in detail the OpenStack upstream activity of Red Hat developers,
but here is a link showing the [http://goo.gl/aewXr latest Red Hat OpenStack upstream development]
== Stable Branch ==
New members from Red Hat, Debian and Suse were added to the [https://launchpad.net/~openstack-stable-maint OpenStack stable maintenance team],
responsible for the stable branches.
= Community engagement =
== OpenStack community meetup, London ==
The [http://www.meetup.com/Openstack-London/events/77153502/ 2nd London OpenStack meeting]
took place on Thurs 27th Sept in the same central London location as before.
= Related projects =
== heat API ==
The Heat project [http://lists.heat-api.org/pipermail/discuss/2012-September/000195.html released V6].
10 years, 11 months
Thing 1: what do we mean when we say cloud?
by Matthew Miller
There was some great discussion on this when the list was first launched,
but at the time, I don't think the answer was clear, and the group went on
with the practical tasks of actually making things work. That's a decent,
functional response, but as we embark on a bigger strategic plan, we need a
more clear definition of our scope. (Then we can start talking about desired
outcomes within that scope, various stakeholders, and so on.)
The embryonic Fedora Cloud Guide¹ says
Pardon the pun, but "the cloud" is a nebulous term. When well-meaning
people talk about cloud computing, they are often talking about one of
many difference scenarios.
I've put a little jar by my desk, and I'm putting quarters into it every
time I say "nebulous", or "hazy", or anything like that. Clearly, "Cloud" is
a marketing term *and* a business buzzword, neither of which lend themselves
to clarity. But it's also a *very real* change in the computing landscape,
and Fedora should take a leadership position in that transition and in the
new tech world. Using a clear framework for our scope will help us through
the fog. (*Plink* — there goes 25¢)
Our Cloud Guide goes on to list Infrastructure as a Service, Platform as a
Service, and Software as a Service. That's an important lens, but it's also
jumping ahead a bit. The National Institute of Standards and Technology
recently published an official definition², and while "government-committee
definition" may light up some alarms, this is actually straightforward and
fuctional. Once you get past the preamble, there's really only two pages to
it.
I like this definition because while it's still broad, it focuses on
essential characteristics which distinguish cloud computing from datacenter
virtualization in general and from "it's on the Internet!"
If I haven't lost you already, I encourage you to read the definition.
Really, it's short. But if you're hanging on by an attention-span thread,
the essentials are:
- On demand self-service.
- Broad network access.
- Resource pooling.
- Rapid elasticity.
- Measured service.
And then it goes on with service models (SaaS, PaaS, IaaS) and deployment
models (private, community, public, hybrid).
I suggest that Fedora adopt this as our definition, and as the basis for the
scope of this SIG. I think this is uncontroversial, but I would like to hear
your feedback.
Of particular note, work here so far has focused on two primary areas:
"JEOS" images³ for Amazon EC2 (and elsewhere), and on software stacks for
deploying cloud infrastructure (Eucalyptus, OpenStack) as a cloud provider.
This has been great so far, but I also want to open up the SIG to some
broader areas as well — those use areas and constituent groups being the
topic of future discussion.
----
1. http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html-s...
2. http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf
3. That's "Just Enough Operating System", if you haven't heard the term.
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>
10 years, 11 months
rescheduling the cloud sig meeting
by Matthew Miller
Robyn mentioned to me that the cloud sig meeting isn't at a very convenient
time for many people. I'm not a big fan of Friday afternoon meetings,
myself, and for the EU people giving up Friday night can't be the most
pleasant.
Since I'm going to be relieving Robyn of the illustrious duty of
facilitating the meeting, I thought this'd be a good time to figure out
a time that might work better.
I threw up <http://whenisgood.net/fedoracloudmeeting> to help figure out a
good time -- if you could take a few seconds to go there and send the times
that generally work for you, hopefully we can figure out something better.
Thanks!
--
Matthew Miller _☁_ Fedora Cloud Architect _☁_ <mattdm(a)fedoraproject.org>
10 years, 11 months
official meeting time change: 14:00 UTC Wednesday
by Matthew Miller
Okay, 14:00 UTC Wednesday works best. Let's move the meeting to then, with a
standing semi-official meeting Tuesday at 20:00 UTC. I'll also try to be in
the IRC channel, well, a lot, but particularly Wednesday at 20:00 UTC.
And of course if we can conduct business on this list that's great too.
(These are 10am Wednesday EDT and 4pm EDT, and 7am/1pm PDT.)
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>
10 years, 12 months
Cloud SIG meeting at 1900 UTC (3pm eastern, noon pacific)
by Matthew Miller
Okay, so we'll do the meeting at the regular time, for everyone who can
make it.
When: 1900 UTC (3pm US Eastern, 12pm US Pacific)
Where: #fedora-meeting on irc.freenode.net
Agenda:
* Matthew learns to run meetbot
* Hello from me and any other new people
* F18 feature-owner statuses
* Strategic plans
* Any other topic you want to talk about.
11 years
Re: tool for image building and update
by Steve Loranz
Just a quick note on the difference between ImageFactory and Oz.
Oz creates a KVM image, does a Just Enough OS (JEOS) install of the operating system, and provides a means to adding additional packages to and/or running customization scripts on the OS installed in this image.
ImageFactory creates a base image and then performs the necessary transformations on the image file itself to allow it to be used on any number of clouds (RHEV-M, vSphere, EC2, etc). ImageFactory can then push this image up to a cloud provider/region so that it can be used for instances.
ImageFactory uses Oz to create the base image before transforming that image for use on various clouds. In version 2 of ImageFactory, we introduce a plugin API that allows one to add plugins for new operating systems and/or new cloud types. The Fedora/RHEL plugin we include with ImageFactory uses Oz to create base images for those operating systems, but one could just as easily replace that plugin with one that uses some other library/tool.
If what you are looking for is creating images that will work on multiple clouds, please have a look at ImageFactory. It offers a CLI and REST api. v2 will be officially released soon. https://github.com/aeolusproject/imagefactory
If you just want to create images for use with KVM, Oz is solid. https://github.com/clalancette/oz
-steve
On Sep 20, 2012, at 12:13 PM, cloud-request(a)lists.fedoraproject.org wrote:
> Message: 2
> Date: Thu, 20 Sep 2012 14:24:36 +0000
> From: Tomas Karasek <tomas.karasek(a)cern.ch>
> To: "cloud(a)lists.fedoraproject.org" <cloud(a)lists.fedoraproject.org>
> Subject: tool for image building and update
> Message-ID:
> <E77A1A8746A0D749B5BA8052CAFF5A83228EE045(a)CERNXCHG12.cern.ch>
> Keywords: CERN SpamKiller Note: -50
> Content-Type: text/plain; charset="us-ascii"
>
> Hello,
>
> I am looking at possibilities of automation of disk image creation (installation) and update.
>
> I ran across tools from Aeolus:
> imagefactory - http://www.aeolusproject.org/imagefactory.html
> and Oz - http://www.aeolusproject.org/oz.html
>
> I noticed Oz is used in Heat too.
> Is there some other tool I could look at?
>
> Thanks,
> Tomas
11 years
Fwd: Re: Aeolus upstream community-building
by Mo Morsi
Forwarding to the cloud sig, all are welcome to attend
Among other things I will be discussing are the image templates that we
are building to be able to be deployed to many different cloud providers
for various setups including mock other fedora infrastructure components.
-Mo
-------- Original Message --------
Subject: Re: Aeolus upstream community-building
Date: Thu, 20 Sep 2012 13:06:49 -0400
From: Mo Morsi <mmorsi(a)redhat.com>
On 09/13/2012 01:41 PM, Matthew Wagner wrote:
>
>
> The following is a new meeting request:
>
> Subject: Aeolus upstream community-building
> Organizer: "Matthew Wagner" <mawagner(a)redhat.com>
>
> Location: Google Plus Hangout!
> Time: Thursday, September 20, 2012, 2:00:00 PM - 2:30:00 PM GMT
> -05:00 US/Canada Eastern
>
>
>
>
> *~*~*~*~*~*~*~*~*~*
>
> Hi folks,
>
> This is an invite to the next meeting to talk about building the
> Aeolus community and outreach efforts.
>
> We held this on Google Hangout last time, which worked well. You will
> need a Google Plus account to attend, and a working microphone (and
> speakers or a headset). It's a video chat (though it will work without
> video if you don't have a camera), so do wear a shirt. You might want
> to try a Google Hangout ahead of time to see if things work; their
> client can be persnickety.
>
> Notes from our last meeting are here:
> http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-September/01251...
>
> Hopefully this time we can talk a bit about how to go about
> implementing some of these things!
>
> -- Matt
Hey all just a reminder, we are planning on meeting on google hangout
today @2.
https://plus.google.com/hangouts/_/c40c41f367049d43b8d14628e5f985133251a1...
The hangout can only support 9 participants so unless you're planning on
contributing, please refrain from joining the hangout. You can just
follow along via the live youtube broadcast here:
http://www.youtube.com/watch?v=2LC58nFzYAc&feature=plcp
I plan on doing a quick overview of my Ohio LinuxFest presentation at
this meeting in addition to discussing the agenda topics.
-Mo
11 years
Hello, Cloud SIG!
by Matthew Miller
Hi everyone. I just posted a message about Fedora cloud (and about me) on
the devel list, which I hope you'll find interesting. In short, Red Hat is
making it possible for me to devote myself full time to making this awesome.
I've posted here sporadically in the midst of my busy day job, but hadn't
had the time to participate as much as I'd have liked. That's changed now,
as this *is* my busy day job.
There's three main parts to my role here:
* Assembling a strategic plan and helping to make it happen
* Working on stuff that needs a hand (including making sure that
everything we need to be doing gets the required resources)
* Communicating the excellent work that's going on to the world
and there's going to be a lot from me on all of those things coming to this
very SIG really soon, but for now I just wanted to say hi.
(Also, I will be hanging out regularly on IRC once I get myself settled in
to the new flow.)
--
Matthew Miller _☁_ Fedora Cloud Architect _☁_ <mattdm(a)fedoraproject.org>
11 years
