On Mon, Dec 14, 2015, at 01:00 PM, Kushal Das wrote: > This email is to resume the discussion on putting Networkd as network > stack in Fedora Cloud Atomic and base images. FWIW, my opinion on this from the Atomic Host perspective hasn't really changed since: https://lists.fedoraproject.org/archives/list/cloud%40lists.fedoraproject.org/message/IGJQ3USBSAY3A3Q3QL4I3MYN6KPXTRB6/ A cloud *guest* only is one usually simple case, but there are a lot of interacting cases on baremetal: libvirt, firewalld, etc. Not to mention the ongoing thread on DNSSEC. Plus Anaconda and Cockpit, among others. There's just already enough on the Atomic Host plate for cluster, container and rel-eng/testing etc. issues that I can't see adding trying to drive networkd as being worth the benefit right now personally. Hm, and now that I look, the change to use dhcp=internal didn't actually get propagated forward from f22. Both NM and dracut-network Require: dhclient at present, otherwise I think NM would automatically use dhcp=internal. _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
