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

2021-08-24 Thread Tommy Sway 
Great!

 

Thank you!

 

 

 

From: Ales Musil  
Sent: Tuesday, August 24, 2021 7:00 PM
To: Tommy Sway 
Cc: users 
Subject: Re: [ovirt-users] about the network name rules on CentOS/Redhat 8 and 
the cloud-init network interface name

 

 

 

On Tue, Aug 24, 2021 at 12:59 PM Ales Musil mailto:amu...@redhat.com> > wrote:

 

 

On Tue, Aug 24, 2021 at 11:17 AM Tommy Sway mailto:sz_cui...@163.com> > 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@ovirt.org <mailto:users@ovirt.org> 
To unsubscribe send an email to users-le...@ovirt.org 
<mailto:users-le...@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/L6LPAKYOUYPMPH45D2PFJETNLXS6BMSJ/

 

 

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

 

 

Forgot the links:

 

[0] 
https://www.freedesktop.org/software/systemd/man/systemd.net-naming-scheme.html

[1] 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/consistent-network-interface-device-naming_configuring-and-managing-networking

 

-- 

Ales Musil 

Software Engineer - RHV Network 

 <https://www.redhat.com> Red Hat EMEA 

 <mailto:amu...@redhat.com> amu...@redhat.comIM: amusil 


 <https://red.ht/sig> 



-- 

Ales Musil 

Software Engineer - RHV Network 

 <https://www.redhat.com> Red Hat EMEA 

 <mailto:amu...@redhat.com> amu...@redhat.comIM: amusil 


 <https://red.ht/sig> 

 

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/UXCFKHVQE5FTS7GTSJDG6MGQEQOAGK3Q/

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

2021-08-24 Thread Ales Musil 
On Tue, Aug 24, 2021 at 11:17 AM Tommy Sway  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@ovirt.org
> To unsubscribe send an email to users-le...@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/L6LPAKYOUYPMPH45D2PFJETNLXS6BMSJ/
>


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 

amu...@redhat.comIM: amusil

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/Q72LY63WV66KFRSBHHFDBQLMCKZWF7BP/

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

2021-08-24 Thread Ales Musil 
On Tue, Aug 24, 2021 at 12:59 PM Ales Musil  wrote:

>
>
> On Tue, Aug 24, 2021 at 11:17 AM Tommy Sway  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@ovirt.org
>> To unsubscribe send an email to users-le...@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/L6LPAKYOUYPMPH45D2PFJETNLXS6BMSJ/
>>
>
>
> 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
>
>
Forgot the links:

[0]
https://www.freedesktop.org/software/systemd/man/systemd.net-naming-scheme.html
[1]
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/consistent-network-interface-device-naming_configuring-and-managing-networking


> --
>
> Ales Musil
>
> Software Engineer - RHV Network
>
> Red Hat EMEA 
>
> amu...@redhat.comIM: amusil
> 
>


-- 

Ales Musil

Software Engineer - RHV Network

Red Hat EMEA 

amu...@redhat.comIM: amusil

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/QQZWSGDHTBIQGNO7GKQZQG5AYUDJIIJX/