On Thu, 2011-09-01 at 09:54 -0700, Robyn Bergeron wrote:
On 09/01/2011 07:58 AM, Mark McLoughlin wrote:
> Robyn suggested that, given the recent progress, we should put OpenStack
> forward as a Fedora 16. It would be a very late exception, so we'll need
> to make a good case to FESCo.
> I've drafted an initial feature page:
> David, Angus and Matt - please feel free to add yourselves as owners.
> I'm not gonna pull this off without your help! :-)
> Next thing we're going to have to do is file a ticket with FESCo like
> the Java7 one:
So actually - once the feature page is done, it goes through the feature
wrangler, who will move the feature page into the FeatureReadyForFesco
category, and will also file the ticket. (The ticket #663 actually ...
failed to follow the process of going through the feature wrangler.)
And since I'm the feature wrangler anyway, I will make the ticket and so
My comments on the feature page:
* Features need to be at 100% by 9/13 - is SELinux assistance the only
thing holding this back from being at 100%?
Yes, that's probably the biggest issue. Dan Walsh has already written
some policy for glance, though, so I fully expect policy for Nova to
magically appear soon :)
Or is the intent to update to Diablo as well?
Yes. We're currently using the Diablo milestone4 release and Diablo is
in bugfix mode now, so updating to the finally release shouldn't be a
* Release notes need to be a bit more comprehensive - this is
what goes into the Fedora release notes. Usually some information about
what it is, does, etc. is helpful here. Probably combining a bit of the
summary with some of the detailed description would be useful here, as
well as including a link to any upstream release notes.
* Please elaborate on "hosting fedora images for openstack"
- would we
have to generate specific images, etc? I wonder if Major Hayden
(rackerhacker) could pipe in here - would it be possible to have Fedora
images at rackspace somehow? :) Alternately, I think we're pretty late
in the cycle to ask releng to figure out what to do here, and Oz isn't
part of that toolchain, so it would be something we'd have to figure out
how to do ourselves, and host it somewhere.
Yeah, I think we're pretty late too. Nice instructions for building
Fedora images should do it, I think. And the Oz instructions are fairly
close to that.