(enter detailed summary) |
(update benefit to fedora) |
||
Line 66: | Line 66: | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
Ability to support/switch between multiple OpenShift versions with minimal effort on the user's part would make both users and maintainers happy. | |||
<!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved? | <!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved? |
Revision as of 19:58, 24 July 2018
OpenShift modules
Summary
Create modules for all supported OpenShift versions.
Owner
- Name: Lokesh Mandvekar
- Email: lsm5@fedoraproject.org
- Release notes owner:
Current status
- Targeted release: Fedora 29
- Last updated: 2018-07-24
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
Currently, the OpenShift upstream project develops and supports multiple versions of OpenShift, along with component tools like cri-o/cri-tools which have their versions tightly coupled to OpenShift versions. This change will result in creation of module builds which will contain the rpms for OpenShift / cri-o and other required tools.
Benefit to Fedora
Ability to support/switch between multiple OpenShift versions with minimal effort on the user's part would make both users and maintainers happy.
Scope
- Proposal owners: Creation / review / koji builds of OpenShift modules
- Other developers: N/A (not a System Wide Change)
- Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
N/A (not a System Wide Change)
User Experience
Users will be able to quickly setup OpenShift environments and switch between versions.
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
N/A (not a System Wide Change)