No edit summary |
(add to Cloud SIG category) |
||
| Line 76: | Line 76: | ||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | ||
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | ||
[[Category:Cloud SIG]] | |||
Revision as of 16:21, 12 January 2012
OpenStack using Oz for image building
Summary
Add a virtual machine image building service to OpenStack, which will use Oz and libguestfs.
Owner
- Name: Richard Jones
- Email: rjones@redhat.com
Current status
- Targeted release: Fedora 17
- Last updated: 2011-12-20
- Percentage of completion: 00%
Detailed Description
With upstream OpenStack there is currently no way to build your own images. All you can do is to upload guests that you have built by hand.
Ideally what you should be able to do is say "give me a Fedora 16 guest" or "give me a Windows 2003 guest with Firefox installed". Oz is an image building tool which lets you do this.
Therefore we would like to add Oz as a service to OpenStack upstream, and package this for Fedora 17.
Benefit to Fedora
Users who install Fedora 17 and OpenStack Essex will have an easy-to-use image building service available.
Scope
We will aim to get this feature into OpenStack upstream first, ensure that it is backported to Essex upstream, and then package it for Fedora 17.
How To Test
TBD. A test day has been booked for OpenStack.
User Experience
It will be very easy to build images by simply specifying the guest type and version required using the Nova command line tools.
Dependencies
(None, since Oz and libguestfs are already packaged for Fedora)
Contingency Plan
No plan needed. If the feature is not ready, it can simply be dropped.