m (Phatina moved page Changes/Storaged to Changes/Replace UDisks2 by Storaged) |
No edit summary |
||
Line 1: | Line 1: | ||
= Replace UDisks2 by Storaged = | |||
== Summary == | == Summary == | ||
[http://storaged.org/ Storaged] extends [https://www.freedesktop.org/wiki/Software/udisks/ UDisks2] API by exporting several enterprise features (in form of plugins), such as LVM2 and iSCSI. This project is a drop-in replacement for UDisks2, either from D-Bus or binary point of view. The main motivation of this change is to provide the unified D-Bus API for all the clients who are willing to manage LVM2, iSCSI, Btrfs, BCache, LSM and ZRam. | |||
Storaged extends UDisks2 API by exporting several enterprise features ( | |||
== Owner == | == Owner == | ||
Line 32: | Line 9: | ||
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:phatina| Peter Hatina]] | * Name: [[User:phatina | Peter Hatina]], [[User:tsmetana | Tomáš Smetana]] | ||
* Email: phatina redhat com | * Email: phatina redhat com, tsmetana redhat com | ||
* Release notes owner: | * Release notes owner: | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
Line 57: | Line 34: | ||
== Detailed Description == | == Detailed Description == | ||
Aim of Storaged is to provide unified higher level management interface for various clients who are willing to query and manage storage bits of the system. We plan to replace UDisks2 by Storaged, since the Storaged itself is the fork of UDisks2 and these 2 projects in its core haven't diverged so much (Storaged got some improvements which popped up while using it). | Aim of Storaged is to provide unified higher level management interface for various clients who are willing to query and manage storage bits of the system. We plan to replace UDisks2 by Storaged, since the Storaged itself is the fork of UDisks2 and these 2 projects in its core haven't diverged so much (Storaged got some improvements which popped up while using it). | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
The drop-in replacement is beneficial for Fedora because currently, there are 2 similar projects (one derived from the other). Since, Storaged can export the same API as UDisks2 does, but with several enterprise extensions, it is natural to replace one daemon with the extended one | The drop-in replacement is beneficial for Fedora because currently, there are 2 similar projects (one derived from the other). Since, Storaged can export the same API as UDisks2 does, but with several enterprise extensions, it is natural to replace one daemon with the extended one: | ||
* we do not need to have very similar services running at the same time; | |||
* one provides only a subset of operations when compared to the other service | |||
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | ||
Line 87: | Line 63: | ||
== Upgrade/compatibility impact == | == Upgrade/compatibility impact == | ||
<!-- 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? --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Since, Storaged should replace UDisks2 in 1:1 manner, there is no additional change required. | Since, Storaged should replace UDisks2 in 1:1 manner, there is no additional change required. | ||
== How To Test == | == How To Test == | ||
Install Storaged which replaces UDisks2 and verify that: | Install Storaged which replaces UDisks2 and verify that: | ||
* GNOME Disks works properly | * GNOME Disks works properly | ||
* GVFS works as expected (notifications of new devices, mouting, ...) | * GVFS works as expected (notifications of new devices, mouting, ...) | ||
== User Experience == | == User Experience == | ||
User will not notice any | User will '''not notice''' any changes comming from the switch UDisks2 to Storaged. | ||
== Dependencies == | == Dependencies == | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | ||
The main consumer of Storaged is Cockpit | The main consumer of Storaged is [http://cockpit-project.org/ Cockpit] and [https://github.com/rhinstaller/blivet Blivet]. We have an agreement with the developers of the respective projects that we will sync when the Storaged replaces UDisks2. | ||
== 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: (What to do? Who will do it?) | * Contingency mechanism: (What to do? Who will do it?) | ||
Line 133: | Line 90: | ||
== Documentation == | == Documentation == | ||
<!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | <!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | ||
Documentation for Storaged can be found at [http://storaged.org/ Storaged Documentation] | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
N/A (not a System Wide Change) | <!-- N/A (not a System Wide Change) --> | ||
== Release Notes == | == Release Notes == |
Revision as of 11:18, 13 April 2016
Replace UDisks2 by Storaged
Summary
Storaged extends UDisks2 API by exporting several enterprise features (in form of plugins), such as LVM2 and iSCSI. This project is a drop-in replacement for UDisks2, either from D-Bus or binary point of view. The main motivation of this change is to provide the unified D-Bus API for all the clients who are willing to manage LVM2, iSCSI, Btrfs, BCache, LSM and ZRam.
Owner
- Name: Peter Hatina, Tomáš Smetana
- Email: phatina redhat com, tsmetana redhat com
- Release notes owner:
Current status
- Targeted release: Fedora 25
- Last updated: 2016-04-13
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
Aim of Storaged is to provide unified higher level management interface for various clients who are willing to query and manage storage bits of the system. We plan to replace UDisks2 by Storaged, since the Storaged itself is the fork of UDisks2 and these 2 projects in its core haven't diverged so much (Storaged got some improvements which popped up while using it).
Benefit to Fedora
The drop-in replacement is beneficial for Fedora because currently, there are 2 similar projects (one derived from the other). Since, Storaged can export the same API as UDisks2 does, but with several enterprise extensions, it is natural to replace one daemon with the extended one:
- we do not need to have very similar services running at the same time;
- one provides only a subset of operations when compared to the other service
Scope
- Proposal owners:
- Other developers: N/A (not a System Wide Change)
- Release engineering: N/A (not a System Wide Change)
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
Since, Storaged should replace UDisks2 in 1:1 manner, there is no additional change required.
How To Test
Install Storaged which replaces UDisks2 and verify that:
- GNOME Disks works properly
- GVFS works as expected (notifications of new devices, mouting, ...)
User Experience
User will not notice any changes comming from the switch UDisks2 to Storaged.
Dependencies
The main consumer of Storaged is Cockpit and Blivet. We have an agreement with the developers of the respective projects that we will sync when the Storaged replaces UDisks2.
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
Documentation for Storaged can be found at Storaged Documentation