Revision as of 05:50, 18 January 2022

Return Cloud Base to Edition Status

Summary

Cloud 'should' be listed on getfedora.org with 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

Name: [Fedora Cloud SIG]
Email: cloud@list.fedoraproject.org <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>
Name: David Duncan
Email: davdunc@amazon.com

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

Feedback

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

Some specific feedback received was that we could potentially deploy images of Fedora Workstation or Fedora Server to accomplish the same tasks that are accomplished with Fedora Cloud Base, but that is generally incorrect. Cloud specific workloads are not meant to be used in the same way as these other editions except under specific circumestances. Cloud specific configurations favor automated deployments with monitoring and logging handled to some degree through remote services. They are meant to be deployed sparingly and then to increase in numbers for scalability.

These images should be able to handle vrtualization for many different workloads. The use of graphical environments or Server roles satisfy only highly specialized cloud experiences.

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 like those of FCOS or Server goals, further accenting this dividing line.

That introduces the highlights for the reasons Fedora Cloud Base fits as an [[https://docs.fedoraproject.org/en-US/council/policy/edition-promotion-policy/%7C 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.

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.

Release engineering: #Releng issue number

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

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

Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
Contingency deadline: N/A (not a System Wide Change)
Blocks release? N/A (not a System Wide Change), Yes/No

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.

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 from https://getfedora.org

@@ Line 1: / Line 1: @@
 <!-- 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 -->
@@ Line 7: / Line 5: @@
 == 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. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
-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.
+Cloud 'should' be listed on getfedora.org with 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 ==
@@ Line 15: / Line 13: @@
 -->
 * Name: [[https://pagure.io/cloud-sig| Fedora Cloud SIG]]
-* Email: cloud@list.fedoraproject.org
+<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
+* Email: cloud@list.fedoraproject.org  <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>
 * Name: [[User:davdunc| David Duncan]]
 * Email: davdunc@amazon.com
@@ Line 48: / Line 47: @@
 == 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. -->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.
+<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 == Feedback ==
@@ Line 55: / Line 54: @@
 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 ==
+Some specific feedback received was that we could potentially deploy images of Fedora Workstation or Fedora Server to accomplish the same tasks that are accomplished with Fedora Cloud Base, but that is generally incorrect. Cloud specific workloads are not meant to be used in the same way as these other editions except under specific circumestances. Cloud specific configurations favor automated deployments with monitoring and logging handled to some degree through remote services. They are meant to be deployed sparingly and then to increase in numbers for scalability.
-<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
-      Be sure to include the following areas if relevant:
-      If this is a major capability update, what has changed?
-           For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
-      If this is a new functionality, what capabilities does it bring?
-           For example: This change allows package upgrades to be performed automatically and rolled-back at will.
-      Does this improve some specific package or set of packages?
-           For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
-      Does this improve specific Spins or Editions?
-           For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
-      Does this make the distribution more efficient?
-           For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
-      Is this an improvement to maintainer processes?
-           For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
-      Is this an improvement targeted as specific contributors?
-           For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.
-     When a Change has multiple benefits, it's better to list them all.
+These images should be able to handle vrtualization for many different workloads. The use of graphical environments or Server roles satisfy only highly specialized cloud experiences.
-     Consider these Change pages from previous editions as inspiration:
+== Benefit to Fedora ==
-     https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
-     https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
-     https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
-     https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
-     https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
--->
 Cloud is a base, it has variations that work in different
 environments, but it supports work that is not related to the “Just
@@ Line 90: / Line 66: @@
 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,
+and yet diverge so much from ''Container'' exclusive like those of FCOS or ''Server'' goals,
 further accenting this dividing line.
-That introduces the highlights for the reasons Fedora Cloud Base fits as an [[https://docs.fedoraproject.org/en-US/council/policy/edition-promotion-policy/| Edition]].
+That introduces the highlights for the reasons Fedora Cloud Base fits
-The cloud base as an edition is plastic in a way that is appropriate
+as an
-to match the various virtual environments on which it is capable of
+[[https://docs.fedoraproject.org/en-US/council/policy/edition-promotion-policy/|
-running. There has been a lot of work explored here and a lot of
+Edition]]. The cloud base as an edition is plastic in a way that is
-writing done to find that next level. In previous years, we had lots of
+appropriate to match the various virtual environments on which it is
-multi-cloud aspirations that couldn’t be fulfilled, but they can be now and we want to ensure availability and ease of use.
+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:
 <!-- 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?-->
-[[https://fedoraproject.org/wiki/Cloud/Cloud_PRD| Cloud PRD]] and [[https://fedoraproject.org/wiki/CloudBase/Technical_Specification| 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.
+[[https://fedoraproject.org/wiki/Cloud/Cloud_PRD| Cloud PRD]] and [[https://fedoraproject.org/wiki/CloudBase/Technical_Specification| 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.
 * Other developers: <!-- REQUIRED FOR SYSTEM WIDE 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?--> 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.
+<!-- 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?--> 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.
-* Release engineering: [https://pagure.io/releng/issues #Releng issue number] N/A<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- 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 -->`TBD`
@@ Line 122: / Line 101: @@
 == Upgrade/compatibility impact ==
-<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> This is a logical change and does not affect upgrade or compatibility requirements for previous releases.
+<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 166: / Line 145: @@
 == 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.
 <!-- 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: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- 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. -->
 * Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
-* Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+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.
 == Documentation ==
@@ Line 183: / Line 162: @@
 == Release Notes ==
-<!-- 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.
-Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
--->
 <!-- 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.
@@ Line 195: / Line 168: @@
 ''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
+   Announcing the promotion of the Fedora Cloud Base to official status as a Fedora Edition. Fedora Cloud Base Images can now be found from https://getfedora.org

Search

Changes/RestoreCloudEdition: Difference between revisions