From Fedora Project Wiki

< Anaconda‎ | Features

Revision as of 20:22, 26 June 2009 by Ddumas (talk | contribs) (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...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Anaconda FCoE Boot Support


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


  • email: hdegoede AT fedoraproject DOT org

Current status

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

Detailed Description

FCoE devices will be recognized and the installation will offer to use them.

Benefit to Fedora

Improved hardware support


The code is written and is currently in debug.

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.


  • TBD

Contingency Plan

Revert to previous codebase.


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