| Дни Испытаний Fedora | |
|---|---|
| |
| Именование сетевых устройсв с использованием Biosdevname | |
| Website | QA/Fedora_15_test_days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
Если Вы пришли на эту страницу до или после официальной даты тестирования, это не значит, что страница для Вас бесполезно. Вы можете провести тестирование и добавить результаты тестов в таблицу и Bugzilla. Если Вы пришли спустя месяц на данную страницу, то посмотрите, возможно сейчас проводятся или уже проведены дополнительные и/или подобные испытания, но более новые. Посмотреть это можно в расписании тестирования.
Что тестируем?
Сегодняшний день испытания будет посвящен тестированию Именованию Сетевых Интерфейсов в Fedora Rawhide
Традиционно сетевые интерфейсы в Linux называются ethN. С несколькими сетевыми адаптерами (встроенными, дополнительными, одно- и многопортовыми) в современных серверных платформах именование происходит "слепое", не возможно с точностью сказать, какой адаптер будет именоваться eth0 встроенный или PCI-адаптер, что в свою очередь не удобно для администрирования сервера.
Данный вопрос решается путем присвоения имен сетевым интерфейсам, основываясь на их физическое расположение на системной плате. Biosdevname, это утилита разработанная в Dell, которая предлагает имена сетевым интерфейсам в заивисимости от их физического расположения.
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
- Narendra K (irc_nick1) will be your host for the day.
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
Prerequisite for Test Day
- Hardware Requirements
- Computer system (Servers/Laptops/Desktops) with onboard(Lan-On-Motherboard) network adapters and/or add-in network adapters.
- Single and multiport add-in network adapters with SRIOV capability
- It is strongly advised that your hardware profile uploaded to Smolt according to these instructions
- Firmware/BIOS requirements
- System firmware/BIOS should implement SMBIOS type 41 record which defines a device type instance and string for onboard devices (network adapters included)or $PIRQ Table(PCI Irq Routing Table).
- System firmware/BIOS should implement SMBIOS type 9 record or implement $PIRQ Table(PCI Irq Routing Table).
- Software Requirements
- The system should be updated to Fedora Rawhide
- The SMBIOS type 41 device type instance and string should be available in sysfs. Other OEMs might export this information in a different SMBIOS type. If it is exported to sysfs, look for the following sysfs links.
# lspci | grep -i ether 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 01:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 02:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) # find /sys/ -name index /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/index /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.1/index /sys/devices/pci0000:00/0000:00:03.0/0000:02:00.0/index /sys/devices/pci0000:00/0000:00:03.0/0000:02:00.1/index # find /sys/ -name label /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/label /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.1/label /sys/devices/pci0000:00/0000:00:03.0/0000:02:00.0/label /sys/devices/pci0000:00/0000:00:03.0/0000:02:00.1/label
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
ifcfg-ethNconfig files - Upgrading from a previous update (Say Fedora 14) to Fedora Rawhide does not affect the naming scheme that existed in the previous update (Say Fedora 14).
Update your machine / Available Rawhide Installation Methods
There are several ways to upgrade your test system.
- Upgrading From Fedora 14 to Today's Rawhide
- Upgrade from Fedora 14 to Fedora Rawhide using
yum-- for guidance, see yum update from previous release
- Install Today's Rawhide
- Install Fedora Rawhide using Fedora 14 ISO media -- for guidance, see Install rawhide using Fedora 14 ISO
- Boot into a Rawhide Live Image
- Download and boot a Fedora Rawhide live image -- for guidance, see How_to_create_and_use_Live_USB
Test Cases
Upgrade Testing - Test cases in this category need to executed when a Fedora 14 system is to be upgraded to Today's Rawhide. Please refer to the section Upgrading From Fedora 14 to Today's 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 need to be executed when installation of Rawhide is in progress. Please refer to the section Install Today's Rawhide above.
- QA:Testcase biosdevname NIC naming after install - Verify that Onboard and Add-in Interfaces are named as expected during Install Time
Run Time Testing - The test cases in this category need to be executed when you are booted into Fedora Live Image. Please refer to the section Boot into a Rawhide Live Image above to download a Fedora Rawhide Live Image.
- QA:Testcase biosdevname on-board network interface names - Verify that onboard interfaces are named as
emN - QA:Testcase biosdevname add-in network interface names - Verify that PCI add-in interfaces are named as
pci<slot>#<port> - QA:Testcase biosdevname SRIOV virtual function interface names - Verify that Virtual Function Interfaces are named as
pci<slot>#<port>_<virtual-function-instance> - QA:Testcase biosdevname interface configuration - Verify that onboard, Add-in, Add-in Virtual Function interfaces can be configured
Test 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 | names after install | names after upgrade | on-board ifaces | add-in ifaces | SRIOV ifaces | interface configuration | References |
|---|---|---|---|---|---|---|---|---|
| Sample User | HW |  |
 |
|
 |
 |