CentOS - Mar 2017 - From Networkmanager to self managed configuration files

> The recommended configuration for EL7 is to use NetworkManager unless
> you have a very specific edge case preventing you from doing so:
>
The truth is a lot of us run servers that don't need to have their 
network "managed" by Networkmanager.

We just need to set an IP address, subnet mask, gateway, and DNS servers 
and we will never be changing that configuration ever again for the 
entire life of the server.
Any 3-4 line script that does the job is sufficient, servers don't need 
gimmicks, they're not going to be hotspotting on wireless networks, the 
cable goes in, the server enters production and that's it!

-- 
Regards,

Giles Coochey
+44 (0) 7584 634 135
+44 (0) 1803 529 451
giles at coochey.net

On Wed, 8 Mar 2017, Giles Coochey wrote:
> The truth is a lot of us run servers that don't need to have their
network
> "managed" by Networkmanager.
You're opting to have your network managed by a bunch of unloved legacy
scripts that you're advised to avoid using unless necessary, or you've
having
it managed by NetworkManager.  If you want to have it managing it this way,
you'll be writing your own scripts.
> We just need to set an IP address, subnet mask, gateway, and DNS servers
and
> we will never be changing that configuration ever again for the entire life
> of the server.
> Any 3-4 line script that does the job is sufficient, servers don't need
> gimmicks, they're not going to be hotspotting on wireless networks, the
cable
> goes in, the server enters production and that's it!
By 3-4 line script, I assume you mean the content of all the files in
/etc/sysconfig/network-scripts that aren't your ifcfg files?

jh

On 08/03/17 10:15, John Hodrien wrote:
> On Wed, 8 Mar 2017, Giles Coochey wrote:
>
>> The truth is a lot of us run servers that don't need to have their 
>> network
>> "managed" by Networkmanager.
>
> You're opting to have your network managed by a bunch of unloved legacy
> scripts that you're advised to avoid using unless necessary, or
you've
> having
> it managed by NetworkManager.  If you want to have it managing it this 
> way,
> you'll be writing your own scripts.
>
>> We just need to set an IP address, subnet mask, gateway, and DNS 
>> servers and we will never be changing that configuration ever again 
>> for the entire life of the server.
>> Any 3-4 line script that does the job is sufficient, servers don't 
>> need gimmicks, they're not going to be hotspotting on wireless 
>> networks, the cable goes in, the server enters production and
that's it!
>
> By 3-4 line script, I assume you mean the content of all the files in
> /etc/sysconfig/network-scripts that aren't your ifcfg files?
>
ifconfig enp0s25 192.168.0.1 netmask 255.255.255.0
route add default gw 192.168.0.254 enp0s25
echo nameserver 8.8.8.8 > /etc/resolv.conf
echo nameserver 8.8.4.4 >> /etc/resolv.conf

-- 
Regards,

Giles Coochey
+44 (0) 7584 634 135
+44 (0) 1803 529 451
giles at coochey.net

On 03/08/2017 01:57 AM, Giles Coochey wrote:
>
>> The recommended configuration for EL7 is to use NetworkManager unless
>> you have a very specific edge case preventing you from doing so:
>>
> The truth is a lot of us run servers that don't need to have their
> network "managed" by Networkmanager.
>
My experience was very difficult going to 7.2 to 7.3 because of a change 
in the behavior of NetworkManager with respect to IPv6 but once I had it 
figured out (thanks to people on this list) it worked out quite well and 
I kept NetworkManager.

But I certainly understand why some don't want to do that.

On 8 March 2017 at 11:15, Alice Wonder <alice at domblogger.net>
wrote:
> On 03/08/2017 01:57 AM, Giles Coochey wrote:
>>
>>
>>> The recommended configuration for EL7 is to use NetworkManager
unless
>>> you have a very specific edge case preventing you from doing so:
>>>
>> The truth is a lot of us run servers that don't need to have their
>> network "managed" by Networkmanager.
>>
>
> My experience was very difficult going to 7.2 to 7.3 because of a change in
> the behavior of NetworkManager with respect to IPv6 but once I had it
> figured out (thanks to people on this list) it worked out quite well and I
> kept NetworkManager.
>
> But I certainly understand why some don't want to do that.

That's fine Alice (and I remember your issue well with the minimally
documented change to stable-privacy by default for new systems ...
argh I still need to write up a blog article about that) but in this
case the person concerned isn't even using the network service, which
if legacy and semi-deprecated is still supported, but just doing a
ridiculous and unsupportable mini script (I'm guessing from rc.local?)
which doesn't handle pretty much any actual networking issue that may
come up - eg failed/delayed interface.