m (fix some formatting) |
m (fix from tgill) |
||
| Line 98: | Line 98: | ||
== 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. | ||
Revision as of 18:25, 5 December 2017
= Changes/StratisStorage
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
- Email: agrover@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 28
- Last updated: 2017-12-05
- Tracker bug: <will be assigned by the Wrangler>
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
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: #Releng issue number (a check of an impact with Release Engineering is needed)
- 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