From Fedora Project Wiki
< Changes
mNo edit summary |
m (→Owner) |
||
| (16 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}} | <!--{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}} | ||
--> | |||
<!-- Self Contained or System Wide Change Proposal? | <!-- Self Contained or System Wide Change Proposal? | ||
Use this guide to determine to which category your proposed change belongs to. | Use this guide to determine to which category your proposed change belongs to. | ||
| Line 27: | Line 27: | ||
== 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. --> | <!-- 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. --> | ||
The Modularity Working Group would like to propose using the modular infrastructure for creating and delivering the Fedora Server Edition for Fedora 27. While we are still working through some of the kinks leading up to the release of Fedora 26, we believe that the changes to the infrastructure and technology implementations will be available with sufficient time to harden the components in time for the 27 release. | The Modularity Working Group, Factory 2.0, Base Runtime, and Server Working Group would like to propose using the modular infrastructure for creating and delivering the Fedora Server Edition for Fedora 27. While we are still working through some of the kinks leading up to the release of Fedora 26, we believe that the changes to the infrastructure and technology implementations will be available with sufficient time to harden the components in time for the 27 release. | ||
== Owner == | == Owner == | ||
| Line 38: | Line 37: | ||
<!-- 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: langdon@fedoraproject.org | * Email: langdon@fedoraproject.org | ||
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->[mailto:sclark@fedoraproject.org Simon Clark] ([[User:sclark|sclark]]) | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | ||
| Line 57: | Line 56: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1474931 #1474931] | ||
== 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 modularity effort is fairly well known and significantly more information may be found on the [ | The modularity effort is fairly well known and significantly more information may be found on the [https://docs.pagure.org/modularity/ Modularity Website] or the [https://www.youtube.com/channel/UC4O8G9SZwqtkIAuKcT8-JpQ YouTube Channel]. In short, modularity is attempting to disconnect the lifecycle of applications from 1) each other 2) the operating system while still maintaining the ease of use of a typical Linux Distro. | ||
This change proposal is to | This change proposal is to promote the work done in the Boltron Release ([https://docs.pagure.org/modularity/prototype/boltron.html preview container image] in advance of the F26 release) to Fedora mainline through the Fedora Server Edition. We will also be working with the community to complete the available content for Fedora Server Edition as modules. | ||
Other edition and spins will not change at this point; users who want to create a Fedora server (as opposed to capital-S Fedora Server) without Modularity can use one of these other spins, including the Fedora Cloud Base image, or else use the "everything netinst". | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 73: | Line 74: | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: | ||
** The Modularity WG, Factory 2.0, Base Runtime, and Server WG teams all have contributions to this effort. The work that each team is doing is significant and wide ranging. We are hoping to: | ** The Modularity WG, Factory 2.0, Base Runtime, and Server WG teams all have contributions to this effort. The work that each team is doing is significant and wide ranging. We are hoping to: | ||
*** collect and incorporate feedback in to the system management experience of using modules (through dnf) | *** collect and incorporate feedback in to the system management experience of using modules (through dnf) | ||
*** modularize a significant amount of the content available for Fedora Server | *** modularize a significant amount of the content available for Fedora Server (focusing on current Server roles) | ||
*** define tools and best practices for implementing modules and keeping them up to date | *** define tools and best practices for implementing modules and keeping them up to date | ||
* Other developers: | * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
** Packagers are already working on modularizing applications; | |||
** | ** the Modularity WG will provide like to support additional package maintainers in modularizing their applications | ||
* Release engineering: | * Release engineering: | ||
** [[ | ** See [[Changes/ModularRelease]]. | ||
* Policies and guidelines: | ** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: | ||
*** This change replaces the Fedora 26 Server release-blocking deliverables with exactly the same things (DVDs and netinst images) but delivered via Modularity instead of the traditional process. | |||
** Although we want to enable changes to module lifecycles over time, it is worth noting that this Change Proposal does NOT change the normal 13 month commitment for anything in the release. | |||
* Policies and guidelines: | |||
** New guidelines are required, they are currently in Draft state and we will be collecting feedback to them during the F26 lifecycle for ratification prior to F27. | |||
*** [[Fedora_Packaging_Guidelines_for_Modules]] | |||
*** [[Container:Guidelines]] | |||
** At this point there are no changes expected to existing guidelines | |||
* Trademark approval: N/A (not needed for this Change) | * Trademark approval: N/A (not needed for this Change) | ||
| Line 98: | Line 103: | ||
== Upgrade/compatibility impact == | == 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? --> | <!-- 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? --> | ||
* We are still gathering requirements and evaluating the feasibility of in-place upgrades from prior versions of Fedora. If upgrading from existing Fedora Server to the new modular Server is not reasonably obtainable, we propose that on upgrade, existing Fedora Server installations become generic non-Edition systems | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES | <!-- REQUIRED FOR SYSTEM WIDE CHANGES | ||
N/A (not a System Wide Change) | N/A (not a System Wide Change) | ||
--> | |||
== How To Test == | == How To Test == | ||
| Line 117: | Line 125: | ||
--> | --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES | <!-- REQUIRED FOR SYSTEM WIDE CHANGES | ||
N/A (not a System Wide Change) | N/A (not a System Wide Change) | ||
--> | |||
Normal system operation (sort of). We are in the process of documenting a full user test script based on the Boltron Preview. We will be working directly with QE to work through test days during the F26 lifecycle and will prepare testing requests for post-f27 launch. A significant part of this work is around improving automated testing. | |||
Tests/comments/feedback should be filed in the [https://pagure.io/modularity/issues Modularity Pagure repo] for comments about modularity. Issues with individual modules should be filed with the appropriate component in bugzilla (or as specified by the Factory 2 team). | |||
== User Experience == | == User Experience == | ||
<!-- 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) | N/A (not a System Wide Change) | ||
--> | |||
We expect the default user experience to be transparent with interactions that are non-standard being an optional experience. The documentation regarding the usage of the new experiences including walkthroughs and demos will be found in the [https://docs.pagure.org/modularity Modularity docs]. | |||
== Dependencies == | == Dependencies == | ||
| Line 129: | Line 144: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
N/A | N/A | ||
== Contingency Plan == | == Contingency Plan == | ||
<!-- 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?) | * Contingency mechanism: (What to do? Who will do it?): Normal rpm/compose build process (vs modular build process) <!-- 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. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: | * Contingency deadline: Needs discussion <!-- 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? Yes <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
* Blocks product? | * Blocks product? Server Edition <!-- Applicable for Changes that blocks specific product release/Fedora.next --> | ||
== Documentation == | == Documentation == | ||
| Line 145: | Line 160: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
[https://docs.pagure.org/modularity Modularity docs]. | |||
== Release Notes == | == Release Notes == | ||
| Line 154: | Line 169: | ||
--> | --> | ||
[[Category: | [[Category:ChangeAcceptedF27]] | ||
<!-- 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 --> | ||
| Line 161: | Line 176: | ||
<!-- Select proper category, default is Self Contained Change --> | <!-- Select proper category, default is Self Contained Change --> | ||
[[Category:SelfContainedChange]] | <!-- [[Category:SelfContainedChange]] --> | ||
[[Category:SystemWideChange]] | |||
Latest revision as of 19:23, 3 November 2017
Modular Server
Summary
The Modularity Working Group, Factory 2.0, Base Runtime, and Server Working Group would like to propose using the modular infrastructure for creating and delivering the Fedora Server Edition for Fedora 27. While we are still working through some of the kinks leading up to the release of Fedora 26, we believe that the changes to the infrastructure and technology implementations will be available with sufficient time to harden the components in time for the 27 release.
Owner
- Name: Langdon White
- Email: langdon@fedoraproject.org
- Release notes owner: Simon Clark (sclark)
- Edition: Server Edition
- Responsible WG: Modularity WG & Server WG
Current status
Detailed Description
The modularity effort is fairly well known and significantly more information may be found on the Modularity Website or the YouTube Channel. In short, modularity is attempting to disconnect the lifecycle of applications from 1) each other 2) the operating system while still maintaining the ease of use of a typical Linux Distro.
This change proposal is to promote the work done in the Boltron Release (preview container image in advance of the F26 release) to Fedora mainline through the Fedora Server Edition. We will also be working with the community to complete the available content for Fedora Server Edition as modules.
Other edition and spins will not change at this point; users who want to create a Fedora server (as opposed to capital-S Fedora Server) without Modularity can use one of these other spins, including the Fedora Cloud Base image, or else use the "everything netinst".
Benefit to Fedora
Scoping the question to this Change Proposal, the benefit to Fedora is to release the multi-lifecycle model for real users. We can prove that most day-to-day operations will be unchanged and that users can opt in to more advanced use cases.
Scope
- Proposal owners:
- The Modularity WG, Factory 2.0, Base Runtime, and Server WG teams all have contributions to this effort. The work that each team is doing is significant and wide ranging. We are hoping to:
- collect and incorporate feedback in to the system management experience of using modules (through dnf)
- modularize a significant amount of the content available for Fedora Server (focusing on current Server roles)
- define tools and best practices for implementing modules and keeping them up to date
- The Modularity WG, Factory 2.0, Base Runtime, and Server WG teams all have contributions to this effort. The work that each team is doing is significant and wide ranging. We are hoping to:
- Other developers:
- Packagers are already working on modularizing applications;
- the Modularity WG will provide like to support additional package maintainers in modularizing their applications
- Release engineering:
- List of deliverables:
- This change replaces the Fedora 26 Server release-blocking deliverables with exactly the same things (DVDs and netinst images) but delivered via Modularity instead of the traditional process.
- Although we want to enable changes to module lifecycles over time, it is worth noting that this Change Proposal does NOT change the normal 13 month commitment for anything in the release.
- List of deliverables:
- Policies and guidelines:
- New guidelines are required, they are currently in Draft state and we will be collecting feedback to them during the F26 lifecycle for ratification prior to F27.
- At this point there are no changes expected to existing guidelines
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
- We are still gathering requirements and evaluating the feasibility of in-place upgrades from prior versions of Fedora. If upgrading from existing Fedora Server to the new modular Server is not reasonably obtainable, we propose that on upgrade, existing Fedora Server installations become generic non-Edition systems
How To Test
Normal system operation (sort of). We are in the process of documenting a full user test script based on the Boltron Preview. We will be working directly with QE to work through test days during the F26 lifecycle and will prepare testing requests for post-f27 launch. A significant part of this work is around improving automated testing.
Tests/comments/feedback should be filed in the Modularity Pagure repo for comments about modularity. Issues with individual modules should be filed with the appropriate component in bugzilla (or as specified by the Factory 2 team).
User Experience
We expect the default user experience to be transparent with interactions that are non-standard being an optional experience. The documentation regarding the usage of the new experiences including walkthroughs and demos will be found in the Modularity docs.
Dependencies
N/A
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?): Normal rpm/compose build process (vs modular build process)
- Contingency deadline: Needs discussion
- Blocks release? Yes
- Blocks product? Server Edition