From Fedora Project Wiki

< Features

Revision as of 15:15, 5 November 2010 by Jreznik (talk | contribs) (FMCI and Matahari)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.


Feature Name

Matahari based Fedora Management and Configuration Infrastructure (FMCI).

Summary

The goal of FMCI is to build a high level management and configuration interface on top of low level system ones. This low level interface is covered mostly by Matahari project. We are going to provide help to this project, so we can share as much code as possible. FMCI aims on local systems (DBus and PolicyKit), on the contrary Matahari on remote systems (QMF) usually hosted in virtualized environments (cloud). But on this level - there's quite a big overlap.

On top of high level Fedora interfaces we'd like to see user interfaces - probably both GUI and TUI, even some CLI tools would be very nice. This interfaces should be reusable by other tools too.

Owner

  • Jaroslav Reznik (jreznik AT redhat DOT com)
  • Roman Rakus (rrakus AT redhat DOT com)
  • Radek Novacek (rnovacek AT redhat DOT com)

Current status

  • Targeted release: Fedora 40
  • Last updated: 2010-11-05
  • Percentage of completion: 5%

Current status:

  • Gathering informations/data from the community.
  • Planning with Matahari guys.
  • Date interface
    • completed with Chrony support implemented (100%)
    • system-config-date port (WIP)
  • Boot interface (WIP)


Detailed Description

TBD.

Scope

GUI system configuration tools are affected by this change - we should port them to the new DBus/Polkit system configuration architecture. But the old GUI tools should work together with the new stack.


How To Test

Unit tests are part of the project.

User Experience

TBD.

Dependencies

No dependencies - independent project.

Contingency Plan

This is new project - there's no contingency plan needed.

Documentation

Release Notes

Comments and Discussion