From Fedora Project Wiki
(Ready for wrangler)
(We are rebaing to 3.11)
 
(5 intermediate revisions by 2 users not shown)
Line 21: Line 21:
  
 
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
 
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
= Origin 3.10 <!-- The name of your change proposal --> =
+
=OpenShift Origin 3.11 <!-- The name of your change proposal --> =
  
 
== Summary ==
 
== Summary ==
Line 56: Line 56:
 
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 
-->
 
-->
* Tracker bug: <will be assigned by the Wrangler>
+
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1598406 #1598406]
 +
* Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/193 #193]
  
 
== Detailed Description ==
 
== Detailed Description ==
Line 103: Line 104:
 
<!-- 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?-->
  
* Release engineering: None (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
+
* Release engineering: None https://pagure.io/releng/issue/7581 <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
 
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
 
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
 
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
 
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
Line 181: Line 182:
 
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
 
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
 
-->
 
-->
 +
* Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/193 #193]
  
[[Category:ChangeReadyForWrangler]]
+
[[Category:ChangeAcceptedF29]]
 
<!-- When your change proposal page is completed and ready for review and announcement -->
 
<!-- When your change proposal page is completed and ready for review and announcement -->
 
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
 
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Latest revision as of 10:29, 2 October 2018


OpenShift Origin 3.11

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

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)
  • 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)

Release Notes

  • Release Notes tracking: #193