From Fedora Project Wiki
< Changes
(Created page with " <!-- Self Contained or System Wide Change Proposal? Use this guide to determine to which category your proposed change belongs to. Self Contained Changes are: * changes to i...") |
No edit summary |
||
| Line 25: | Line 25: | ||
== Summary == | == Summary == | ||
Changing how pungi works to make composes more distributed and transparent | Changing how pungi works to make composes more distributed and transparent. | ||
== Owner == | == Owner == | ||
| Line 55: | Line 55: | ||
Changing how pungi works to make composes, we aim to achieve a few goals. | Changing how pungi works to make composes, we aim to achieve a few goals. | ||
Always do a complete compose, including rawhide and branched. | * Always do a complete compose, including rawhide and branched. Essentially we will have TC composes daily. | ||
* Make sure that the tools used to make Fedora translate directly to making RHEL | |||
Make sure that the tools used to make Fedora translate directly to making RHEL | * Enable more people to be involved in the development of compose tools | ||
* Farm off compose tasks to hosts in koji | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 70: | Line 70: | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: Extend the functionality of pungi and koji | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Other developers: | * Other developers: NA <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
| Line 79: | Line 79: | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. | ||
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.--> | Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.--> | ||
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A | ** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | <!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | ||
* Policies and guidelines: | * Policies and guidelines: releng docs on how to do composes will need updating <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | ||
Revision as of 05:05, 25 November 2015
Pungi Refactor
Summary
Changing how pungi works to make composes more distributed and transparent.
Owner
- Name: Dennis Gilmore
- Email: dennis@ausil.us
- Release notes owner:
Current status
- Targeted release: Fedora 24
- Last updated: 2015-11-25
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
Changing how pungi works to make composes, we aim to achieve a few goals.
- Always do a complete compose, including rawhide and branched. Essentially we will have TC composes daily.
- Make sure that the tools used to make Fedora translate directly to making RHEL
- Enable more people to be involved in the development of compose tools
- Farm off compose tasks to hosts in koji
Benefit to Fedora
- Faster composes
- More frequent composes
- Nightly composes will look the same as a release compose
- More transparent and publicly visible logs.
- More people able to work on the tools used to make Fedora
Scope
- Proposal owners: Extend the functionality of pungi and koji
- Other developers: NA
- Release engineering: This will be a major change in how releng does composes
- List of deliverables: N/A
- Policies and guidelines: releng docs on how to do composes will need updating
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
There will be no changes to existing installs, The release tree will probably look a little differently and some files will have different names
How To Test
TODO
User Experience
Fedora Composes may look a bit different to previously but have all the same functionality.
Dependencies
livemedia-creator change
Contingency Plan
If we are unable to get the compose process changed before Alpha Change freeze we will revert to using the old method of composing Fedora.
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: Alpha Change freeze
- Blocks release? Yes
- Blocks product? All
Documentation
https://pagure.io/docs/releng/ https://pagure.io/docs/pungi/