CentOS virt - Nov 2016 - CentOS-7 x86_64 AMIs and consistent network device naming

Hello,

Re:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/7.3_Release_Notes/bug_fixes_general_updates.html

Are there any upcoming plans for turning off the use of legacy interface
names in the next official CentOS 7.x AMI?

Currently, both the official RHEL 7.3 GA AMI and the latest available
official CentOS-7 x86_64 AMI use legacy interface names via either:

- "net.ifnames=0" kernel boot parameter
or
- "ln -vs /dev/null /etc/udev/rules.d/80-net-setup-link.rules"

As I'm setting up some automation which will use the official CentOS 7 AMI,
I'm wondering whether to switch on the new naming scheme manually and
pre-empt the switch over or wait until the official AMIs switch over.

Also, will the next CentOS 7 AMI start using NetworkManager instead of the
traditional ifcfg-* scripts?

Regards,
Jinesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos-virt/attachments/20161104/d6312764/attachment-0006.html>

On 04/11/16 11:18, Jinesh Choksi wrote:
> Hello,
> 
> Re:
>
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/7.3_Release_Notes/bug_fixes_general_updates.html
> 
> Are there any upcoming plans for turning off the use of legacy interface
> names in the next official CentOS 7.x AMI?
> 
> Currently, both the official RHEL 7.3 GA AMI and the latest available
> official CentOS-7 x86_64 AMI use legacy interface names via either:
> 
> - "net.ifnames=0" kernel boot parameter
> or
> - "ln -vs /dev/null /etc/udev/rules.d/80-net-setup-link.rules"
> 
> As I'm setting up some automation which will use the official CentOS 7
> AMI, I'm wondering whether to switch on the new naming scheme manually
> and pre-empt the switch over or wait until the official AMIs switch over.
> 
> Also, will the next CentOS 7 AMI start using NetworkManager instead of
> the traditional ifcfg-* scripts?

would making these changes not break the existing automation that folks
might have in place ?




-- 
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc

Jinesh,
I think centOS still stay on ifcfg-* fashsion. 
For network manager, it is optional for networking in CentOS.
For AMI, I think you should stay for a while until it is no longer present
in kernel.

Xlord
-----Original Message-----
From: centos-virt-bounces at centos.org [mailto:centos-virt-bounces at
centos.org]
On Behalf Of Karanbir Singh
Sent: Friday, November 4, 2016 9:23 PM
To: centos-virt at centos.org
Subject: Re: [CentOS-virt] CentOS-7 x86_64 AMIs and consistent network
device naming

On 04/11/16 11:18, Jinesh Choksi wrote:
> Hello,
> 
> Re:
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux
> /7-Beta/html/7.3_Release_Notes/bug_fixes_general_updates.html
> 
> Are there any upcoming plans for turning off the use of legacy 
> interface names in the next official CentOS 7.x AMI?
> 
> Currently, both the official RHEL 7.3 GA AMI and the latest available 
> official CentOS-7 x86_64 AMI use legacy interface names via either:
> 
> - "net.ifnames=0" kernel boot parameter or
> - "ln -vs /dev/null /etc/udev/rules.d/80-net-setup-link.rules"
> 
> As I'm setting up some automation which will use the official CentOS 7 
> AMI, I'm wondering whether to switch on the new naming scheme manually 
> and pre-empt the switch over or wait until the official AMIs switch over.
> 
> Also, will the next CentOS 7 AMI start using NetworkManager instead of 
> the traditional ifcfg-* scripts?

would making these changes not break the existing automation that folks
might have in place ?




--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
_______________________________________________
CentOS-virt mailing list
CentOS-virt at centos.org
https://lists.centos.org/mailman/listinfo/centos-virt