Bug 763421 (GLUSTER-1689)

Summary:	Ethernet interfaces need to be able to be mapped to the correct device names at install time
Product:	[Retired] GlusterSP	Reporter:	Kevin Brooks <brooks>
Component:	core	Assignee:	Timothy Asir <timothyasir>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	3.0.5	CC:	platform, shireesh, vijay
Target Milestone:	3.2
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.