From Fedora Project Wiki

(general care & feeding)
(more care and feeding - use proper headings and sub-heads)
Line 40: Line 40:
== Prerequisite for Test Day ==  
== Prerequisite for Test Day ==  


; Hardware Requirements
=== 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.
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.
Line 63: Line 63:
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]
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
=== Software Requirements ===
<ol>
 
<li> Fedora Rawhide.
# Fedora Rawhide
</li><li>''Optional'' - the SMBIOS type 41 device type instance and string 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).
# ''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)
</li></ol>


== How to test? ==
== How to test? ==
Line 75: Line 74:
# Network interface names ''after'' installation is completed (after you login for first time)
# Network interface names ''after'' installation is completed (after you login for first time)
# Required changes available in {{filename|ifcfg-ethN}} config files
# Required changes available in {{filename|ifcfg-ethN}} config files
# ''Upgrading'' from a previous update (Say Fedora 14) to Fedora [[Releases/Rawhide|Rawhide]] does not affect the naming scheme that existed in the previous update (Say Fedora 14).
# ''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''' ===
=== '''Install or upgrade to Rawhide''' ===
Line 81: Line 80:
There are several ways to set up your test system.
There are several ways to set up your test system.


; Upgrading From Fedora 14 to Rawhide {{anchor|update}}
{{anchor|update}}
: 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]]
==== 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]


; Install Rawhide {{anchor|install}}
{{anchor|live}}
# 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]]
==== Boot into a Rawhide live image ====
# 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]


; Boot into a Rawhide live image {{anchor|live}}
* 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]]
: 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]]


== Test Cases ==
=== 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.
'''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.
Line 109: Line 114:
# [[QA:Testcase biosdevname interface configuration]] - Verify that onboard, add-in, and add-in Virtual Function interfaces can be configured
# [[QA:Testcase biosdevname interface configuration]] - Verify that onboard, add-in, and add-in Virtual Function interfaces can be configured


== Test Results ==
=== 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:
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:

Revision as of 09:01, 26 January 2011

Fedora Test Days
Echo-testing-48px.png
Network Device Naming With Biosdevname

Date Thursday, January 27, 2011
Time all day

Website QA/Fedora_15_test_days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
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 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 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 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. 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: em<port>
  • Add-in PCI cards: pci<slot>#<port>_<virtual-function-instance>

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.

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

Hardware Requirements

A script is available to determine whether your system will be impacted by the Package-x-generic-16.pngbiosdevname change. The following example shows how to run the script to determine whether your hardware can be used during the Test Day.

# 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  ]

If the output of the script is [ OK ] and any of the following checks is [ OK ], your hardware is supported by biosdevname and you can take part in the Test Day.

For reference, the hardware requirements are:

  1. A system (servers, laptop, or desktop) with one or more onboard network adapter(s) and/or one or more add-in network adapter(s)
  2. System firmware/BIOS should implement an SMBIOS type 41 or type 9 record, or PCI Interrupt Routing
  3. Single and multiport add-in network adapters with SRIOV capability

It is strongly advised that you upload your hardware profile uploaded to Smolt according to these instructions

Software Requirements

  1. Fedora Rawhide
  2. 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 $PIRQ 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

  1. Network interface names during install time
  2. Network interface names after installation is completed (after you login for first time)
  3. Required changes available in ifcfg-ethN config files
  4. Upgrading from a previous release (Fedora 14) to Fedora 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.

Upgrading From Fedora 14 to Rawhide

Install Rawhide

Boot into a Rawhide live image

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 Upgrading From Fedora 14 to Rawhide above.

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

  1. QA:Testcase biosdevname NIC naming after install - Verify that onboard and add-in interfaces are named as expected during install time
  2. 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 image, or after performing a new Rawhide installation.

  1. QA:Testcase biosdevname on-board network interface names - Verify that onboard interfaces are named as emN
  2. QA:Testcase biosdevname add-in network interface names - Verify that PCI add-in interfaces are named as pci<slot>#<port>
  3. QA:Testcase biosdevname SRIOV virtual function interface names - Verify that Virtual Function interfaces are named as pci<slot>#<port>_<virtual-function-instance>
  4. 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 Bugzilla usually for the component udisks, or 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 install upgrade kickstart on-board add-in SRIOV iface configuration References
Sample User HW
Pass pass
Inprogress inprogress
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345