No edit summary |
|||
| Line 17: | Line 17: | ||
* Targeted release: [[Releases/15| Fedora 15]] | * Targeted release: [[Releases/15| Fedora 15]] | ||
* Last updated: 2010-11-05 | * Last updated: 2010-11-05 | ||
* Percentage of completion: | * Percentage of completion: 90% | ||
== Detailed Description == | == Detailed Description == | ||
Revision as of 16:07, 25 January 2011
Rework Buildinstall
Summary
Replace the contents of the scripts/ subdirectory in anaconda with an external tool named lorax that generates the installation images for distribution trees. Lorax should be flexible enough for use as a standalone program, but capable of easy integration in to pungi and other release engineering tools. Image contents should be configurable at runtime and not require a rebuild of lorax.
https://fedorahosted.org/lorax/ https://fedorahosted.org/lorax/browser
Owner
- Name: Jesse Keating
- Name: Martin Gracik (mgracik AT redhat DOT com)
Current status
- Targeted release: Fedora 15
- Last updated: 2010-11-05
- Percentage of completion: 90%
Detailed Description
The buildinstall scripts are a mess. Cleaning them up would provide benefit to tree composes and more.
Benefit to Fedora
- Release engineering would have the flexibility to tweak install image contents without depending on a new anaconda build.
- Joint ownership of image building between installer team and rel-eng.
- Anaconda releases are not so strictly tied to rel-eng schedules.
- Ability to change image contents without needing an 11th anaconda build.
- Better integration in to pungi rather than the hackjob pile of shell scripts currently in anaconda.
- No more upd-instroot or mk-images nightmare.
Scope
Lorax will be a completely separate project and component in the distribution. It will take the place of the scripts/ subdirectory in anaconda. Downstream users of lorax will be pungi and possibly other release engineering tools that come along.
Test Plan
Generate test images outside of the rel-eng process, compare contents with images currently generated by the scripts/ tools. Clean up inconsistencies and problems before having pungi use lorax directly.
User Experience
End users are not directly affected by this change.
Dependencies
Lorax itself is not dependent on any other component being delivered, but coordination with pungi will need to be handled so the transition to lorax is not problematic.
Contingency Plan
Continue using the existing rel-eng scripts that are part of the anaconda project.