[ovirt-users] Re: about the network name rules on CentOS/Redhat 8 and the cloud-init network interface name

On Tue, Aug 24, 2021 at 11:17 AM Tommy Sway <sz_cuitao(a)163.com&gt; wrote: > Everybody is good! > > As you all know, to use the client's network card name in cloud-init, you > must fill in the exact name of the network card interface. > > This was easy in version 7 and before, which usually started with EN0. > > > > After version 8, however, the naming conventions for network cards > changed a lot. In my own test environment, for example, I started with ENS3. > > I'm not sure what naming convention it uses, which would make it > impossible to specify nic information using cloud-init. > > > > Could you help me explain how to deal with this problem? > > Thank you very much! > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/L6LPAKYOUYP... > Hi, this is called Predictable Network Names and it is the default policy for net interface naming in el8. There are a couple tricks you can do to mitigate that, you can disable it, or predict the name based on your configuration PCI slot etc [0]. There is a documentation for RHEL that explains it [1]. There is also another option and that's using a custom udev rule to assign whatever name you want based on some identifiers like MAC, PCI addr etc. Hopefully this helps. Best regards, Ales

-- Ales Musil Software Engineer - RHV Network Red Hat EMEA <https://www.redhat.com> amusil(a)redhat.com IM: amusil <https://red.ht/sig>