In https://blueprints.launchpad.net/ubuntu/+spec/foundations-w-networkd-vs-ifupdown we want to provide networkd as a viable option for Ubuntu, in particular server/cloud land. This requires some integration with existing packages, in particular calling the /etc/network/if-up.d/ and if-post-down.d/ scripts, similar to what NetworkManager does.
I would like to land this in wily still, so that people can experiment it and we still have some time to tweak it for 16.04 LTS:
As we don't currently use (or even advertise) networkd in Ubuntu, the risk of this is very low IMHO. The main regression risk is if that would somehow influence/break interfaces managed by ifupdown or NetworkManager, but the above changes test if the interface is managed by networkd.
In https:/ /blueprints. launchpad. net/ubuntu/ +spec/foundatio ns-w-networkd- vs-ifupdown we want to provide networkd as a viable option for Ubuntu, in particular server/cloud land. This requires some integration with existing packages, in particular calling the /etc/network/ if-up.d/ and if-post-down.d/ scripts, similar to what NetworkManager does.
I would like to land this in wily still, so that people can experiment it and we still have some time to tweak it for 16.04 LTS:
http:// anonscm. debian. org/cgit/ pkg-systemd/ systemd. git/commit/ ?id=27f7cc9f9f3 2
As we don't currently use (or even advertise) networkd in Ubuntu, the risk of this is very low IMHO. The main regression risk is if that would somehow influence/break interfaces managed by ifupdown or NetworkManager, but the above changes test if the interface is managed by networkd.