From Fedora Project Wiki
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 2: | Line 2: | ||
{{Infobox_group | {{Infobox_group | ||
| name = | | name = Fedora Test Days | ||
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_15_test_days]] | | image = [[File:Echo-testing-48px.png|link=QA/Fedora_15_test_days]] | ||
| caption = [[Features/ConsistentNetworkDeviceNaming|Network Device Naming With Biosdevname]] | | caption = [[Features/ConsistentNetworkDeviceNaming|Network Device Naming With Biosdevname]] | ||
| date = | | 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 | |||
}} | }} | ||
Line 12: | Line 16: | ||
== What to test? == | == What to test? == | ||
Today's | 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. | 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. | ||
Line 19: | Line 23: | ||
The naming convention followed is: | The naming convention followed is: | ||
* Embedded devices: <code>em<port></code> | * Embedded devices: <code>em<port></code> | ||
* Add-in PCI cards: <code>pci<slot>#<port>_<virtual-function-instance></code> | * Add-in PCI cards: <code>pci<slot>#<port>_<virtual-function-instance></code> | ||
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. | 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. | ||
Line 28: | Line 30: | ||
* [http://linux.dell.com/wiki/index.php/Oss/libnetdevname#Implementation Unsuccessful Attempts to Address This Issue] | * [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] | * [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) -- will be your host for the day | |||
* [[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 == | == Prerequisite for Test Day == | ||
Line 33: | Line 42: | ||
=== 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. | ||
<pre> | <pre> | ||
# su -c 'curl -s https://fedoraproject.org/w/uploads/3/38/Biosdevname-support-check.sh | bash' | |||
Password: | Password: | ||
Checking hardware requirements [ OK ] | Checking hardware requirements [ OK ] | ||
Line 51: | Line 60: | ||
# System firmware/BIOS should implement an SMBIOS type 41 or type 9 record, or PCI Interrupt Routing | # 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 | # 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) | ## SR-IOV support (enabled in BIOS if BIOS provides the option) | ||
## Single and multiport add-in network adapters with SRIOV capability | ## Single and multiport add-in network adapters with SRIOV capability | ||
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 === | ||
Line 93: | Line 93: | ||
* 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]] | * 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] | * 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}} | {{anchor|live}} | ||
==== Boot into a Rawhide live image ==== | ==== Boot into a Rawhide live image ==== | ||
Line 103: | Line 101: | ||
=== Complete the 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. | |||
* [[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. | '''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. | ||
Line 127: | Line 119: | ||
=== Report your 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: | |||
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. | |||
{| | {| | ||
Line 156: | Line 144: | ||
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref> | | {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref> | ||
| {{result|fail}} <ref>{{bz|12345}}</ref> | | {{result|fail}} <ref>{{bz|12345}}</ref> | ||
| <references/> | | <references/> | ||
|- | |- | ||
|} | |} | ||
[[Category:Fedora 15 Test Days]] | [[Category:Fedora 15 Test Days]] |