systemd and changes
dcbw at redhat.com
Thu Sep 2 15:40:21 UTC 2010
On Fri, 2010-08-27 at 19:58 +0100, Mark Chappell wrote:
> On 27/08/2010, Tomasz Torcz <tomek at pipebreaker.pl> wrote:
> > NM doesn't (yet?) support:
> > - bridges: https://bugzilla.redhat.com/show_bug.cgi?id=558982
> > - vlans: https://bugzilla.redhat.com/show_bug.cgi?id=492377
> That would explain why I couldn't figure out how to do it :)
When NM does support these, it will support these using the normal ifcfg
file key/value formats which are documented in the 'initscripts' package
as they always have been. There's nothing special about ifcfg files
that NetworkManager really changes; we've gone to great effort to
interpret ifcfg files almost exactly like ifup/ifdown interpret them.
So, if you want to use a CLI to create system-wide network connections,
you use 'vi' or 'nano' or 'emacs' and write an ifcfg file like you
always did. Nothing has changed here.
Then you ifup them. Or you use nmcli to activate them. The point is
that when creating or activating/deactivating connections that NM
supports your workflow should not really change.
> > Nb. there is following feature:
> > http://fedoraproject.org/wiki/Features/Shared_Network_Interface
> > which is about cooperation between NM and Fedora virtualisation stuff
> > and includes bridging support.
> But again SFAICT requires manual intervention when creating a new
> server. Like I said, the less I have to do to bring up a new server
> the better.
More information about the devel