Changes/KojiSignedRepos

Koji Generates Repositories of Signed RPMs

Summary

Extend Koji with a new feature that allows users to generate yum repositories of signed RPMs.

Owner

• Name: Jay Greguske
• Email: jgregusk with the usual red hat domain
• Release notes owner:

Current status

• Targeted release: Fedora 24
• Last updated: 2015-11-09
• Tracker bug: <will be assigned by the Wrangler>

Detailed Description

This is a significant enabler for generating DVD media, other ISOs, and images more efficiently. It also allows other tools such as mash or pungi to offload much of the heavy-lifting to the build system. Longer term, we may be able to reduce the number of tools needed to manufacture Fedora releases.

Benefit to Fedora

The benefit to Release Engineering should be self-evident: less tools, hosts, and services to maintain. This opens the door a little to let a small set of users generate their own signed repositories from Koji if they want to as well. This may be useful for QA testing.

Scope

• Proposal owners: Jay Greguske

• Release engineering: This feature does require coordination with release engineering (e.g. changes to installer image generation or update package delivery.)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

• Contingency mechanism: Just use the old process for generating Fedora composes and delivering them.
• Contingency deadline: N/A (not a System Wide Change)
• Blocks release? Probably not.
• Blocks product? Nope

Documentation

This should not affect Fedora documentation for users, but it will affect Standard Operating Procedures (SOPs) for Rel-Eng. If the current process to build and release Fedora is documented anywhere, it will need to be updated.