On Thu, Apr 17, 2014 at 09:47:21PM +0200, Miloslav Trmač wrote:
> > (NetworkManager and initscripts) and one that's available but not used by
> > default anywhere (systemd-networkd). This would simply swap the status of
> > systemd-networkd and initscripts.
> Is NetworkManager already at the *100% complete* feature parity that would
> make this possible? (Keeping in mind that "possible" and "a good idea" are
> still not the same...)
I don't think I accept your premise here. 100% (possibly spread between
networkd and NetworkManager) would be necessary for dropping initscripts
completely, but that's not being proposed.
> > Yeah, as I've said elsewhere, I'd love to see a network unit generator
> > which takes traditional ifcfg-* files as input. I think we need
> > ifup/ifdown compatibility scripts, too.
> Would these be prerequisites to making the change?
ifup/ifdown are probably real prerequisites (some of the ec2 tools assume
their presence), and an ifcfg generator a high-value nice-to-have.
> > It is _largely_ the case that complex networking is done outside of the
> > guests and presented to the guests as simple interfaces. Usually that's
> > one device with DHCP, but there may be additional interfaces with DHCP
> > or static interfaces.
> Well, this particular possibility is strictly black/white—either the
> completely different configuration and API is exposed, or it isn't; if
> there are any alternatives to configure at all, it is exposed.
Not following you.
--
Matthew Miller -- Fedora Project -- <mattdm@xxxxxxxxxxxxxxxxx>
"Tepid change for the somewhat better!"
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
