(Check in the template to begin working on it) |
m (internal link cleaning) |
||
(10 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
<!-- All fields on this form are required to be accepted by FESCo. | <!-- All fields on this form are required to be accepted by FESCo. | ||
We also request that you maintain the same order of sections so that all of the feature pages are uniform. --> | We also request that you maintain the same order of sections so that all of the feature pages are uniform. --> | ||
Line 11: | Line 4: | ||
<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all features in the same namespace --> | <!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all features in the same namespace --> | ||
= | = Multipath Installation = | ||
== Summary == | == Summary == | ||
Anaconda adds the ability to correctly identify and set up multipath devices for use as installation targets. | |||
== Owner == | == Owner == | ||
* Name: [[User:Pjones| Peter Jones]] | |||
* Name: [[User: | * Email: pjones@redhat.com | ||
* Email: | |||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/ | * Targeted release: [[Releases/? | Fedora ? ]] | ||
* Last updated: | * Last updated: 9-Feb-2010 | ||
* Percentage of completion: | * Percentage of completion: 95% | ||
== Detailed Description == | == Detailed Description == | ||
This feature adds support for installing to a multipath device and booting from such a device. | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
This is a hardware enabling feature. It allows Fedora to be installed on machines which were previously problematic. | |||
== Scope == | == Scope == | ||
This has repercussions in several packages: | |||
* Anaconda | |||
** identification/setup before install | |||
** configure dracut to build a hostonly initrd | |||
* grubby/kernel: | |||
** build initrd at the end of the installation rather than as soon as the kernel is installed | |||
* dracut | |||
** assemble mpath devices during boot in order to correctly find the root filesystem | |||
== How To Test == | == How To Test == | ||
* install to a machine with multipath storage. | |||
** Ideally, test devices should include active/active and active/passive configurations. | |||
* see if it boots correctly afterwards | |||
** boot, and then run "dmsetup ls" and "dmsetup table" as root, making sure that the output indicates that / is indeed using a multipath device. | |||
== User Experience == | == User Experience == | ||
During installation, multipath devices should show up on the "multipath" tab under "Specialized Storage Devices", and the constituent devices should not be present. | |||
== Dependencies == | == Dependencies == | ||
This depends on changes to: | |||
* anaconda (80% done (kickstart support is TODO)) | |||
* dracut (100% done) | |||
* device-mapper-multipath (100% done) | |||
* lvm (100% done, I think) | |||
* kernel (100% done) | |||
* grubby (100% done) | |||
== Contingency Plan == | == Contingency Plan == | ||
* None necessary - hardware that doesn't install correctly still won't install correctly. | |||
== Documentation == | == Documentation == | ||
* No separate docs at this time; we will add some for kickstart support. There's also some documentation of the UI as part of [[Design/AnacondaStorageUI|the storage design page]]. | |||
== Release Notes == | == Release Notes == | ||
* anaconda now supports installation to multipath devices. | |||
== Comments and Discussion == | == Comments and Discussion == | ||
* See [[Talk:Features/ | * See [[Talk:Features/MultipathInstall]] | ||
[[Category:FeaturePageIncomplete]] | |||
<!-- When your feature page is completed and ready for review --> | <!-- When your feature page is completed and ready for review --> | ||
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | ||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | ||
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> |
Latest revision as of 21:43, 17 September 2016
Multipath Installation
Summary
Anaconda adds the ability to correctly identify and set up multipath devices for use as installation targets.
Owner
- Name: Peter Jones
- Email: pjones@redhat.com
Current status
- Targeted release: Fedora ?
- Last updated: 9-Feb-2010
- Percentage of completion: 95%
Detailed Description
This feature adds support for installing to a multipath device and booting from such a device.
Benefit to Fedora
This is a hardware enabling feature. It allows Fedora to be installed on machines which were previously problematic.
Scope
This has repercussions in several packages:
- Anaconda
- identification/setup before install
- configure dracut to build a hostonly initrd
- grubby/kernel:
- build initrd at the end of the installation rather than as soon as the kernel is installed
- dracut
- assemble mpath devices during boot in order to correctly find the root filesystem
How To Test
- install to a machine with multipath storage.
- Ideally, test devices should include active/active and active/passive configurations.
- see if it boots correctly afterwards
- boot, and then run "dmsetup ls" and "dmsetup table" as root, making sure that the output indicates that / is indeed using a multipath device.
User Experience
During installation, multipath devices should show up on the "multipath" tab under "Specialized Storage Devices", and the constituent devices should not be present.
Dependencies
This depends on changes to:
- anaconda (80% done (kickstart support is TODO))
- dracut (100% done)
- device-mapper-multipath (100% done)
- lvm (100% done, I think)
- kernel (100% done)
- grubby (100% done)
Contingency Plan
- None necessary - hardware that doesn't install correctly still won't install correctly.
Documentation
- No separate docs at this time; we will add some for kickstart support. There's also some documentation of the UI as part of the storage design page.
Release Notes
- anaconda now supports installation to multipath devices.
Comments and Discussion