[cloud] #14: Investigate systemd-networkd

[Fedora Cloud Trac Tickets]

#14: Investigate systemd-networkd
------------------------------+--------------------------------
 Reporter:  mattdm            |       Owner:  janeznemanic
     Type:  task              |      Status:  new
 Priority:  normal            |   Milestone:  Fedora 21 (Alpha)
Component:  Cloud Base Image  |  Resolution:
 Keywords:                    |
------------------------------+--------------------------------

Comment (by gospo):

 Replying to [comment:3 janeznemanic]:
 > Report on my work.
 [...]
 >
 > I did some research on scripts in /etc/sysconfig/network-scripts. All
 those scripts depend on ifcfg-* files in the same directory. But systemd-
 networkd doesn't use ifcfg-* files. I removed ifcfg-* files and systemd-
 netword worked fine. I was also able to ping google. But if I tried to use
 for example ifup or ifdown script then that script failed. Because it
 couldn't source ifcfg-*. I think so, I might be wrong. Since ifup and
 ifdown are links to /usr/sbin/{ifup,ifdown} it might be possible to remove
 /usr/sbin/{ifup,ifdown}. But I haven't tested that so I'm not sure. I
 think we also don't need to use /etc/rc.d/init.d/network. I removed that
 file and networking worked fine with systemd-networkd.
 >
 > So to sum up. If systemd-networkd service is used it is possible in my
 opinion to remove scripts in /etc/sysconfig/network-scripts and
 /etc/rc.d/init.d/network script. Besides that it is possible to remove
 NetworkManager.
 >
 I took a quick look at the files from initscripts that are likely
 networking related.  It seems possible to remote these from initscripts
 core and (as Johannes suggested above) possibly break initscripts out into
 a new package.  If there was a desire to add the missing functionality to
 networkd that is currently in initscripts then the new initscripts package
 could be slowly whittled away to nothing when ppp and netconsole support
 are added to networkd (that appears to be the only missing functionality).

 /etc/NetworkManager
 /etc/NetworkManager/dispatcher.d
 /etc/NetworkManager/dispatcher.d/00-netreport
 /etc/networks
 /etc/ppp
 /etc/ppp/ip-down
 /etc/ppp/ip-down.ipv6to4
 /etc/ppp/ip-up
 /etc/ppp/ip-up.ipv6to4
 /etc/ppp/ipv6-down
 /etc/ppp/ipv6-up
 /etc/ppp/peers
 /etc/rc.d/init.d/netconsole
 /etc/rc.d/init.d/network
 /etc/sysconfig/netconsole
 /etc/sysconfig/network-scripts
 /etc/sysconfig/network-scripts/*
 /usr/bin/ipcalc
 /usr/lib/udev/rename_device
 /usr/lib/udev/rules.d/60-net.rules
 /usr/libexec/initscripts
 /usr/libexec/initscripts/legacy-actions
 /usr/sbin/ifdown
 /usr/sbin/ifup
 /usr/sbin/netreport
 /usr/sbin/ppp-watch
 /usr/sbin/usernetctl
 /usr/share/doc/initscripts/changes.ipv6
 /usr/share/doc/initscripts/ipv6-6to4.howto
 /usr/share/doc/initscripts/ipv6-tunnel.howto
 /usr/share/doc/initscripts/static-routes-ipv6
 /usr/share/man/man1/genhostid.1.gz
 /usr/share/man/man1/ipcalc.1.gz
 /usr/share/man/man1/netreport.1.gz
 /usr/share/man/man8/ifdown.8.gz
 /usr/share/man/man8/ifup.8.gz
 /usr/share/man/man8/ppp-watch.8.gz}}}


 > '''Thoughts? Suggestions? Ideas?'''
 >
 > One more thing that's been bothering me for a few days now. How does
 systemd name network interfaces when Fedora is run on top of different
 hypervisors? If xen or kvm is used how does systemd name network
 interfaces?

 Systemd will name the device based on the bus/device/function of the
 interfaces, so there could be some differences in the name chosen
 depending on the hypervisor used (since each hypervisor may chose a
 difference bus/dev/function for a given emulated interface.

-- 
Ticket URL: <https://fedorahosted.org/cloud/ticket/14#comment:5>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System