(Initial Origin change proposal) |
(Contingency and update ansible mention) |
||
| Line 62: | Line 62: | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
Rebase of the Origin package to the latest upstream release. To note upgrade path from previous version (3.9) will not be covered by this change(dnf update origin, will most | Rebase of the Origin package to the latest upstream release. To note upgrade path from previous version (3.9) will not be covered by this change(dnf update origin, will most certainly be unable to cleanly update Origin cluster), any one interested in helping out with the supportable update path please reach out to the change owner or any origin maintainer. Upstream provided update ansible playbooks are located at https://github.com/openshift/openshift-ansible/tree/master/playbooks/byo/openshift-cluster/upgrades | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 162: | Line 162: | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: | * Contingency mechanism: Revert to the older version (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Revision as of 12:06, 19 June 2018
Origin 3.10
Summary
Rebase of the Openshift Origin package to the latest upstream version, along with introduction of necessary infrastructure container images.
Owner
- Name: Jakub Čajka
- Email: jcajka@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 29
- Last updated: 2018-06-19
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
Rebase of the Origin package to the latest upstream release. To note upgrade path from previous version (3.9) will not be covered by this change(dnf update origin, will most certainly be unable to cleanly update Origin cluster), any one interested in helping out with the supportable update path please reach out to the change owner or any origin maintainer. Upstream provided update ansible playbooks are located at https://github.com/openshift/openshift-ansible/tree/master/playbooks/byo/openshift-cluster/upgrades
Benefit to Fedora
Keeping up with latest and greatest of Openshift Origin Fedora will deliver cutting edge platform for development, testing and deployment of Openshift Origin. With introduction of the infrastructure container images it will be possible to run Openshift Origin cluster top to bottom based on the Fedora distribution in contrast of using the upstream built images.
Scope
- Proposal owners: rebase of the package, creation of the missing infrastructure container images
- Other developers: N/A (not a System Wide Change)
- Release engineering: None (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines: None (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
Latest version of the oc client will be available to the end user allowing them to interact with the latest version of Origin based openshift clusters.
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: Revert to the older version (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)