On Fri, Oct 4, 2019 at 6:26 AM Jim Perrin <jperrin at centos.org> wrote:> > > On 10/3/19 2:42 PM, Jerry Geis wrote: > > I have need to use the old network-scripts and not NetworkManager. > > Why? I'd like to understand more about the use case where this is a > requirement. > > >One example we have is qemu virtual machine hosts where setting up the bridge in the ifcfg scripts is easier and avoiding NetworkManager messing things up in a non-intuitive way is critical. Also, we have 150+ machines with fixed IP addresses, always-on connections, and no wireless. Having NetworkManager do seemingly random things is not desirable. FWIW we disable NetworkManager with systemctl in our potinstall kickstart scripts and it seems to do what we want. --> Jim Perrin > The CentOS Project | http://www.centos.org > twitter: @BitIntegrity | GPG Key: FA09AD77 > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >-- *Matt Phelps* *Information Technology Specialist, Systems Administrator* (Computation Facility, Smithsonian Astrophysical Observatory) Center for Astrophysics | Harvard & Smithsonian 60 Garden Street | MS 39 | Cambridge, MA 02138 email: mphelps at cfa.harvard.edu cfa.harvard.edu | Facebook <http://cfa.harvard.edu/facebook> | Twitter <http://cfa.harvard.edu/twitter> | YouTube <http://cfa.harvard.edu/youtube> | Newsletter <http://cfa.harvard.edu/newsletter>
On 10/4/19 2:27 PM, Phelps, Matthew wrote:> On Fri, Oct 4, 2019 at 6:26 AM Jim Perrin <jperrin at centos.org> wrote: > >> >> >> On 10/3/19 2:42 PM, Jerry Geis wrote: >>> I have need to use the old network-scripts and not NetworkManager. >> >> Why? I'd like to understand more about the use case where this is a >> requirement. >> >> >> > One example we have is qemu virtual machine hosts where setting up the > bridge in the ifcfg scripts is easier and avoiding NetworkManager messing > things up in a non-intuitive way is critical. > > Also, we have 150+ machines with fixed IP addresses, always-on connections, > and no wireless. Having NetworkManager do seemingly random things is not > desirable. > > FWIW we disable NetworkManager with systemctl in our potinstall kickstart > scripts and it seems to do what we want. >+1 Bridge for VM's is main reason I hate NM. I now mess with both NM and br0 controled by network because I use Windows VM on my laptop. As soon as you disconnect LAN cable your eth and bridge connection are gone and stupid KVM can not recover and reconnect to newly activated bridge when you return LAN cable, even only a second later... -- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe StarOS, Mikrotik and CentOS/RHEL/Linux consultant
Once upon a time, Ljubomir Ljubojevic <centos at plnet.rs> said:> Bridge for VM's is main reason I hate NM. I now mess with both NM and > br0 controled by network because I use Windows VM on my laptop. As soon > as you disconnect LAN cable your eth and bridge connection are gone and > stupid KVM can not recover and reconnect to newly activated bridge when > you return LAN cable, even only a second later...See the NetworkManager-config-server package. -- Chris Adams <linux at cmadams.net>
On Fri, Oct 04, 2019 at 08:27:08AM -0400, Phelps, Matthew wrote:> Also, we have 150+ machines with fixed IP addresses, always-on connections, > and no wireless. Having NetworkManager do seemingly random things is not > desirable.I mention this every time people bash NetworkManager on servers. I have NM set up on all our servers. Why? Because the legacy network-scripts service tries to bring up the interface once on boot. We had a power outage to the entire floor of our datacenter and the linux systems booted faster than the network infrastructure. Any linux system not using NM tried to bring up the interface, saw that there was no connection, and gave up. We had to physically reboot those hosts. Systems running NM dynamically brought up their interface when the interface became active. -- Jonathan Billings <billings at negate.org>