From Fedora Project Wiki
< Changes
m (remove template warning) |
No edit summary |
||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 21: | Line 21: | ||
<!-- 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 --> | ||
= | = Stratis Storage = | ||
== Summary == | == Summary == | ||
| Line 31: | Line 31: | ||
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:grover| Andy Grover]] | * Name: [[User:grover| Andy Grover]], [[User:ignatenkobrain | Igor Gnatenko]] | ||
<!-- 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: agrover@redhat.com | * Email: agrover@redhat.com, ignatenkobrain@fedoraproject.org | ||
* Release notes | * Release notes ticket: [https://pagure.io/fedora-docs/release-notes/issue/74 #74]<!--- 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) | ||
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | ||
| 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: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1531488 #1531488] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 70: | Line 70: | ||
== Scope == | == Scope == | ||
* | * Change owner: Stratis is currently in-development, with a 0.5 release coming soon. COPR repo exists already (https://copr.fedorainfracloud.org/coprs/grover/stratis/) Additional work would be to adapt the existing packaging scripts to the new Rust library packaging support that is in F28. Early feedback in F28 will help us reach 1.0 for Fedora 29. Although there are clearly later opportunities for system-wide changes based on Stratis, this initial inclusion would be entirely self-contained. | ||
Although there are clearly later opportunities for system-wide changes based on Stratis, this initial inclusion would be entirely self-contained. | |||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
| Line 78: | Line 76: | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Release engineering: [https://pagure.io/releng/ | * Release engineering: [https://pagure.io/releng/issue/7198 #7198] <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES --> | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
| Line 98: | Line 96: | ||
== How To Test == | == How To Test == | ||
Until version 1.0, Stratis should not be used | Until version 1.0, Stratis should not be used on a system with valuable data. Stratis will not be well-integrated into the boot process, nor will placing root partition on it be possible. However, Fedora users and testers can try Stratis on non-primary disks, and put it through its paces to generate bug reports and feature requests that can guide Stratis development leading up to a stable release. | ||
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | ||
| Line 158: | Line 156: | ||
--> | --> | ||
[[Category: | [[Category:ChangeAcceptedF28]] | ||
<!-- 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 14:36, 2 March 2018
Stratis Storage
Summary
Add initial support for Stratis, a local storage management solution. This will allow initial testing and user feedback that will guide Stratis's development and stabilization.
Owner
- Name: Andy Grover, Igor Gnatenko
- Email: agrover@redhat.com, ignatenkobrain@fedoraproject.org
- Release notes ticket: #74
Current status
Detailed Description
Stratis is a local storage system akin to Btrfs, ZFS, and LVM. Its goal is to enable easier setup and management of disks and SSDs, as well as enabling the use of advanced storage features -- such as thin provisioning, snapshots, integrity, and a cache tier -- without requiring expert-level storage administration knowledge. Furthermore, Stratis includes monitoring and repair capabilities, and a programmatic API, for better integration with higher levels of system management software.
Benefit to Fedora
Stratis can benefit Fedora users by making it easier and less hassle to administer the system's storage devices. Making this easier is key to increasing the uptake of advanced storage features (listed above), which can further benefit the user in reduced administration headaches, increased reliability, and greater flexibility.
Down the road, integrating Stratis support into Anaconda and other management tools via its API could simplify the installation experience, and make a dnf upgrade-rollback feature much easier.
Scope
- Change owner: Stratis is currently in-development, with a 0.5 release coming soon. COPR repo exists already (https://copr.fedorainfracloud.org/coprs/grover/stratis/) Additional work would be to adapt the existing packaging scripts to the new Rust library packaging support that is in F28. Early feedback in F28 will help us reach 1.0 for Fedora 29. Although there are clearly later opportunities for system-wide changes based on Stratis, this initial inclusion would be entirely self-contained.
- Other developers: N/A (not a System Wide Change)
- Release engineering: #7198
- 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
N/A.
N/A (not a System Wide Change)
How To Test
Until version 1.0, Stratis should not be used on a system with valuable data. Stratis will not be well-integrated into the boot process, nor will placing root partition on it be possible. However, Fedora users and testers can try Stratis on non-primary disks, and put it through its paces to generate bug reports and feature requests that can guide Stratis development leading up to a stable release.
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
Just don't include the Stratis-specific packages in the final release.
- 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? N/A
Documentation
Please see https://stratis-storage.github.io/ for design documents and API reference.
Development and issue tracking is at https://github.com/stratis-storage/stratisd
N/A (not a System Wide Change)
Release Notes
TBD