< Changes
No edit summary |
(Postponed to F23 as requested by change owner) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 22: | Line 22: | ||
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | ||
= | = Domain Controller Set Up Through Cockpit <!-- The name of your change proposal --> = | ||
== Summary == | == Summary == | ||
| Line 36: | Line 35: | ||
* Name: [[User:sgallagh| Stephen Gallagher]] | * Name: [[User:sgallagh| Stephen Gallagher]] | ||
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | ||
* Email: sgallagh@redhat.com | * Email: sgallagh@redhat.com | ||
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
| Line 47: | Line 46: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/ | * Targeted release: [[Releases/23 | Fedora 23 ]] | ||
* Last updated: 2015-01-19 | * Last updated: 2015-01-19 | ||
<!-- 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 57: | Line 56: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1191529 #1191529] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 144: | Line 143: | ||
--> | --> | ||
[[Category: | [[Category:ChangePageIncomplete]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 15:21, 18 February 2015
Domain Controller Set Up Through Cockpit
Summary
With Fedora 21, the rolekit project now provides a public D-BUS interface for creating a Domain Controller based on the FreeIPA project. This Change will track adding this capability to the Cockpit management console of Fedora Server.
Owner
- Name: Stephen Gallagher
- Email: sgallagh@redhat.com
- Release notes owner:
Current status
Detailed Description
Providing users with a simple graphical user interface to set up a FreeIPA Domain Controller will provide a fast way to bootstrap an enterprise-grade Linux environment. Once the Domain Controller is made available, it becomes easy to manage single-sign-on between systems (and Cockpit instances), control user authentication and authorization centrally and manage DNS entries (among other things).
Benefit to Fedora
To make Fedora Server more appealing to the novice and intermediate administrator, adding this functionality to Cockpit will significantly reduce the barrier to entry to creating a secure domain based on best-practice policies.
Scope
- Proposal owners:
The Cockpit user experience needs to be written and added to that upstream project. It needs to be connected to the local rolekit daemon.
- 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
N/A (not a System Wide Change)
How To Test
N/A (not a System Wide Change)
User Experience
This will provide a new graphical experience for setting up a domain controller. This will be reflected in a new module within the Cockpit management console.
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
UXD design: https://raw.githubusercontent.com/cockpit-project/cockpit-design/master/roles/roles.png
