From Fedora Project Wiki
Line 114: 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 -->
N/A (not a System Wide Change)
The AArch64 is similar to x86_64, ARMv7 the current primary architectures and other Fedora architectures so the user experience is expected to be the same as the other architectures. The install and boot paths are the same across all supported devices using uEFI and grub2 so there's no special cases.


== Dependencies ==
== Dependencies ==

Revision as of 18:21, 2 November 2017



AArch64 Server Promotion

Summary

Promote Aarch64 server technologies to Primary Architecture status. This would include the Server installer, the DVD installer ISOs, the Cloud (qcow2 images) and Docker base images.

Owner

Owner

  • Name: Peter Robinson
  • Email: pbrobinson@fedoraproject.org
  • Name: Paul Whalen
  • Email: pwhalen@fedoraproject.org
  • Release notes owner:
  • Responsible WG: ARM SIG

Current status

  • Targeted release: Fedora 28
  • Last updated: 2017-11-02
  • Tracking bug:

Detailed Description

The AArch64 Architecture in the server space is a mature product with numerous platforms widely available for testing. We support both SBSA Enterprise Haware as well as a number of Single Board Computers, initially officially supported in Fedora 27 with the aarch64 SBC Feature, with new device support being added all the time and more widely available and affordable hardware.

The changes is actually a minor one as we already produce all the deliverables as an Alternate Architecture, this primarily be a change of where the output of the artifacts are delivered on the mirrors and making the architecture a release blocking architecture.

Benefit to Fedora

This feature

Scope

  • Proposal owners: The general AArch64 support is already in place and is widely and actively supported by the Fedora ARM SIG and numerous ARM vendors and third parties in Fedora. There will be further and wider support, hardware enablement, polish and general improvements.
  • Other developers: N/A: There's no work required for other developers, the aarch64 architecture is already widely supported as an Alternate Architecture.
  • Release engineering: Needs approval from release engineering as a primary architecture as well as pungi configuration changes to output artifacts to new location on the primary mirror.
  • Policies and guidelines: Updates to the primary architectures and release blocking details will need to be updated to reflect that the AArch64 Server/Cloud/Docker components are now considered primary.
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

No impact on upgrades, for AArch64 systems running Fedora 27 or older releases the upgrades will be seemless as Mirror Manager will automatically deal with the location of the new Fedora 28 content.

How To Test

N/A (not a System Wide Change)

User Experience

The AArch64 is similar to x86_64, ARMv7 the current primary architectures and other Fedora architectures so the user experience is expected to be the same as the other architectures. The install and boot paths are the same across all supported devices using uEFI and grub2 so there's no special cases.

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) Feature is already mostly complete, upstream stable release is scheduled will within the required release window
  • 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