From Fedora Project Wiki
< Changes
No edit summary |
(add a note about making it possible to run non-root GUI) |
||
| Line 66: | Line 66: | ||
* Anaconda addons have stable API to work with. | * Anaconda addons have stable API to work with. | ||
* Users can create their own UI or even UI less installation. | * Users can create their own UI or even UI less installation. | ||
* enables running the UI as a non-root user (a requirement for running Anaconda GUI natively on Wayland in the future) | |||
* Anaconda modules can be enabled and disabled or even not present in the installation environment. | * Anaconda modules can be enabled and disabled or even not present in the installation environment. | ||
* Better test-ability of Anaconda. | * Better test-ability of Anaconda. | ||
<!-- 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?--> | <!-- 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?--> | ||
Revision as of 14:01, 9 January 2018
Anaconda modularization
Summary
Anaconda installer will be split into several modules that will communicate over DBus using stable API.
Owner
- Name: Jiří Konečný
- Email: jkonecny@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 28
- Last updated: 2018-01-09
- 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.
- enables running the UI as a non-root user (a requirement for running Anaconda GUI natively on Wayland in the future)
- Anaconda modules can be enabled and disabled or even not present in the installation environment.
- Better test-ability of Anaconda.
Scope
- Proposal owners:
- Split Anaconda to modules with DBus API.
- Old UI must be modified to use new DBus API.
- Other developers:
- Thanks to the nature of how addons work right now, we need a cooperation from the Anaconda addon developers.
- Release engineering: #7240
- List of deliverables: N/A (not a System Wide Change)
- 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
User experience should be consistent with the older releases.
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: Fallback to the old (non-modular) solution will be still available during development.
- Contingency deadline: Final freeze
- Blocks release? No
Documentation
https://rhinstaller.wordpress.com/2017/10/09/anaconda-modularisation/
Most of the articles here: https://rhinstaller.wordpress.com
Release Notes
TODO