2014-04-21 16:18 GMT+02:00 Matthew Miller :
> On Thu, Apr 17, 2014 at 10:30:48PM +0200, Miloslav Trmač wrote:
> > Writing too fast... you were actually arguing for a situation "2 used by
> > default + 1 used but not used by default" I think. In that case your
> > argument is right but it's my tur
On Tue, Apr 22, 2014 at 06:01:31AM +0200, Lennart Poettering wrote:
> Note that it should be relatively straight-forward to implement a
> generator (even in shell...) that generates native systemd-networkd
> configuration snippets from ifcfg files at runtime (or upgrade-time),
> similar to how we c
On Tue, 22.04.14 06:01, Lennart Poettering (mzerq...@0pointer.de) wrote:
> > environment (say, everything via DHCP, no VPNs, no IPSec, no bridges,
> > nothing else), and telling both users and application developers not to
>
> Note that networkd supports static configuration, bridges and some for
On Thu, 17.04.14 01:24, Miloslav Trmač (m...@volny.cz) wrote:
> 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 an
On Thu, Apr 17, 2014 at 10:30:48PM +0200, Miloslav Trmač wrote:
> Writing too fast... you were actually arguing for a situation "2 used by
> default + 1 used but not used by default" I think. In that case your
> argument is right but it's my turn to not accept your premise :) networkd
> was intro
2014-04-17 22:27 GMT+02:00 Miloslav Trmač :
> 2014-04-17 21:54 GMT+02:00 Matthew Miller :
>
> 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 s
2014-04-17 21:54 GMT+02:00 Matthew Miller :
> 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 a
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%
2014-04-17 1:42 GMT+02:00 Matthew Miller :
> On Thu, Apr 17, 2014 at 01:24:50AM +0200, Miloslav Trmač wrote:
> > 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
>
> I think we'd stay at two,
On Thu, Apr 17, 2014 at 01:24:50AM +0200, Miloslav Trmač wrote:
> 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
I think we'd stay at two, basically -- right now, we have two in use
(NetworkMana
2014-04-14 22:56 GMT+02:00 Matthew Miller :
> > > ** Replace NetworkManager, etc. with systemd-networkd.
>
> Also, I know you know this but just as a general clarification: the cloud
> image isn't currently using NetworkManager anyway but is using the good ol'
> network initscripts.
>
I don't th
On Mon, Apr 14, 2014 at 04:15:50PM -0400, Bill Nottingham wrote:
> > ** Replace NetworkManager, etc. with systemd-networkd.
> > ** Make sure only just kernel-core, not kernel and kernel-drivers, is
> > installed (see the related change: Modular Kernel Packaging for Cloud [1]).
> > ** Make sure onl
Jaroslav Reznik (jrez...@redhat.com) said:
> == Scope ==
> As mentioned, there's really various changes that are quite independent of
> each other but share the common goal.
>
> * Proposal owners:
> ** Replace NetworkManager, etc. with systemd-networkd.
> ** Make sure only just kernel-core, not
13 matches
Mail list logo
