From Fedora Project Wiki
(initial text, incomplete)
 
(update feature page, ready for wrangler)
Line 12: Line 12:
== Current status ==
== Current status ==
* Targeted release: [[Releases/15 | Fedora 15 ]]  
* Targeted release: [[Releases/15 | Fedora 15 ]]  
* Last updated: 2010-10-26
* Last updated: 2010-11-13
* Percentage of completion: 00%
* Percentage of completion: 75%


<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
Line 21: Line 21:


The proposal is as follows:
The proposal is as follows:
* revive biosdevname from a dead.package
* update biosdevname to upstream release 0.3.0 (Done)
* provide a kickstart option to use biosdevname in udev rules
* ensure postinstall udev uses biosdevname in udev rules to name LAN-on-Motherboard network ports from ethX to lom[1234] (Done)
* have kickstart / anaconda use the biosdevname-provided names
* have kickstart / anaconda use the biosdevname-provided name lom[1234] (TBD)
* ensure postinstall udev uses biosdevname in udev rules




== Benefit to Fedora ==
== Benefit to Fedora ==
System Administrators can then use BIOS-provided names, which are consistent and not arbitrarily named, for their network ports.  This eliminates the confusion that non-deterministic naming brings, and eliminates the use of hard-coded MAC address based port renaming which a) is racy and error-prone, and b) introduces state into an otherwise stateless system.
System Administrators can then use BIOS-provided names, which are consistent and not arbitrarily named, for their network ports.  This eliminates the confusion that non-deterministic naming brings, and eliminates the use of hard-coded MAC address based port renaming which a) is racy and error-prone, and b) introduces state into an otherwise stateless system.
This is only known to affect Dell PowerEdge 10G and newer servers, and HP 5G and newer servers, that expose network port labels in SMBIOS.


== Scope ==
== Scope ==
Line 34: Line 36:


== How To Test ==
== How To Test ==
TBD
* System-Under-Test must be a Dell PowerEdge 10g or newer server (PE 1950 III class, or R610 class), or HP ProLiant 380 (5G or 6G).
<!-- 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.  
* biosdevname must be installed on the target system.
 
* erase /lib/udev/rules.d/70-persistent-net.rules file.  This is where naming is persisted across reboots.
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.
* reboot the system
 
* Following reboot:
A good "how to test" should answer these four questions:
** /sbin/ifconfig -a must show LAN-on-Motherboard ports named lom[1234]
 
** lom[1234] must correspond to the chassis labels. Verify using ethtool -p lom[1234] and watch the lights blink.
0. What special hardware / data / etc. is needed (if any)?
** /lib/udev/rules.d/70-persistent-net.rules should now have rules for lom[1234] and should correspond to chassis labels.
1. How do I prepare my system to test this feature? What packages
* Testing within anaconda TBD
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?
-->


== 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. -->
LAN-on-Motherboard ports will be named lom[1234] rather than ethX


== 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)? -->
None


== 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.  -->
None necessary, revert to previous release behaviour.


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. -->
* http://marc.info/?l=linux-hotplug&m=128892593821639&w=2
*


== Release Notes ==
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
*
* LAN-on-Motherboard ports on Dell PowerEdge 10G and newer servers, and HP ProLiant 5G and newer servers, will be named lomX rather than ethX, corresponding to the chassis labels.  Add-in network cards are unaffected and remain named ethX.  Existing installations upgraded to Fedora 15 will not see a change in names unless /lib/udev/rules.d/70-persistent-net.rules is deleted.
 


== Comments and Discussion ==
== Comments and Discussion ==
* See [[Talk:Features/YourFeatureName]] <!-- 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/YourFeatureName]]




[[Category:FeaturePageIncomplete]]
[[Category:FeatureReadyForWrangler]]
<!-- 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 -->

Revision as of 04:27, 14 November 2010

Consistent Network Device Naming

Summary

On systems with multiple network ports, allow use of BIOS-provided port names instead of ethX.

Owner

  • Email: Matt_Domsch@dell.com

Current status

  • Targeted release: Fedora 15
  • Last updated: 2010-11-13
  • Percentage of completion: 75%


Detailed Description

Systems, particularly servers, with multiple network ports, name the ports ethX in a non-deterministic order, and are therefore not useful for system administrators.

The proposal is as follows:

  • update biosdevname to upstream release 0.3.0 (Done)
  • ensure postinstall udev uses biosdevname in udev rules to name LAN-on-Motherboard network ports from ethX to lom[1234] (Done)
  • have kickstart / anaconda use the biosdevname-provided name lom[1234] (TBD)


Benefit to Fedora

System Administrators can then use BIOS-provided names, which are consistent and not arbitrarily named, for their network ports. This eliminates the confusion that non-deterministic naming brings, and eliminates the use of hard-coded MAC address based port renaming which a) is racy and error-prone, and b) introduces state into an otherwise stateless system.

This is only known to affect Dell PowerEdge 10G and newer servers, and HP 5G and newer servers, that expose network port labels in SMBIOS.


Scope

see above

How To Test

  • System-Under-Test must be a Dell PowerEdge 10g or newer server (PE 1950 III class, or R610 class), or HP ProLiant 380 (5G or 6G).
  • biosdevname must be installed on the target system.
  • erase /lib/udev/rules.d/70-persistent-net.rules file. This is where naming is persisted across reboots.
  • reboot the system
  • Following reboot:
    • /sbin/ifconfig -a must show LAN-on-Motherboard ports named lom[1234]
    • lom[1234] must correspond to the chassis labels. Verify using ethtool -p lom[1234] and watch the lights blink.
    • /lib/udev/rules.d/70-persistent-net.rules should now have rules for lom[1234] and should correspond to chassis labels.
  • Testing within anaconda TBD

User Experience

LAN-on-Motherboard ports will be named lom[1234] rather than ethX

Dependencies

None

Contingency Plan

None necessary, revert to previous release behaviour.

Documentation

Release Notes

  • LAN-on-Motherboard ports on Dell PowerEdge 10G and newer servers, and HP ProLiant 5G and newer servers, will be named lomX rather than ethX, corresponding to the chassis labels. Add-in network cards are unaffected and remain named ethX. Existing installations upgraded to Fedora 15 will not see a change in names unless /lib/udev/rules.d/70-persistent-net.rules is deleted.


Comments and Discussion

Retrieved from "https://fedoraproject.org/w/index.php?title=Features/ConsistentNetworkDeviceNaming&oldid=207159"