Anaconda/Features/ReworkBuildinstall

From FedoraProject

< Anaconda | Features(Difference between revisions)
Jump to: navigation, search
(Owner)
(Test Plan)
 
(3 intermediate revisions by 2 users not shown)
Line 4: Line 4:
  
 
== Summary ==
 
== 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 ==
 
== Owner ==
Line 10: Line 15:
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/X| Fedora X]]  
+
* Targeted release: [[Releases/15| Fedora 15]]  
* Last updated: 2007-11-19
+
* Last updated: 2010-11-05
* Percentage of completion: 0%
+
* Percentage of completion: 90%
  
 
== Detailed Description ==
 
== Detailed Description ==
Line 19: Line 24:
  
 
== Benefit to Fedora ==
 
== 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 ==
 
== 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 ==
 
== 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.
 +
 +
After this, provide a patch for pungi so lorax will get used by rel-eng process for Fedora test days.
  
 
== User Experience ==
 
== User Experience ==
 +
 +
End users are not directly affected by this change.
  
 
== Dependencies ==
 
== 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 ==
 
== Contingency Plan ==
 +
 +
Continue using the existing rel-eng scripts that are part of the anaconda project.
  
 
== Documentation ==
 
== Documentation ==
  
 
== Release Notes ==
 
== Release Notes ==
 +
 
[[Category:Anaconda]]
 
[[Category:Anaconda]]

Latest revision as of 16:08, 25 January 2011

Contents

[edit] Rework Buildinstall

[edit] 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

[edit] Owner

[edit] Current status

  • Targeted release: Fedora 15
  • Last updated: 2010-11-05
  • Percentage of completion: 90%

[edit] Detailed Description

The buildinstall scripts are a mess. Cleaning them up would provide benefit to tree composes and more.

[edit] 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.

[edit] 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.

[edit] 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.

After this, provide a patch for pungi so lorax will get used by rel-eng process for Fedora test days.

[edit] User Experience

End users are not directly affected by this change.

[edit] 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.

[edit] Contingency Plan

Continue using the existing rel-eng scripts that are part of the anaconda project.

[edit] Documentation

[edit] Release Notes