From Fedora Project Wiki
mNo edit summary
 
(15 intermediate revisions by 3 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 22: Line 22:


<!-- 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 -->
<!-- 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 -->
= Changes/Modular_Server_Preview <!-- The name of your change proposal --> =
= Modular Server Preview (Codename: Boltron!) <!-- The name of your change proposal --> =


== 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. -->
As we progress down the modularity path, we finally have enough content, architecture and understanding that we would like to release an edition of Fedora that is actually usable. However, as we aren't ready for production yet, we would like to do a "preview" release so that people can see it and try it but it doesn't actually take the place of a production edition. As such this Change Proposal requests that we set up a "Modular Server Edition" with some sort of flag that indicates that it is meant for experimentation and not real use. We plan to model the Server Edition in content and most use scenarios.   
As we progress down the modularity path, we finally have enough content, architecture and understanding that we would like to release a preview version of a Modular Fedora Server that is actually usable. However, as we aren't ready for production yet, we would like to do a "preview" release so that people can see it and try it but it doesn't actually take the place of a production edition. As such this Change Proposal requests that we set up a "Modular Server Edition" with some sort of flag that indicates that it is meant for experimentation and not real use. We plan to model the Server Edition in content and most use scenarios.   


== Owner ==
== Owner ==
Line 36: Line 36:
<!-- 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)
Brief discussion with jboyer seems to indicate that this is not required. However, am open to discussion.
Brief discussion with jboyer seems to indicate that this is not required. However, am open to discussion.
Line 57: Line 57:
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: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1419506 #1419506]


== Detailed Description ==
== Detailed Description ==
Line 76: Line 76:
* Other developers:  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* 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?-->
<!-- 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?-->
** We would like to enable Fedora Packagers to provide modules to this release of Modular Server.  
** A limited number of Fedora Packagers will help to provide modules and containers for this release of Modular Server. See [[Changes/ModuleBuildService]] for more details.
** We would further like to provide the ability for Fedora Packagers to provide containerized variants of their packages/modules


* Release engineering:  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering:  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
Line 83: Line 82:
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.-->
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.-->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: Numerous but largely aligned with the [https://kolinahr.fedorainfracloud.org/edit/57ff81347b76717eefcbc44b Server WG Logic Model] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: Numerous but largely aligned with the [https://kolinahr.fedorainfracloud.org/edit/57ff81347b76717eefcbc44b Server WG Logic Model] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
** Release engineering needs to create and deliver this new "edition." The Factory 2 team is largely responsible. [[User:Ralph|Threebean]] has been the primary point of contact thus far.
** Release engineering needs to create and deliver this new artifact. The Factory 2 team is largely responsible. [[User:Ralph|Threebean]] has been the primary point of contact thus far.


<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
** A beta edition delivering the Modular Server
** A preview release image delivering the Modular Server


* Policies and guidelines:  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Policies and guidelines:  <!-- 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. -->
<!-- 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 [[Fedora_Packaging_Guidelines_for_Modules|1]]] [[Container:Guidelines|2]]] are required, they are in beta state like the rest of this proposal. -->
** 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.
** New guidelines [[Fedora_Packaging_Guidelines_for_Modules]] and [[Container:Guidelines]] are required, they are in beta state like the rest of this proposal.
*** [[Fedora_Packaging_Guidelines_for_Modules]]
*** [[Fedora_Packaging_Guidelines_for_Modules]]
*** [[Container:Guidelines]]
*** [[Container:Guidelines]]
Line 106: Line 104:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
Arguably, this is not applicable as the delivery is for a beta version of an Edition. We do expect to have an upgrade path but it will be as risky as anything else in the beta.
Arguably, this is not applicable as the delivery is for a preview version of an Edition. We do expect to have an upgrade path but it will be as risky as anything else in the preview.


== How To Test ==
== How To Test ==
Line 124: Line 122:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
Normal system operation (sort of). We are delivering this Beta in order to get exactly this sort of feedback. We would like to hear from anyone experimenting with the beta about how it does or does not meet their expectations.  
Normal system operation (sort of). We are delivering this Preview in order to get exactly this sort of feedback. We would like to hear from anyone experimenting with the preview about how it does or does not meet their expectations.  


