From Fedora Project Wiki

Revision as of 16:58, 3 January 2018 by Jkonecny (talk | contribs) (First version)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Anaconda modularization

Summary

Anaconda installer will be split into several modules that will communicate over DBus with stable API.

Owner

Current status

  • Targeted release: Fedora 28
  • Last updated: 2018-01-03
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Anaconda will be split into several modules that will communicate over DBus. The goal is to introduce a stable way to interact with Anaconda to support its customization, extensibility and testability. It will be easier to monitor the installation, maintain an install class or an addon, drop some modules or provide your own UI.

Benefit to Fedora

  • Anaconda addons have stable API to work with.
  • Users can create their own UI or even UI less installation.
  • Anaconda modules can be enabled and disabled or even not present in the installation environment.
  • Better test-ability of Anaconda -- more stable versions.


Scope

  • Proposal owners:
    • Split Anaconda to modules with DBus API.
    • Old UI must be rewritten to use new DBus API.
  • Other developers:
    • Thanks to the nature of how addons work right now we need cooperation during the transition period of addon developers.
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes