From Fedora Project Wiki
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)
 
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 -->
= Atomic, Cloud and Container images for s390x =
+
= 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, Atomic Host (iso, qcow2 and raw format) and regular Cloud Images (qcow2 and raw format).
+
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 60: Line 60:
  
 
<!-- 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 Atomic, Cloud 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.
+
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 brings in shipping Atomic, Cloud and Container images in Fedora for s390x as well.
+
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 ==
Line 79: Line 79:
 
<!-- ** [[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:
 
** List of deliverables: This change will bring following variants and deliverables for s390x architecture:
*** Container - Provides Fedora-Container-Minimal-Base and Fedora-Container-Base
+
*** Container - Provides Fedora-Container-Minimal-Base and Fedora-Container-Base images
*** Cloud - Provides Fedora Cloud iso
+
*** Cloud - Provides Fedora-Cloud-Base images (qcow2 and raw)
*** Atomic - Provides Fedora Atomic iso
 
*** CloudImages - Provides Fedora-Cloud-Base and Fedora-Atomic 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 -->
  
Line 116: Line 114:
 
<!-- 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 container and cloud Images officially shipped by Fedora in their environment set-up. They will also be able to run Atomic Host on s390x which is optimized to run container images.
+
s390x users will be able to run container and cloud Images officially shipped by Fedora in their environment set-up.
  
 
== Dependencies ==
 
== Dependencies ==

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

Release Notes