Wondering if I can get some input how everyone is dealing with these new network naming conventions in RHEL 7:
https://access.redhat.com/documentat...ce_Naming.html
When I have a NIC like eno16777736 is very ugly. Something like enp5s0 looks better but it's still uglier. Ubuntu kept them consistent at least in the various server versions it had which is good. When I login to meetings and have to specify which NIC fails I have to read this long thing out 'e-n-o-1-6-7-7-7-7-3-6' sounds alot worse then 'e-t-h-0'. Makes for longer problem resolution in the least. So reading that page above from RedHat, it could be any of the 5 different naming conventions, which in itself is very unpredictable. How do you guy's handle it? I rename it to the old way and use UDEV which seems alot better since a MAC won't change. And once set, I never have to touch it again. Earlier I could rely that eth0 pointed to some NIC and it looked the same on both VM's and Physicals making it easy for automation etc now it could be any of the 5 naming conventions.
Why not simply attach the same eth0 to the same physical interface on each reboot based on the hardware profile instead of incorporating a hard to remember random string in the name itself? ( It's kind of like saying that putting triangles instead of wheels on cars makes more sense because we can get up to 33% rubber contact with the road instead of 2% - 5% of a round tire's circumference and the more rubber contacts the road, the better the breaking distance. True, but we won't get anywhere because we ignore the usability that was aimed for with that. )
So I'm wondering how the rest of the community handles this? Do you rename it or do you leave it and just work with it as-is?
Cheers,
DH
