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

Targeted release: Fedora 27
Last updated: 2017-11-03
Tracker bug: #1474931

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

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:

- See Changes/ModularRelease.

- 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)

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

Documentation

Modularity docs.

Release Notes

@@ 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?
 Use this guide to determine to which category your proposed change belongs to.
@@ Line 27: / Line 27: @@
 == 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. -->
+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 ==
@@ Line 33: / Line 34: @@
 This should link to your home wiki page so we know who you are.
 -->
-* Name: [[User:FASAcountName| Your Name]]
+* Name: [[User:langdon| Langdon White]]
 <!-- 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: <your email address so we can contact you, invite you to meetings, etc.>
+* 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)
 * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
 -->
-<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)
+<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) -->
-* Product:
+* Edition: Server Edition
-* Responsible WG:
+* Responsible WG: Modularity WG & Server WG
--->
 == Current status ==
-* Targeted release: [[Releases/<number> | Fedora <number> ]]
+* Targeted release: [[Releases/27 | Fedora 27 ]]
 * 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
@@ Line 56: / Line 56: @@
 CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 -->
-* Tracker bug: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1474931 #1474931]
 == 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 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 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 ==
+<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
+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.
-<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
 == 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?-->
+** 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
+* 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
-* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Release engineering:
-<!-- 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?-->
-* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engeneering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
+** See [[Changes/ModularRelease]].
-<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid 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 -->
-** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]:
-<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
+*** 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: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Policies and guidelines:
-<!-- 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. -->
+** 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)
@@ Line 90: / Line 103: @@
 == 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? -->
+* 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)
+ -->
 == How To Test ==
@@ Line 109: / Line 125: @@
 -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+<!-- REQUIRED FOR SYSTEM WIDE CHANGES
 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 ==
 <!-- 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)
+ -->
+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 ==
@@ Line 121: / Line 144: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
+N/A
 == 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.  -->
-* 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?): 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. -->
-* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* 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? -->
-* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Blocks release? Yes <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
+* Blocks product? Server Edition <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
 == Documentation ==
@@ Line 137: / Line 160: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
+[https://docs.pagure.org/modularity Modularity docs].
 == Release Notes ==
@@ Line 146: / Line 169: @@
 -->
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF27]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 153: / Line 176: @@
 <!-- Select proper category, default is Self Contained Change -->
-[[Category:SelfContainedChange]]
+<!-- [[Category:SelfContainedChange]] -->
-<!-- [[Category:SystemWideChange]] -->
+[[Category:SystemWideChange]]

Search

Changes/Modular Server: Difference between revisions