From Fedora Project Wiki
(Created page with '= Anaconda FCoE Boot Support = == Summary == Add FCoE support to anaconda's boot and storage code. == Owner == <!--This should link to your home wiki page so we know who you ar...')
 
No edit summary
Line 1: Line 1:
= Anaconda FCoE Boot Support =
= Anaconda FCoE Support =


== Summary ==
== Summary ==
Add FCoE support to anaconda's boot and storage code.
Add FCoE support to anaconda's storage code.


== Owner ==
== Owner ==
<!--This should link to your home wiki page so we know who you are-->
* Name: [[HansdeGoede | Hans De Goede]]
* Name: [[User:hdegoede| Hans De Goede]]
* email: jwrdegoede AT fedoraproject DOT org
 
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
* email: hdegoede AT fedoraproject DOT org


== Current status ==
== Current status ==
* Targeted release: [[Releases/11 | Fedora 12 ]]  
* Targeted release: [[Releases/12 | Fedora 12 ]]  
* Last updated: 2009-06-26
* Last updated: 2009-06-26
* Percentage of completion: 70%
* Percentage of completion: 40%


== Detailed Description ==
== Detailed Description ==
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
FCoE devices can be added from the advanced storage menu and then used to install onto.
FCoE devices will be recognized and the installation will offer to use them.


== Benefit to Fedora ==
== Benefit to Fedora ==
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
Improved hardware support
Improved hardware support


== Scope ==
== Scope ==
<!-- What work do the 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?-->
The code is mostly written and is currently in debug, still to do:
The code is written and is currently in debug.
* kickstart support for fcoe
* write out FCoE configuration information to the installed system


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature 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.
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
A good "how to test" should answer these four questions:
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this feature? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the feature is
working like it's supposed to?
3. What are the expected results of those actions?
-->
Testing will require FCoE hardware, which is not terribly common.  
Testing will require FCoE hardware, which is not terribly common.  


Line 64: Line 46:


== User Experience ==
== User Experience ==
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
This should improve the user's experience with regard to the storage configuration portion of system installation.
This should improve the user's experience with regard to the storage configuration portion of system installation.


Line 70: Line 51:


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature 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 feature)? -->
* openfcoe initiator support inside the kernel (done)
* TBD
* fcoe-utils (done)
 


== 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 "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
Disable the add FCoE storage button, which effectively nullifies all FCoE code
Revert to previous codebase.


== Documentation ==
== Documentation ==
Line 85: Line 64:


== Comments and Discussion ==
== Comments and Discussion ==
* See [[Talk:Features/AnacondaStorageRewrite]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
* See [[Talk:Features/AnacondaStorageRewrite]]or conversation without bogging down the main feature page -->


[[Category:FeaturePageIncomplete]]
[[Category:FeatureReadyForWrangler]]
<!-- When your feature page is completed and ready for review -->
<!-- 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-->

Revision as of 11:46, 29 June 2009

Anaconda FCoE Support

Summary

Add FCoE support to anaconda's storage code.

Owner

Current status

  • Targeted release: Fedora 12
  • Last updated: 2009-06-26
  • Percentage of completion: 40%

Detailed Description

FCoE devices can be added from the advanced storage menu and then used to install onto.

Benefit to Fedora

Improved hardware support

Scope

The code is mostly written and is currently in debug, still to do:

  • kickstart support for fcoe
  • write out FCoE configuration information to the installed system

How To Test

Testing will require FCoE hardware, which is not terribly common.

We will have to verify the following areas of functionality:

  • recognize devices and install
    • on new partitions
    • on existing partitions
    • on new LVM logical volumes
    • on preexisting LVM logical volumes
  • creation of encrypted block devices at various levels in the device stack (partition, PV, LV, mdarray, &c)
  • detection of arbitrarily complex device configurations (luks, mdraid, lvm, &c)
  • management and configuration of existing encrypted block devices
  • automatic partitioning of systems
  • clearing of existing devices/partitions
  • removal of existing devices
  • reconfiguration of existing devices
  • detection of existing upgradable installations with widely varied storage configurations
  • rescue mounting of existing systems with a wide variety of storage configurations


User Experience

This should improve the user's experience with regard to the storage configuration portion of system installation.

No impact unless you have this hardware.

Dependencies

  • openfcoe initiator support inside the kernel (done)
  • fcoe-utils (done)

Contingency Plan

Disable the add FCoE storage button, which effectively nullifies all FCoE code

Documentation

Will need to include in Installation Guide.

Release Notes

  • Not terribly applicable because this hardware is not common, but worth a small mention.

Comments and Discussion

Retrieved from "https://fedoraproject.org/w/index.php?title=Anaconda/Features/FCoE&oldid=110676"