Editing Test Day:2011-01-27 Network Device Naming With Biosdevname

{{autolang|base=yes}}

{{Infobox_group
| name = Fedora Test Days
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_15_test_days]]
| caption = [[Features/ConsistentNetworkDeviceNaming|Network Device Naming With Biosdevname]]
| date = Thursday, January 27, 2011
| time = all day
| website = [[QA/Fedora_15_test_days]]
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
| fedora_mailing_list = test
}}

{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}

== What to test? ==

Today's instalment of Fedora Test Day will focus on '''[[Features/ConsistentNetworkDeviceNaming#Consistent_Network_Device_Naming|Network Interface Naming]]'''.

Traditionally network interfaces in Linux are named ethN. With multiple network adapters, both onboard and add-in, single and multiport, in modern server platforms, the naming of these interfaces is non-deterministic. Specifically, ''eth0'' does not always map to ''Gb1'' or ''Embedded NIC 1'' as named on the server chassis. This makes the existing naming not very user friendly for administration. 

This issue is addressed by assigning names to network interfaces based on their physical location on the system board.  [http://linux.dell.com/biosdevname/ Biosdevname], which is a Dell developed utility, can suggest names to network interfaces, which are physical location based.

The naming convention followed is:
* Embedded devices: <code>em<port></code>   [https://fedoraproject.org/wiki/File:Onboard_Network_Adapters.jpg Image]
* Add-in PCI cards: <code>pci<slot>#<port>_<virtual-function-instance></code> [https://fedoraproject.org/wiki/File:PCI_Addin_Network_Adapters.jpg Image]

Please find an example {{filename|ifconfig}} output from this naming convention [https://fedoraproject.org/wiki/QA:Testcase_biosdevname_Example_Ifconfig_Output here]

Please refer to the following link for more details on the issue itself and various solutions we proposed upstream to address this issue which were unsuccessful.

* [http://linux.dell.com/wiki/index.php/Oss/libnetdevname#Implementation  Unsuccessful Attempts to Address This Issue]
* [http://linux.dell.com/files/presentations/Linux_Plumbers_Conf_2010/matt-domsch-network-device-naming.pdf Linux Plumbers Conf 2010 presentation by Matt Domsch]

== Who's available ==

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* [[User:Narendrak|Narendra K]] (nick: narendrak) -- 3:30 - 18:30
[[Infrastructure/UTCHowto#How_can_I_convert_UTC_into_local_time.3F|UTC]]
* [[User:mdomsch|Matt Domsch]] (nick: mdomsch) -- 18:00 - 23:00 [[Infrastructure/UTCHowto#How_can_I_convert_UTC_into_local_time.3F|UTC]]
* [[User:jlaska|James Laska]] (nick: jlaska) -- 13:00 - 22:00 [[Infrastructure/UTCHowto#How_can_I_convert_UTC_into_local_time.3F|UTC]]

== Prerequisite for Test Day == 

=== Hardware Requirements ===

A [[:File:Biosdevname-support-check.sh|script is available]] to determine whether your system will be impacted by the {{package|biosdevname}} change.  The following example shows how to run the script to determine whether your hardware can be used during the Test Day.

<pre>
# su -c 'curl -s https://fedoraproject.org/w/uploads/3/38/Biosdevname-support-check.sh | bash' 
Password: 
Checking hardware requirements                             [  OK  ]
Checking for SMBIOS type 41 support                        [  OK  ]
Checking for SMBIOS type 9 support                         [  OK  ]
Checking for PCI Interrupt Routing support                 [  OK  ]
</pre>

If the output of the script is <code>[  <span style="color:green;">OK</span>  ]</code> and ''any'' of the following checks is <code>[  <span style="color:green;">OK</span>  ]</code>, your hardware is supported by biosdevname and you can take part in the Test Day.

For reference, the hardware requirements are:

# A system (servers, laptop, or desktop) with one or more onboard network adapter(s) and/or one or more add-in network adapter(s)
# System firmware/BIOS should implement an SMBIOS type 41 or type 9 record, or PCI Interrupt Routing
# Requirements for Testing a SR-IOV capable network adapter
## Intel VT-d or AMD-VI hardware with CPU virtualization and IOMMU (enabled in BIOS, please refer to the system manufacturer's manual on how to enable the options)
## SR-IOV support (enabled in BIOS if BIOS provides the option)
## Single and multiport add-in network adapters with SRIOV capability

For more information on SR-IOV Please see [http://en.community.dell.com/dell-blogs/enterprise/b/tech-center/archive/2010/11/17/rhel-6-up-and-running-with-sr-iov-on-dell-poweredge-servers.aspx here]

It is strongly advised that you upload your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]

=== Software Requirements ===

# Fedora Rawhide
# ''Optional'' - the SMBIOS type 41 device type instance and string should be available in sysfs.  This will be available in sysfs '''only''' when BIOS implements type 41. If type 41 is not implemented, then <code>$PIRQ</code> will be the fallback and this attribute will not be available in sysfs. This attribute is available on kernels with version >= 2.6.36 (includes Rawhide)

== How to test? ==

At a high level, the testing will focus on 
# Network interface names ''during'' install time
# Network interface names ''after'' installation is completed (after you login for first time)
# Required changes available in {{filename|ifcfg-ethN}} config files
# ''Upgrading'' from a previous release (Fedora 14) to Fedora [[Releases/Rawhide|Rawhide]] does not affect the naming scheme that existed in the previous release

=== '''Install or upgrade to Rawhide''' ===

There are several ways to set up your test system.

{{anchor|update}}
==== Upgrading From Fedora 14 to Rawhide ====

* You can upgrade an already installed Fedora 14 system using {{command|yum}} - for guidance, see [[Releases/Rawhide#Yum_update_from_previous_release|yum update from previous release]]

{{anchor|install}}
==== Install Rawhide ====

* You can install Rawhide with [http://fedoraproject.org/get-fedora Fedora 14 ISO media] - for guidance, see [[Releases/Rawhide#Using_a_general_release_Fedora_ISO|Install Rawhide using Fedora 14 ISO]]
* Or you can use a special Rawhide install image provided for this test day - [http://jlaska.fedorapeople.org/test-day/i386 i386] or [http://jlaska.fedorapeople.org/test-day/x86_64 x86_64] {{filename|boot.iso}}. For guidance, see [http://docs.fedoraproject.org/en-US/Fedora/14/html/Installation_Guide/index.html the installation guide]

{{anchor|live}}
==== Boot into a Rawhide live image ====

* You can download and boot a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ Fedora Rawhide live image] - for guidance, see [[How_to_create_and_use_Live_USB]]

=== Complete the Test Cases ===

'''Upgrade Testing''' - These test cases should be executed when upgrading a Fedora 14 system to Rawhide. Please refer to the section [[#update|Upgrading From Fedora 14 to Rawhide]] above.

* [[QA:Testcase biosdevname NIC rules persist after upgrade]] - Verify upgrade from Fedora 14 to Rawhide

'''Install Time Testing''' - The test cases in this category should be executed when performing a new Rawhide installation. Please refer to the section [[#install|Install Rawhide]] above.

# [[QA:Testcase biosdevname NIC naming after install]] - Verify that onboard and add-in interfaces are named as expected during install time
# [[QA:Testcase biosdevname Automated Kickstart Installation]] - Unattended/automated kickstart installation using ksdevice=emN option

'''Run Time Testing''' - The test cases in this category should be executed when running a fresh Rawhide - either from the [[#live|live image]], or after performing a [[#install|new Rawhide installation]].

# [[QA:Testcase biosdevname on-board network interface names]] - Verify that onboard interfaces are named as <code>emN</code>
# [[QA:Testcase biosdevname add-in network interface names]] - Verify that PCI add-in interfaces are named as <code>pci<slot>#<port></code>
# [[QA:Testcase biosdevname SRIOV virtual function interface names]] - Verify that Virtual Function interfaces are named as <code>pci<slot>#<port>_<virtual-function-instance></code>
# [[QA:Testcase biosdevname interface configuration]] - Verify that onboard, add-in, and add-in Virtual Function interfaces can be configured

=== Report your results ===

Construct a table or list to allow testers to post results.  Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:

If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility gnome-disk-utility] for bugs in the Palimpsest graphical front end itself. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, if your system worked correctly, simply enter the word '''PASS'''. If you had trouble, enter the word '''FAIL''', with a footnote indicator, and put a link to the bug report in the References column (as in the example line). For tests you could not perform, enter a dash.

{|
! User
! Smolt Profile
! [[QA:Testcase biosdevname NIC naming after install|install]]
! [[QA:Testcase biosdevname NIC rules persist after upgrade|upgrade]]
! [[QA:Testcase_biosdevname_Automated_Kickstart_Installation|kickstart]]
! [[QA:Testcase biosdevname on-board network interface names|on-board]]
! [[QA:Testcase biosdevname add-in network interface names|add-in]]
! [[QA:Testcase biosdevname SRIOV virtual function interface names|SRIOV]]
! [[QA:Testcase biosdevname interface configuration|iface configuration]]
! References
|-
| [[User:SampleUser|Sample User]]
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
| {{result|pass}} 
| {{result|unknown}}
| {{result|inprogress}}
| {{result|none}}
| {{result|pass}}
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|fail}} <ref>{{bz|12345}}</ref>
| <references/>
|-
|}

[[Category:Fedora 15 Test Days]]