Bug 1628578

Summary:	No mention of paravirtualized devices naming
Product:	Red Hat Enterprise Linux 7	Reporter:	Lukas Zapletal <lzap>
Component:	doc-Networking_Guide	Assignee:	Marc Muehlfeld <mmuehlfe>
Status:	CLOSED WONTFIX	QA Contact:	Zhang Kexin <kzhang>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	7.7-Alt	CC:	lnykryn, rhel-docs, thaller
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-06 08:54:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lukas Zapletal 2018-09-13 13:22:01 UTC

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/ch-consistent_network_device_naming

Section Number and Name: 
CHAPTER 8. CONSISTENT NETWORK DEVICE NAMING

Describe the issue: 
After reading the rules in section 8.1. Naming Schemes Hierarchy it is not clear how paravirtualized network cards will be named.

Suggestions for improvement: 
We should be explicit here. The correct answer is scheme 2 (PCIe card naming convention - ens) but please verify this this is just my wild guess.


Additional information: 
In RHEL7 consitent naming for virtio-net driver must be explicitly enabled: https://access.redhat.com/solutions/3219091

Comment 8 Lukáš Nykrýn 2019-05-06 08:51:29 UTC

But to be honest, I don't think we should change the doc here. It does not matter if the device is virtualized or not, the rules are still the same. And the net.ifnames=1 is just an ugly hack. Maybe it is fine if it is just documented in the KB.