From Fedora Project Wiki
m
Line 11: Line 11:
 
Towards accomplishing the second goal, we set out to study existing workflows and hypothesize what non-automated modularity workflows would entail.
 
Towards accomplishing the second goal, we set out to study existing workflows and hypothesize what non-automated modularity workflows would entail.
  
== See also ==
+
== Infrastructure TOC ==
  
* [[Modularity/Architecture/Infra/Life_of_a_package_update|Life of a package update]]
+
# [[Modularity/Architecture/Infra/Life_of_a_package_update|Life of a package update]]
* [[Modularity/Architecture/Infra/Life_of_a_module_update|Life of a module update]]
+
# [[Modularity/Architecture/Infra/Life_of_a_module_update|Life of a module update]]
* [[Modularity/Architecture/Infra/Infrastructure_services_proposal|Infrastructure services proposal]]
+
# [[Modularity/Architecture/Infra/Infrastructure_services_proposal|Infrastructure services proposal]]
* [[Modularity/Architecture/Infra/Two_approaches_to_the_orchestrator|Two approaches to the orchestrator]]
+
# [[Modularity/Architecture/Infra/Two_approaches_to_the_orchestrator|Two approaches to the orchestrator]]
* [[Modularity/Architecture/Infra/Open_questions_and_notes|Open questions and notes]]
+
# [[Modularity/Architecture/Infra/Open_questions_and_notes|Open questions and notes]]
* [[Modularity/Developer_Notes|Developer Notes]] — the current state of development
+
# [[Modularity/Developer_Notes|Developer Notes]] — the current state of development
  
 
[[Category:Modularity]]
 
[[Category:Modularity]]

Revision as of 14:05, 9 September 2016

One part of the so-called “Factory 2.0”

The goal of this document is to describe a high level plan for what kinds of systems will need to be modified and introduced to Fedora Infrastructure to support building, maintaining, and shipping modular things.

Note: There are open questions still which can impact this plan.

Background

We know from the originally nebulous discussions that led to the formation of a modularity initiative in Fedora that we were going to create a new framework for building and composing the distribution, one which could have negative side-effects on our existing efforts if we weren’t careful. “Modularity will be very powerful. It will give us enough power to shoot ourselves in the foot.” We’re talking about allowing the creation of combinations of components with independent lifecycles. There’s the possibility of a combinatorial explosion in there that we’ll need to contain. We’ll do that in part by vigorously limiting the number of supported modules with policy, to be taken up in another document, and by providing infrastructure automation to reduce the amount of manual work required.

Towards accomplishing the second goal, we set out to study existing workflows and hypothesize what non-automated modularity workflows would entail.

Infrastructure TOC

  1. Life of a package update
  2. Life of a module update
  3. Infrastructure services proposal
  4. Two approaches to the orchestrator
  5. Open questions and notes
  6. Developer Notes — the current state of development