From Fedora Project Wiki
< Changes
Sinnykumari (talk | contribs) m (User Experience) |
Sinnykumari (talk | contribs) m (We will have cloud-base and container images in F28. Dropping Atomic from F28 becase of very long(14hrs) time for ostree repo creation on s390x) |
||
| (33 intermediate revisions by 2 users not shown) | |||
| Line 23: | Line 23: | ||
<!-- 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 --> | ||
= | = Cloud-base and Container images for s390x = | ||
== Summary == | == Summary == | ||
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. --> | <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. --> | ||
This change is to bring s390x architecture closer to other Fedora architectures by adding widely used Fedora variants. This includes container images and Cloud-base images (qcow2 and raw format). | |||
== Owner == | == Owner == | ||
| Line 36: | Line 36: | ||
* Name: [[User:sinnykumari| Sinny Kumari]] | * Name: [[User:sinnykumari| Sinny Kumari]] | ||
* Email: <sinnykumari@fedoraproject.org> | * Email: <sinnykumari@fedoraproject.org> | ||
* Release notes | * Release notes ticket: [https://pagure.io/fedora-docs/release-notes/issue/107 #107] | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | ||
--> | --> | ||
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) | <!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) | ||
* Product: | * Product: --> | ||
* Responsible WG: | * Responsible WG: Fedora s390x SIG | ||
== Current status == | == Current status == | ||
| Line 56: | Line 55: | ||
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: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1547235 #1547235] | ||
== Detailed Description == | == Detailed Description == | ||
<!-- 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. --> | ||
We already ship Cloud-base and Container images on other 64-bit Fedora supported architectures- aarch64, x86_64 and ppc64le. With Fedora 27, s390x is part of primary koji build system. | |||
Currently, we only ship Server and Everything variants for s390x. So, our next steps should be to have missing Fedora variants on s390x architecture which users will find useful. This change brings in shipping Cloud-base and Container images in Fedora for s390x as well. | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
s390x users will stick to Fedora for their cloud environment set-up while running VMs or containers. Also, we are one step closer on Fedora being fully multi-arch. | |||
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: These are isolated changes which doesn't impact existing Fedora 28 release plan on s390x. To have these changes ready to ship in Fedora 28, we mainly require s390x koji builders configured to run these composes, [https://pagure.io/pungi-fedora/pull-request/496 changes in pungi configuration] to enable the additional compose and fixing s390x specific issues encountered when compose fails to run. | ||
<!-- 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: Changes in Fedora infrastructure configs/scripts will be required to have s390x builders configured to run additional composes. [https://pagure.io/fedora-infrastructure/issue/6659 Fedora Infrastructure issue] has been filed to keep track of required changes to be done. | ||
<!-- 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: [https://pagure.io/releng/ | * Release engineering: [https://pagure.io/releng/issue/7286 #Releng 7286] | ||
<!-- 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 --> | ||
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- ** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
** List of deliverables: This change will bring following variants and deliverables for s390x architecture: | |||
*** Container - Provides Fedora-Container-Minimal-Base and Fedora-Container-Base images | |||
*** Cloud - Provides Fedora-Cloud-Base images (qcow2 and raw) | |||
<!-- 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: No change should be required <!-- 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. --> | ||
| Line 91: | Line 93: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
No impact on upgrades because this change brings new deliverables which are isolated from existing deliverables provided on s390x. | |||
== How To Test == | == How To Test == | ||
Any of these images should be easily testable on | Any of these images should be easily testable on a s390x Virtual Machine running latest Fedora. Method of testing is similar to how we test on other architectures like x86_64, ppc64le. | ||
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | ||
| Line 108: | Line 110: | ||
3. What are the expected results of those actions? | 3. What are the expected results of those actions? | ||
--> | --> | ||
== User Experience == | == User Experience == | ||
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
s390x users will be able to run | s390x users will be able to run container and cloud Images officially shipped by Fedora in their environment set-up. | ||
== Dependencies == | == Dependencies == | ||
| Line 121: | Line 120: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
None | |||
== Contingency Plan == | == Contingency Plan == | ||
<!-- 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: Reverting back related changes done in f28 branch of [https://pagure.io/pungi-fedora/ pungi-fedora] should be sufficient.<!-- 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: | * Contingency deadline: Beta Freeze | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? | * Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
* Blocks product? No <!-- Applicable for Changes that blocks specific product release/Fedora.next --> | * Blocks product? No <!-- Applicable for Changes that blocks specific product release/Fedora.next --> | ||
| Line 136: | Line 135: | ||
<!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | <!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | ||
[[Architectures/s390x | Fedora s390x wiki page]] will be updated with required changes. | [[Architectures/s390x | Fedora s390x wiki page]] will be updated with required changes. | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES | <!-- REQUIRED FOR SYSTEM WIDE CHANGES | ||
N/A (not a System Wide Change) --> | N/A (not a System Wide Change) --> | ||
| Line 147: | Line 145: | ||
--> | --> | ||
[[Category: | [[Category:ChangeAcceptedF28]] | ||
<!-- 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 --> | ||
| Line 154: | Line 152: | ||
<!-- Select proper category, default is Self Contained Change --> | <!-- Select proper category, default is Self Contained Change --> | ||
[[Category:SelfContainedChange]] | <!-- [[Category:SelfContainedChange]] --> | ||
[[Category:SystemWideChange]] | |||
Latest revision as of 05:19, 23 March 2018
Cloud-base and Container images for s390x
Summary
This change is to bring s390x architecture closer to other Fedora architectures by adding widely used Fedora variants. This includes container images and Cloud-base images (qcow2 and raw format).
Owner
- Name: Sinny Kumari
- Email: <sinnykumari@fedoraproject.org>
- Release notes ticket: #107
- Responsible WG: Fedora s390x SIG
Current status
Detailed Description
We already ship Cloud-base and Container images on other 64-bit Fedora supported architectures- aarch64, x86_64 and ppc64le. With Fedora 27, s390x is part of primary koji build system. Currently, we only ship Server and Everything variants for s390x. So, our next steps should be to have missing Fedora variants on s390x architecture which users will find useful. This change brings in shipping Cloud-base and Container images in Fedora for s390x as well.
Benefit to Fedora
s390x users will stick to Fedora for their cloud environment set-up while running VMs or containers. Also, we are one step closer on Fedora being fully multi-arch.
Scope
- Proposal owners: These are isolated changes which doesn't impact existing Fedora 28 release plan on s390x. To have these changes ready to ship in Fedora 28, we mainly require s390x koji builders configured to run these composes, changes in pungi configuration to enable the additional compose and fixing s390x specific issues encountered when compose fails to run.
- Other developers: Changes in Fedora infrastructure configs/scripts will be required to have s390x builders configured to run additional composes. Fedora Infrastructure issue has been filed to keep track of required changes to be done.
- Release engineering: #Releng 7286
- List of deliverables: This change will bring following variants and deliverables for s390x architecture:
- Container - Provides Fedora-Container-Minimal-Base and Fedora-Container-Base images
- Cloud - Provides Fedora-Cloud-Base images (qcow2 and raw)
- List of deliverables: This change will bring following variants and deliverables for s390x architecture:
- Policies and guidelines: No change should be required
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
No impact on upgrades because this change brings new deliverables which are isolated from existing deliverables provided on s390x.
How To Test
Any of these images should be easily testable on a s390x Virtual Machine running latest Fedora. Method of testing is similar to how we test on other architectures like x86_64, ppc64le.
User Experience
s390x users will be able to run container and cloud Images officially shipped by Fedora in their environment set-up.
Dependencies
None
Contingency Plan
- Contingency mechanism: Reverting back related changes done in f28 branch of pungi-fedora should be sufficient.
- Contingency deadline: Beta Freeze
- Blocks release? No
- Blocks product? No
Documentation
Fedora s390x wiki page will be updated with required changes.