<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2014-04-14 22:56 GMT+02:00 Matthew Miller <span dir="ltr"><<a href="mailto:mattdm@fedoraproject.org" target="_blank">mattdm@fedoraproject.org</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">> > ** Replace NetworkManager, etc. with systemd-networkd.<br>
<snip><br></div>
Also, I know you know this but just as a general clarification: the cloud<br>
image isn't currently using NetworkManager anyway but is using the good ol'<br>
network initscripts.<br></blockquote><br></div>I don't think we can, or should, have three separate network configuration systems in Fedora at the same time. We already know how long and painful the migration to NetworkManager has been—and AFAICS networkd doesn't support any of the icfg-* files, unlike NetworkManager, so it would mean a <i>more</i> painful migration.<br>
<br></div><div class="gmail_extra">Also see the recent caching DNS / DNSSEC discussions, which effectively move the DNS resolver configuration away from /etc/resolv.conf to a NetworkManager API.<br><br></div><div class="gmail_extra">
With what I know so far, this would only make sense to me if the Cloud images were explicitly designed to run in a very specific network environment (say, everything via DHCP, no VPNs, no IPSec, no bridges, nothing else), and telling both users and application developers not to touch the configuration in any way.<br>
</div><div class="gmail_extra"> Mirek<br></div></div>