* [PROPOSAL]: Support Alternate Network Device Naming Schemes
@ 2009-11-27 9:11 Narendra K
0 siblings, 0 replies; 4+ messages in thread
From: Narendra K @ 2009-11-27 9:11 UTC (permalink / raw)
To: anaconda-devel-list
Cc: netdev, matt_domsch, charles_rose, sandeep_k_shandilya,
jordan_hargrave, shyam_iyer
We have been having discussions in the netdev list about creating multiple names for the network interfaces to bring determinism into the way network interfaces are named in the OSes. In specific, "eth0 in the OS does not always map to the integrated NIC Gb1 as labelled on the chassis".
http://marc.info/?l=linux-netdev&m=125510301513312&w=2 - (Re: PATCH: Network Device Naming mechanism and policy)
http://marc.info/?l=linux-netdev&m=125619338904322&w=2 - ([PATCH] udev: create empty regular files to represent net)
As a result of those discussions, we propose an installer based solution.
Installers as of now allow the discovered network interfaces to be configured. This solution proposes to provide an option for the users to either retain the default naming convention that the kernel now has, i.e ethN names or rename the network interfaces based on the chassis label, MAC addresses, Driver name and any other naming convention. Here is how the modified network configuration wizard would look during the os installation process -
---------- Network Configuration ------------------------
Default [ ] | SMBIOS Names [x] | Driver Names [] | MAC Names []
-----------------------------------------------------------------------
eth0 | Addin_NIC_1 | ice0 |
-----------------------------------------------------------------------
eth1 | Embedded_NIC_1 | bce0 |
-----------------------------------------------------------------------
eth2 | Embedded_NIC_2 | bce1 |
-----------------------------------------------------------------------
eth3 | Embedded_NIC_3 | bce2 |
-----------------------------------------------------------------------
eth4 | Embedded_NIC_4 | bce3 |
-----------------------------------------------------------------------
------------
| Next |
------------
[ ice0 - Intel Controller 0, bce0 - Broadcom Controller 0 ]
1. In addition to the default ethN names the user can check against the available naming conventions and the wizard would show the names the interfaces will be renamed to.
2. The moment the user hits the Next button all interfaces are renamed as per the Naming convention they have selected.
3. Any further network communication would be using the new names.
4. Ifconfig would show names like "Embedded_NIC_1" and not eth0 etc.
This way the OS names of network interfaces would have a co-relation to the chassis names. Irrespective of what the OS names the integrated port one, i.e eth0 or eth1, Embedded_NIC_1 will always refer to the integrated port 1, bringing in determinism.
Additional Reference:
http://marc.info/?l=linux-hotplug&m=125692284431543&w=2
http://marc.info/?l=linux-netdev&m=125683519310462&w=2
http://marc.info/?l=linux-netdev&m=125754944814387&w=2
http://marc.info/?l=linux-hotplug&m=125536996902867&w=2
With regards,
Narendra K
^ permalink raw reply [flat|nested] 4+ messages in thread
* [PROPOSAL]: Support Alternate Network Device Naming Schemes
@ 2009-11-27 9:42 Narendra K
2009-11-30 17:07 ` Jon Masters
2009-11-30 18:34 ` Bill Nottingham
0 siblings, 2 replies; 4+ messages in thread
From: Narendra K @ 2009-11-27 9:42 UTC (permalink / raw)
To: anaconda-devel-list
Cc: netdev, matt_domsch, charles_rose, sandeep_k_shandilya,
jordan_hargrave, shyam_iyer
We have been having discussions in the netdev list about creating multiple names for the network interfaces to bring determinism into the way network interfaces are named in the OSes. In specific, "eth0 in the OS does not always map to the integrated NIC Gb1 as labelled on the chassis".
http://marc.info/?l=linux-netdev&m=125510301513312&w=2 - (Re: PATCH: Network Device Naming mechanism and policy)
http://marc.info/?l=linux-netdev&m=125619338904322&w=2 - ([PATCH] udev: create empty regular files to represent net)
As a result of those discussions, we propose an installer based solution.
Installers as of now allow the discovered network interfaces to be configured. This solution proposes to provide an option for the users to either retain the default naming convention that the kernel now has, i.e ethN names or rename the network interfaces based on the chassis label, MAC addresses, Driver name and any other naming convention. Here is how the modified network configuration wizard would look during the os installation process -
---------- Network Configuration ------------------------
Default [ ] | SMBIOS Names [x] | Driver Names [] | MAC Names []
-----------------------------------------------------------------------
eth0 | Addin_NIC_1 | ice0 |
-----------------------------------------------------------------------
eth1 | Embedded_NIC_1 | bce0 |
-----------------------------------------------------------------------
eth2 | Embedded_NIC_2 | bce1 |
-----------------------------------------------------------------------
eth3 | Embedded_NIC_3 | bce2 |
-----------------------------------------------------------------------
eth4 | Embedded_NIC_4 | bce3 |
-----------------------------------------------------------------------
------------
| Next |
------------
[ ice0 - Intel Controller 0, bce0 - Broadcom Controller 0 ]
1. In addition to the default ethN names the user can check against the available naming conventions and the wizard would show the names the interfaces will be renamed to.
2. The moment the user hits the Next button all interfaces are renamed as per the Naming convention they have selected.
3. Any further network communication would be using the new names.
4. Ifconfig would show names like "Embedded_NIC_1" and not eth0 etc.
This way the OS names of network interfaces would have a co-relation to the chassis names. Irrespective of what the OS names the integrated port one, i.e eth0 or eth1, Embedded_NIC_1 will always refer to the integrated port 1, bringing in determinism.
Additional Reference:
http://marc.info/?l=linux-hotplug&m=125692284431543&w=2
http://marc.info/?l=linux-netdev&m=125683519310462&w=2
http://marc.info/?l=linux-netdev&m=125754944814387&w=2
http://marc.info/?l=linux-hotplug&m=125536996902867&w=2
With regards,
Narendra K
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PROPOSAL]: Support Alternate Network Device Naming Schemes
2009-11-27 9:42 [PROPOSAL]: Support Alternate Network Device Naming Schemes Narendra K
@ 2009-11-30 17:07 ` Jon Masters
2009-11-30 18:34 ` Bill Nottingham
1 sibling, 0 replies; 4+ messages in thread
From: Jon Masters @ 2009-11-30 17:07 UTC (permalink / raw)
To: Discussion of Development and Customization of the Red Hat Linux Installer
Cc: netdev, shyam_iyer, matt_domsch, jordan_hargrave, charles_rose
On Fri, 2009-11-27 at 03:42 -0600, Narendra K wrote:
> We have been having discussions in the netdev list about creating multiple names for the network interfaces to bring determinism into the way network interfaces are named in the OSes. In specific, "eth0 in the OS does not always map to the integrated NIC Gb1 as labelled on the chassis".
>
> http://marc.info/?l=linux-netdev&m=125510301513312&w=2 - (Re: PATCH: Network Device Naming mechanism and policy)
> http://marc.info/?l=linux-netdev&m=125619338904322&w=2 - ([PATCH] udev: create empty regular files to represent net)
>
> As a result of those discussions, we propose an installer based solution.
Very cool. Thanks for your continued hard work on this stuff :) Do you
have proof of concept Anaconda patches available?
Jon.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PROPOSAL]: Support Alternate Network Device Naming Schemes
2009-11-27 9:42 [PROPOSAL]: Support Alternate Network Device Naming Schemes Narendra K
2009-11-30 17:07 ` Jon Masters
@ 2009-11-30 18:34 ` Bill Nottingham
1 sibling, 0 replies; 4+ messages in thread
From: Bill Nottingham @ 2009-11-30 18:34 UTC (permalink / raw)
To: Discussion of Development and Customization of the Red Hat Linux Installer
Cc: netdev, shyam_iyer, matt_domsch, jordan_hargrave, charles_rose
Narendra K (Narendra_K@dell.com) said:
> Installers as of now allow the discovered network interfaces to be configured. This solution proposes to provide an option for the users to either retain the default naming convention that the kernel now has, i.e ethN names or rename the network interfaces based on the chassis label, MAC addresses, Driver name and any other naming convention. Here is how the modified network configuration wizard would look during the os installation process -
>
>
> ---------- Network Configuration ------------------------
>
> Default [ ] | SMBIOS Names [x] | Driver Names [] | MAC Names []
> -----------------------------------------------------------------------
> eth0 | Addin_NIC_1 | ice0 |
> -----------------------------------------------------------------------
> eth1 | Embedded_NIC_1 | bce0 |
> -----------------------------------------------------------------------
> eth2 | Embedded_NIC_2 | bce1 |
> -----------------------------------------------------------------------
> eth3 | Embedded_NIC_3 | bce2 |
> -----------------------------------------------------------------------
> eth4 | Embedded_NIC_4 | bce3 |
> -----------------------------------------------------------------------
>
> ------------
> | Next |
> ------------
>
> [ ice0 - Intel Controller 0, bce0 - Broadcom Controller 0 ]
>
> 1. In addition to the default ethN names the user can check against the available naming conventions and the wizard would show the names the interfaces will be renamed to.
> 2. The moment the user hits the Next button all interfaces are renamed as per the Naming convention they have selected.
> 3. Any further network communication would be using the new names.
> 4. Ifconfig would show names like "Embedded_NIC_1" and not eth0 etc.
That's a horrible interface to show the user when a large portion of
them do not care at all. (Also, not sure why netdev@vger cares about the
implementation details of OS installers.)
Bill
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-11-30 18:34 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-11-27 9:42 [PROPOSAL]: Support Alternate Network Device Naming Schemes Narendra K
2009-11-30 17:07 ` Jon Masters
2009-11-30 18:34 ` Bill Nottingham
-- strict thread matches above, loose matches on Subject: below --
2009-11-27 9:11 Narendra K
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).