From Fedora Project Wiki
(FMCI and Matahari)
 
(3 intermediate revisions by 2 users not shown)
Line 5: Line 5:


= Feature Name =
= Feature Name =
Fedora Management and Configuration Infrastructure (FMCI).
Matahari based Fedora Management and Configuration Infrastructure (FMCI).


== Summary ==
== Summary ==
The current Fedora management and configuration tools state is not very good in comparison with other distributions.
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.
Fedora includes several system configuration tools (system-config-*) - .  


This should change with FMCI.
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.
 
This effort includes:
* consistent high level management and configuration interface exposed over system message bus (DBus),  
* proper documentation of existing interfaces exposed over system message bus,
* and user interfaces using this/these interface(s).


== Owner ==
== Owner ==
Line 25: Line 19:
== Current status ==
== Current status ==
* Targeted release: [[Releases/{{FedoraVersion||next}} | {{FedoraVersion|long|next}} ]]  
* Targeted release: [[Releases/{{FedoraVersion||next}} | {{FedoraVersion|long|next}} ]]  
* Last updated: 2010-03-22
* Last updated: 2010-11-05
* Percentage of completion: 5% (planning stage)
* Percentage of completion: 5%


Current status:
Current status:
* Waiting for Fedorahosted.org
* 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)
 
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->


Line 39: Line 40:
== Scope ==
== Scope ==


TBD.
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.  
 
<!-- What work do the 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 the 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?-->


== How To Test ==
== How To Test ==


TBD.
Unit tests are part of the project.
 


== User Experience ==
== User Experience ==
Line 54: Line 54:
== Dependencies ==
== Dependencies ==


TBD.
No dependencies - independent project.


== Contingency Plan ==
== Contingency Plan ==
Line 61: Line 61:
== Documentation ==
== Documentation ==


TBD.
* [https://fedorahosted.org/fmci/wiki/ExistingInterfaces Implemented interfaces in Fedora]
* [https://fedorahosted.org/fmci/wiki/OngoingInterfaces Work in progress]


== Release Notes ==
== Release Notes ==

Latest revision as of 15:15, 5 November 2010


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