< Changes
(→Detailed Description: update description) |
m (Tweaks and cleanups) |
||
| Line 14: | Line 14: | ||
* Name: [[https://pagure.io/cloud-sig| Fedora Cloud SIG]] | * Name: [[https://pagure.io/cloud-sig| Fedora Cloud SIG]] | ||
<!-- 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. --> | <!-- 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> | * 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]] | * Name: [[User:davdunc| David Duncan]] | ||
* Email: davdunc@amazon.com | * Email: davdunc@amazon.com | ||
| Line 53: | Line 53: | ||
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --> | <!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --> | ||
See the discussion here: https://discussion.fedoraproject.org/t/fedora-cloud-edition-not-an-edition-and-the-future/34064/23 | See the discussion here: https://discussion.fedoraproject.org/t/fedora-cloud-edition-not-an-edition-and-the-future/34064/23 | ||
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 | 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 circumstances. 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 | These images should be able to handle virtualization for many different workloads. The use of graphical environments or Server roles satisfy only highly specialized cloud experiences. | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 72: | Line 72: | ||
That introduces the highlights for the reasons Fedora Cloud Base fits | That introduces the highlights for the reasons Fedora Cloud Base fits | ||
as an | as an | ||
[https://docs.fedoraproject.org/en-US/council/policy/edition-promotion-policy/ | |||
Edition | 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 | 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 | capable of running. There has been a lot of work explored here and a | ||
| Line 83: | Line 83: | ||
* Proposal owners: | * 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?--> | <!-- 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?--> | ||
[[ | [[Cloud/Cloud_PRD|Cloud PRD]] and [[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 --> | * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Revision as of 18:02, 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
- 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
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.The Fedora Cloud Base image is uniquely focused on supporting cloud and other fail-only environments.
Feedback
See the discussion here: https://discussion.fedoraproject.org/t/fedora-cloud-edition-not-an-edition-and-the-future/34064/23
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 circumstances. 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 virtualization 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/ 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