From Fedora Project Wiki
< Changes
(→Detailed Description: update description) |
(Add trackers) |
||
| (21 intermediate revisions by 5 users not shown) | |||
| Line 5: | Line 5: | ||
== Summary == | == 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?". --> | <!-- 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 Workstation, Server and IoT. The petition to | Cloud '''should''' be listed on getfedora.org with Workstation, Server and IoT. The petition to reinstate 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 == | == Owner == | ||
| Line 12: | Line 12: | ||
This should link to your home wiki page so we know who you are. | This should link to your home wiki page so we know who you are. | ||
--> | --> | ||
* Name: | * 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 21: | Line 21: | ||
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | ||
--> | --> | ||
== Current status == | == Current status == | ||
[[Category:ChangePageIncomplete]] | <!-- [[Category:ChangePageIncomplete]] --> | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
[[Category:ChangeAcceptedF37]] | |||
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> | <!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> | ||
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--> | <!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--> | ||
<!-- Select proper category, default is Self Contained Change --> | <!-- Select proper category, default is Self Contained Change --> | ||
[[Category:SelfContainedChange]] | <!-- [[Category:SelfContainedChange]] --> | ||
[[Category:SystemWideChange]] | |||
* Targeted release: [[Releases/ | * Targeted release: [[Releases/37 | Fedora Linux 37 ]] | ||
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
| Line 42: | Line 42: | ||
ON_QA -> change is fully code complete | ON_QA -> change is fully code complete | ||
--> | --> | ||
* FESCo issue: | * [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/3EIQGEYDHHPV5EYGCGJAUJOACF5IZ6Q4/ devel thread] | ||
* Tracker bug: | * FESCo issue: [https://pagure.io/fesco/issue/2802 #2802] | ||
* Release notes tracker: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2096419 #2096419] | ||
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/847 #847] | |||
== 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 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. | 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 == | == Feedback == | ||
<!-- 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 == | ||
Cloud is a base, it has variations that work in different | 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. | ||
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 | 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]. 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. | ||
Edition | |||
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 == | == Scope == | ||
<!-- 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?--> | ||
[[ | * Proposal owners: [[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. | ||
<!-- 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. | <!-- 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?--> | ||
* 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: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Release engineering: [https://pagure.io/releng/issues #Releng issue number] `TBD` | ||
<!-- 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. | <!-- 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 --> | 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 --> | ||
* Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. Please submit a pull request with the proposed changes before submitting your Change proposal. --> | <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. Please submit a pull request with the proposed changes before submitting your Change proposal. --> | ||
* Trademark approval: | * Trademark approval: https://pagure.io/Fedora-Council/tickets/issue/397 | ||
* Alignment with Objectives: | * Alignment with Objectives: | ||
| Line 105: | Line 91: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
In restoring the Cloud edition to the official Edition status, we eliminate any issues. It is with the downgrade to edition status where there will be an impact. The release information will have to be modified to remove the edition identifiers and this may cause an impact to current users. | |||
== How To Test == | == How To Test == | ||
| Line 137: | Line 123: | ||
- Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running". | - Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running". | ||
- Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system. | - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system. | ||
--> 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. | --> | ||
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 == | == Dependencies == | ||
| Line 148: | Line 135: | ||
<!-- 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: (What to do? Who will do it?) 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 --> Remove the | ||
<!-- 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. --> We could include this as late as the rc1 | ||
* Contingency deadline: | * Contingency deadline: 2022-10-18 <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- 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? | * Blocks release? This is not a release blocker <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
If this is not approved for | If this is not approved for F37, we will roll forward to F38 and prepare as required. There is no technical change in the image build requirements. | ||
== Documentation == | == Documentation == | ||
| Line 160: | Line 147: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Documentation is currently in the wiki for the [[Cloud|working group]] and the [[Cloud SIG]] and is in the process of a series of updates to be moved to the [[DocsProject|Fedora Docs]] format | |||
== Release Notes == | == Release Notes == | ||
| Line 169: | Line 157: | ||
''Fedora Cloud Base Edition'' | ''Fedora Cloud Base Edition'' | ||
Fedora Cloud Base has been promoted to official status as a Fedora Edition. Fedora Cloud Base Images can now be downloaded from https://getfedora.org. | |||
Latest revision as of 18:57, 13 June 2022
Return Cloud Base to Edition Status
Summary
Cloud should be listed on getfedora.org with Workstation, Server and IoT. The petition to reinstate 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 37
- Last updated: 2022-06-13
- devel thread
- FESCo issue: #2802
- Tracker bug: #2096419
- Release notes tracker: #847
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 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: https://pagure.io/Fedora-Council/tickets/issue/397
- Alignment with Objectives:
Upgrade/compatibility impact
In restoring the Cloud edition to the official Edition status, we eliminate any issues. It is with the downgrade to edition status where there will be an impact. The release information will have to be modified to remove the edition identifiers and this may cause an impact to current users.
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) Remove the
We could include this as late as the rc1
- Contingency deadline: 2022-10-18
- Blocks release? This is not a release blocker
If this is not approved for F37, we will roll forward to F38 and prepare as required. There is no technical change in the image build requirements.
Documentation
Documentation is currently in the wiki for the working group and the Cloud SIG and is in the process of a series of updates to be moved to the Fedora Docs format
Release Notes
Fedora Cloud Base Edition
Fedora Cloud Base has been promoted to official status as a Fedora Edition. Fedora Cloud Base Images can now be downloaded from https://getfedora.org.