From Fedora Project Wiki
(Change Proposal ready for 2014-04-23 FESCo meeting (#1290))
(Deferred to F22)
 
(3 intermediate revisions by 2 users not shown)
Line 33: Line 33:
-->
-->
* Name: [[User:Sgallagh| Stephen Gallagher]]
* Name: [[User:Sgallagh| Stephen Gallagher]]
** Email: sgallagh@redhat.com
* Email: sgallagh@redhat.com
<!-- 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. -->
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
* Release notes owner: [[User:Pbokoc| Petr Bokoc]] pbokoc at redhat dot com
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
Line 44: Line 44:


== Current status ==
== Current status ==
* Targeted release: [[Releases/21 | Fedora 21 ]]  
* Targeted release: [[Releases/22 | Fedora 22 ]]  
* Last updated: 2014-04-08
* Last updated: 2014-04-08
<!-- 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 54: Line 54:
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: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1091300 #1091300]


== Detailed Description ==
== Detailed Description ==
Line 147: Line 147:
-->
-->


[[Category:ChangeReadyForFesco]]
[[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 09:21, 29 August 2014


Anaconda Support for Server Roles

Summary

The Fedora Server SIG will develop a plug-in for Anaconda to support the deployment of Fedora Server Roles in kickstart files.

Owner

  • Name: Stephen Gallagher
  • Email: sgallagh@redhat.com
  • Release notes owner: Petr Bokoc pbokoc at redhat dot com
  • Product: Fedora Server
  • Responsible WG: Server WG

Current status

Detailed Description

Deploying Server Roles during installation will require a higher level of access to the installed system than %post can provide. The Fedora Server SIG will develop an Anaconda plug-in that will add kickstart directives to deploy available server roles.

Benefit to Fedora

This feature - as an add-on to the Fedora Server Role capabilities - will vastly simplify the setup of standard infrastructure components. As a result, it will become easier for administrators (both junior and senior) to rapidly deploy best-practice services for their networks.

Scope

We will need to develop an Anaconda plugin to process kickstart directives. A GUI spoke is an explicit non-goal for Fedora 21; it may be added in the future.

  • Proposal owners:

Development work of the Anaconda plug-in.

  • Release engineering:
    • It will be necessary to include this plug-in into the installer image.
  • Policies and guidelines: N/A

Upgrade/compatibility impact

This will be relevant only to new system installations.

How To Test

Tests will need to be written for the unattended installation of any supported Server Roles.

Such tests should be automatable by creating stock kickstart files and verifying that the post-install state is appropriate.

User Experience

Users of kickstart will have new capabilities available to them for setting up best-practice infrastructure services.

Dependencies

Framework for Server Role deployment

Contingency Plan

  • Contingency mechanism: Ship without kickstart support in Fedora 21 and defer to next release
  • Contingency deadline: Beta Freeze
  • Blocks release? No
  • Blocks product? Fedora Server (highly-desired, but not blocking)

Documentation

None yet.

Release Notes