From Fedora Project Wiki
(list server WG as the change owner) |
(minor wording tweak) |
||
| Line 22: | Line 22: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/21 | Fedora 21 ]] | * Targeted release: [[Releases/21 | Fedora 21]] | ||
* Last updated: April 1, 2014 | * Last updated: April 1, 2014 | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
| Line 35: | Line 35: | ||
== Detailed Description == | == Detailed Description == | ||
A new D-Bus service will be made available, exposing available server roles, | A new D-Bus service will be made available, exposing available server roles, making it possible to deploy, configure and manage them. | ||
Revision as of 18:49, 1 April 2014
Framework for Server Role Deployment
Summary
A new D-Bus service, and associated command-line tools, to deploy and manage Server Roles.
Owner
- Name: Fedora Server Working Group
- Email: server AT lists DOT fedoraproject DOT org
- Release notes owner:
- Product: Server
- Responsible WG: Server
Current status
- Targeted release: Fedora 21
- Last updated: April 1, 2014
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
A new D-Bus service will be made available, exposing available server roles, making it possible to deploy, configure and manage them.
Benefit to Fedora
Scope
- Proposal owners:
- Other developers: N/A (not a System Wide Change)
- Release engineering: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
Upgrade/compatibility impact
This is new functionality, so no impact on upgrades from previous releases.
The newly introduced user-facing API is intended to be long-term, available also in future releases of Fedora without breaking applications that use it as documented. (Note that the same promise is not given for the API used to implement the server roles.)
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)