From Fedora Project Wiki
(Initial preview: Not yet ready for review)
 
(Initial save)
Line 48: Line 48:


== 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. -->The Fedora Cloud Working Group is committed to producing, testing, and distributing the Fedora Cloud Base as an [[https://docs.fedoraproject.org/en-US/council/policy/edition-promotion-policy/| Edition]] and to deliver a tailored experience across multiple virtual compute environments. This includes support for more established public cloud compute environments, like Amazon EC2, Google Compute Platform, or Azure Compute and also other environments, such as Hashicorp's Vagrant or Gnome Boxes. It would be ideal if these were easily discoverable from the Fedora landing pages and supported side by side with other specialized editions including Fedora Server and Fedora Workstation.


== Feedback ==
== Feedback ==
Line 189: Line 189:
-->
-->


Release Notes will be published in Fedora Cloud Base documentation. As a part of the transition to Edition, Cloud documentation will move from the Wiki to Fedora Documentation.
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
 
-->
 
''Fedora Cloud Base Edition''
  Announcing the promotion of the Fedora Cloud Base to official status as a Fedora Edition. Fedora Cloud Base images can now be found at https://getfedora.org

Revision as of 05:02, 18 January 2022


Return Cloud Base to Edition Status

Summary

Cloud 'should' be listed on getfedora.org with equal billing to Workstation, Server and IoT. The petition to instate the Cloud Base as an official Edition is based on the clear identification of unique environmental support requirements for private hyperscaler and public cloud environments not specifically addressed by other Editions.

Owner


Current status

  • Targeted release: Fedora Linux 36
  • Last updated: 2022-01-18
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

The Fedora Cloud Working Group is committed to producing, testing, and distributing the Fedora Cloud Base as an [Edition] and to deliver a tailored experience across multiple virtual compute environments. This includes support for more established public cloud compute environments, like Amazon EC2, Google Compute Platform, or Azure Compute and also other environments, such as Hashicorp's Vagrant or Gnome Boxes. It would be ideal if these were easily discoverable from the Fedora landing pages and supported side by side with other specialized editions including Fedora Server and Fedora Workstation.

Feedback

See the discussion here: https://discussion.fedoraproject.org/t/fedora-cloud-edition-not-an-edition-and-the-future/34064/23?u=mattdm

Benefit to Fedora

Cloud is a base, it has variations that work in different environments, but it supports work that is not related to the “Just enough” position of FCOS and extends the surface for experimental workloads at the base operating system layers. The Cloud working group has a very dedicated group of supporters who find value beyond the requirements of the other editions. With the adoption of btrfs in this most recent release there was much stir over how it could fit so well and yet diverge so much from Container exclusive or Server goals, further accenting this dividing line.

That introduces the highlights for the reasons Fedora Cloud Base fits as an [Edition]. The cloud base as an edition is plastic in a way that is appropriate to match the various virtual environments on which it is capable of running. There has been a lot of work explored here and a lot of writing done to find that next level. In previous years, we had lots of multi-cloud aspirations that couldn’t be fulfilled, but they can be now and we want to ensure availability and ease of use.

Scope

  • Proposal owners:

[Cloud PRD] and [Technical Specification] updates are in process to ensure that we provide sufficient roadmap and technical specification to confirm alignment with the Fedora Project overall and especially that we are aligned with the Cloud Base users and established infrastructure providers. This will also increase the number of blog posts that the Cloud Working Group provides and increase the number of submissions to PR engagements for the Fedora Cloud Base work.

  • Other developers:
Web changes will need to be made to accomodate the publication of links and some artwork will need to be created to align with current Project design. We expect to be responsible for infrastructure updates related to image deployment. We also expect to be the first stop for other editions and spins for image publication assistance. 

TBD

  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives:

Upgrade/compatibility impact

This is a logical change and does not affect upgrade or compatibility requirements for previous releases. 


How To Test

Standard QA testing and evaluation methods apply for QA Compose.


User Experience

This may change where Fedora Cloud Base Images are located in the web portal, but it will most likely be simpler to discover the images themselves. 

Dependencies

There are no currently known dependencies for this.

Contingency Plan

If this is not approved for F36, we will roll forward to F37 and prepare as required. There is no technical change in the image build requirements.

  • Contingency mechanism: N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? No


Documentation

N/A (not a System Wide Change)

Release Notes

Fedora Cloud Base Edition

 Announcing the promotion of the Fedora Cloud Base to official status as a Fedora Edition. Fedora Cloud Base images can now be found at https://getfedora.org