From Fedora Project Wiki
< Changes
(Move to Fedora 22, see tracking bug for more details) |
(Change accepted on 2015-01-28 FESCo meeting) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 30: | Line 30: | ||
This should link to your home wiki page so we know who you are. | This should link to your home wiki page so we know who you are. | ||
--> | --> | ||
* Name: [[User:kevin| Kevin Fenzi]] and [[User:Tuanta| Truong Anh Tuan]] | * Name: [[User:sgallagh| Stephen Gallagher]], [[User:kevin| Kevin Fenzi]] and [[User:Tuanta| Truong Anh Tuan]] | ||
<!-- 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: server@lists.fedoraproject.org | * Email: server@lists.fedoraproject.org | ||
| Line 43: | Line 43: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/22 | Fedora 22 ]] | * Targeted release: [[Releases/22 | Fedora 22 ]] | ||
* Last updated: | * Last updated: 2015-01-20 | ||
<!-- 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 | ||
Bugzilla states meaning as usual: | Bugzilla states meaning as usual: | ||
| Line 81: | Line 81: | ||
* Release engineering: | * Release engineering: | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. --> | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. --> | ||
N/A | |||
* Policies and guidelines: | * Policies and guidelines: | ||
| Line 90: | Line 90: | ||
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | ||
This functionality will be designed not to interfere with existing deployments of postgresql. | |||
== How To Test == | == How To Test == | ||
| Line 117: | Line 117: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Individual parts of this Change may or may not be completed in time for Fedora | Individual parts of this Change may or may not be completed in time for Fedora 22. This may include a Cockpit graphical UI tool and an OpenLMI remote management tool. | ||
== Contingency Plan == | == Contingency Plan == | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: Do not ship the Database Server role in | * Contingency mechanism: Do not ship the Database Server role in Fedora 22. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: Beta | * Contingency deadline: Beta | ||
| Line 143: | Line 142: | ||
--> | --> | ||
[[Category: | [[Category:ChangeAcceptedF22]] | ||
<!-- 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:27, 29 January 2015
Database Server Role
Summary
The Fedora Server Product will provide a standard deployment mechanism for a Linux Database Server (powered by the postgresql project).
Owner
- Name: Stephen Gallagher, Kevin Fenzi and Truong Anh Tuan
- Email: server@lists.fedoraproject.org
- Release notes owner: Petr Bokoc pbokoc at redhat dot com
- Product: Server
- Responsible WG: Server WG
Current status
Detailed Description
The Fedora Server Product will be shipped with a role-deployment mechanism. One such role will be to act as a primary or replica Database Server for the Linux machines in the network.
This will be implemented by taking advantage of the postgresql project, packaging it up within the Server Role Framework and enabling it to be deployed through the mechanisms described in the Framework for Server Role Deployment Change Proposal.
Note that this role is a secondary target of the Server Working group.
Benefit to Fedora
The major advantage to Fedora is a vast simplification in the setup and deployment of a managed Linux network. With the Database Server Role, the user will be asked to provide a few very basic pieces of information about their network and the role deployment tools will do the rest of the work for them. With the Database Server in place, users will have a ready to use datastore without lengthy configuration.
Scope
- Proposal owners:
- Postgresql server and related tools need to be packaged appropriately for use with the Server Role Infrastructure.
- A D-BUS API plugin needs to be written and tested to support deployment and monitoring of the Database server.
- Other developers:
- None
- Release engineering:
N/A
- Policies and guidelines:
- Packaging guidelines for this Change should be inherited from the Framework for Server Role Deployment Change Proposal.
Upgrade/compatibility impact
This functionality will be designed not to interfere with existing deployments of postgresql.
How To Test
- What special hardware / data / etc. is needed (if any)?
- This Role should work on any Fedora Server installation.
- How do I prepare my system to test this change? What packages need to be installed, config files edited, etc.?
- Testing should be performed on a clean installation of Fedora Server, both through kickstart and interactive install.
- What specific actions do I perform to check that the change is working like it's supposed to?
- There will be a role-deployment tool provided, as well as possibly a Cockpit module, to deploy the Database Server Role. These tools should be run to do the initial deployment. Subsequent testing should be performed by remotely accessing the database.
- What are the expected results of those actions?
- A usable database server for whatever database application needs you have.
User Experience
Users will now be provided with an easy way to deploy a Database Server for their Linux environment. If they are using Cockpit, this will be presented to them with a simple GUI.
Dependencies
Individual parts of this Change may or may not be completed in time for Fedora 22. This may include a Cockpit graphical UI tool and an OpenLMI remote management tool.
Contingency Plan
- Contingency mechanism: Do not ship the Database Server role in Fedora 22.
- Contingency deadline: Beta
- Blocks release? No
- Blocks product? No
Documentation
Documentation has not yet been written, but we will be coordinating with the Fedora Documentation team.