On Thu, Mar 19, 2015, at 12:56 PM, Matt Micene wrote:

I'd be in favor of pulling NetworkManager. It still seems that network is the way for "server" class systems to handle networking

It's not that simple, at least for Atomic, because the *exact same* tree

in Fedora 22 can also be deployed on bare metal, and NetworkManager

handles far more networking types than the legacy network package.

Further on bare metal, Anaconda presently only knows how to interact

with NetworkManager.

Clearly 3 networking subsystems is not long term sustainable; the good

news is that NetworkManager and networkd are sharing some code,

NetworkManager is getting smaller, etc. No one is investing in the legacy

network package though AFAIK.

The "mainline" cloud image though is a different case - I'm sure networkd

can be quite usable there, particularly if one doesn't care about the legacy

initscripts config file formats.

Given that, I'd propose for now:

@@ -19,7 +21,8 @@ firewall --disabled

bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8"

network --bootproto=dhcp --device=link --activate --onboot=on

-services --enabled=network,sshd,rsyslog,cloud-init,cloud-init-local,cloud-config,cloud-final

+services --disabled=network

+services --enabled=sshd,rsyslog,cloud-init,cloud-init-local,cloud-config,cloud-final

zerombr

clearpart --all