Bug 763421 (GLUSTER-1689) - Ethernet interfaces need to be able to be mapped to the correct device names at install time
Summary: Ethernet interfaces need to be able to be mapped to the correct device names ...
Keywords:
Status: CLOSED WONTFIX
Alias: GLUSTER-1689
Product: GlusterSP
Classification: Retired
Component: core
Version: 3.0.5
Hardware: All
OS: All
low
low
Target Milestone: 3.2
Assignee: Timothy Asir
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-23 23:28 UTC by Kevin Brooks
Modified: 2011-02-10 12:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Kevin Brooks 2010-09-23 23:28:13 UTC
Without the ability to identify and map your Ethernet interfaces to the correct interface name at boot time you end up with a mess that you have to go back in and fix manually.  The udev subsystem does a horrible job of mapping interfaces to anything sane.  With parallel device driver loads it assigning interfaces to names with no sane way to predict what it's going to do.  In a server environment where specific interfaces may need to be mapped to specific networks and functions the ability to identify and assign interfaces to names is extremely important.


Note You need to log in before you can comment on or make changes to this bug.