From Fedora Project Wiki
m (dependencies)
m (contingency plan)
Line 127: Line 127:


<!-- 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: Initial attempt on producing these images on local s390x machines seems to give working docker images. Some work required for having working Atomic images (e.g. [https://bugzilla.redhat.com/show_bug.cgi?id=1535043 oz package update] ) which is doable in F28 time-frame. Also, required  [https://pagure.io/pungi-fedora/pull-request/496 changes in pungi configuration] are already in place. Still, if due to some reason we are not able to get these images ready for F28, they can be moved to Fedora 29. <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* 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: Fedora 28 Final Freeze
* 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? N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* 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 -->


Revision as of 18:24, 20 February 2018



Atomic, Cloud and Docker images for s390x

Summary

This change is to bring s390x architecture closer to other Fedora architectures by adding widely used Fedora variants. This includes docker images, Atomic Host (iso, qcow2 and raw format) and regular Cloud Images (qcow2 and raw format).

Owner

  • Name: Sinny Kumari
  • Email: <sinnykumari@fedoraproject.org>
  • Release notes owner:
  • Responsible WG: Fedora s390x SIG

Current status

  • Targeted release: Fedora 28
  • Last updated: 2018-02-20
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

We already ship Atomic, Cloud and Docker 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 Docker 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
      • Cloud - Provides Fedora Cloud iso
      • Atomic - Provides Fedora Atomic iso
      • CloudImages - Provides Fedora-Cloud-Base and Fedora-Atomic 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 docker 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.

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

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/Atomic_Cloud_and_Docker_images_for_s390x&oldid=511379"