Feedback channel is not well determined. The team requests that the Change Wrangler make recommendations. Bugzilla is probably not appropriate but fedora-devel, modularity-wg pagure issues, modularity-wg meetings would all be viable choices.
Feedback channel is not well determined. The team requests that the Change Wrangler make recommendations. Bugzilla is probably not appropriate but fedora-devel, modularity-wg pagure issues, modularity-wg meetings would all be viable choices.
Line 137: Line 135:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
Although a System Wide Change, not applicable.
** [[Changes/ModuleBuildService]]
** [[Changes/ModularCompose]]
** [[Changes/BaseRuntime]]


== 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: Cancel release of the Modular Server Beta; decision to be made by Modularity WG, Factory-2, & BRT Leads.  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency mechanism: Cancel release of the Modular Server Preview; decision to be made by Modularity WG, Factory-2, & BRT Leads.  <!-- 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: Beta Freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency deadline: Beta Freeze. Picked arbitrarily, we can be flexible here but it is important to have a deadline. <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
** To lower disruption to other Fedora Editions we may want to intentionally delay this release to have "Deadline+1-week" for the complete F26 schedule  
** To lower disruption to other Fedora Editions we may want to intentionally delay this release to have "Deadline+1-week" for the complete F26 schedule  
<!-- 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? -->
Line 166: Line 166:




[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF26]]
<!-- 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 173: Line 173:


<!-- Select proper category, default is Self Contained Change -->
<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
<!-- [[Category:SelfContainedChange]] -->
<!-- [[Category:SystemWideChange]] -->
[[Category:SystemWideChange]]

Latest revision as of 14:16, 4 July 2017


Modular Server Preview (Codename: Boltron!)

Summary

As we progress down the modularity path, we finally have enough content, architecture and understanding that we would like to release a preview version of a Modular Fedora Server that is actually usable. However, as we aren't ready for production yet, we would like to do a "preview" release so that people can see it and try it but it doesn't actually take the place of a production edition. As such this Change Proposal requests that we set up a "Modular Server Edition" with some sort of flag that indicates that it is meant for experimentation and not real use. We plan to model the Server Edition in content and most use scenarios.

Owner

  • Edition: N/A but in collaboration with Server WG
  • Responsible WG: Modularity WG

Current status

Detailed Description

The modularity effort is fairly well known and significantly more information may be found on the wiki 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.

Benefit to Fedora

Scoping the question to this Change Proposal, the benefit to Fedora is 2-fold. First, distributing an early version of a usable example of Modularity will allow for feedback and exposure to a wider audience than the people closely following the project. Second, we will be able to exercise the release processes we have been changing to support Modularity and improve the Fedora Infrastructure.

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. However, as the release is being managed in a "preview channel" none of the changes, whether released on time or not, will impact any other aspect of Fedora. Also, while we have high hopes for the amount of content we plan to release, even a small percentage of that content being ready will be enough to help prove the concept and generate feedback.
  • Other developers:
    • A limited number of Fedora Packagers will help to provide modules and containers for this release of Modular Server. See Changes/ModuleBuildService for more details.
  • Release engineering:
    • A preview release image delivering the Modular Server
  • Policies and guidelines:
  • Trademark approval: N/A (not needed for this Change)
    • This is based on a Fedora Objective and, as a result, does not seem to require Trademark approval even though it will carry the Trademark

Upgrade/compatibility impact

Arguably, this is not applicable as the delivery is for a preview version of an Edition. We do expect to have an upgrade path but it will be as risky as anything else in the preview.

How To Test

Normal system operation (sort of). We are delivering this Preview in order to get exactly this sort of feedback. We would like to hear from anyone experimenting with the preview about how it does or does not meet their expectations.

Feedback channel is not well determined. The team requests that the Change Wrangler make recommendations. Bugzilla is probably not appropriate but fedora-devel, modularity-wg pagure issues, modularity-wg meetings would all be viable choices.

User Experience

See above.

Dependencies

Contingency Plan

  • Contingency mechanism: Cancel release of the Modular Server Preview; decision to be made by Modularity WG, Factory-2, & BRT Leads.
  • Contingency deadline: Beta Freeze. Picked arbitrarily, we can be flexible here but it is important to have a deadline.
    • To lower disruption to other Fedora Editions we may want to intentionally delay this release to have "Deadline+1-week" for the complete F26 schedule
  • Blocks release? No
  • Blocks product? No

Documentation

Release Notes

  • Content to come
Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/Modular_Server_Preview&oldid=496763"