< Changes
(→Release Notes: https://pagure.io/fesco/issue/1688#comment-430734) |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 34: | Line 34: | ||
* Name: [[User:vpodzime| Vratislav Podzimek]] (Anaconda/Blivet) | * Name: [[User:vpodzime| Vratislav Podzimek]] (Anaconda/Blivet) | ||
* Email: vpodzime@redhat.com | * Email: vpodzime@redhat.com | ||
* Name: Heinz Mauelshagen (LVM) | * Name: [[User:mauelsha| Heinz Mauelshagen (LVM)]] | ||
* Email: heinzm@redhat.com | * Email: heinzm@redhat.com | ||
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/26 | Fedora 26 ]] | * Targeted release: [[Releases/26 | Fedora 26 ]] | ||
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1427113 #1427113] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 61: | Line 60: | ||
<!-- 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: | * Release engineering: N/A <!-- 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 rebuid 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 rebuid 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 139: | Line 138: | ||
TBD | TBD | ||
[[Category: | [[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 05:38, 17 March 2017
Anaconda LVM RAID
Summary
Use LVM RAID instead of LVM of top of MD RAID in the Anaconda installer.
Owner
- Name: Vratislav Podzimek (Anaconda/Blivet)
- Email: vpodzime@redhat.com
- Name: Heinz Mauelshagen (LVM)
- Email: heinzm@redhat.com
- Release notes owner:
Current status
Detailed Description
In the current situation when a user chooses LVM (or Thin LVM) partitioning in the Custom Spoke and then sets RAID level for the VG Anaconda (and Blivet) create an MD RAID device which is used as a PV for the VG. With this change we are going to use LVM RAID directly instead. That means that all the LVs in that VG will be RAID LVs with the specified RAID level. LVM RAID provides same functionality as MD RAID (it shares the same kernel code) with better flexibility and additional features expected in future.
Benefit to Fedora
Using a new promising solution with better flexibility (e.g. using different RAID levels for different LVs, changing RAID levels of existing LVs etc.) and reliability due to ongoing development and maintenance from the LVM team.
Scope
- Proposal owners:
- Blivet developers: Support creation of LVM RAID in a similar way as LVM on top of MD RAID. (Creation of RAID LVs is already supported.)
- Anaconda developers: Use the new way to create LVM RAID instead of creating LVM on top of MD RAID.
- LVM developers: LVM RAID already has all features required by this change.
- Other developers: N/A (not a System Wide Change)
- Release engineering: N/A
- 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 (not a System Wide Change)
How To Test
1. Try LVM (or Thin LVM) installation with some RAID level specified for the newly created VG.
2. Reboot.
3. Check that the newly created LVs have the specified RAID level. (e.g. using "sudo lvs -o +lv_layout")
User Experience
There should be no visible change for non-expert users. Expert users could make use of the new LVM RAID's features.
Dependencies
Anaconda (Blivet) already depends on all packages (lvm2) related to this change.
Contingency Plan
- Contingency mechanism: Revert changes in Anaconda and keep using the existing solution
- Contingency deadline: Beta (Due to the simple contingency mechanism.)
- Blocks release: Yes
Documentation
Documentation will be covered in the Installation Guide.
Release Notes
TBD