On Thu, Mar 19, 2015, at 01:09 PM, Matthew Miller wrote:
On Thu, Mar 19, 2015 at 12:47:22PM -0400, Dusty Mabe wrote:
I would suggest that we adopt the approach that Fedora Cloud Base
takes by just having the Network service enabled. This would also mean
we can pull the NetworkManager
On Thu, Mar 19, 2015, at 12:56 PM, Matt Micene wrote:
I'd be in favor of pulling NetworkManager. It still seems that network is
the way for server class systems to handle networking
It's not that simple, at least for Atomic, because the *exact same* tree
in Fedora 22 can also be deployed
On Thu, Mar 19, 2015 at 06:27:13PM -0400, Colin Walters wrote:
On Thu, Mar 19, 2015, at 12:56 PM, Matt Micene wrote:
I'd be in favor of pulling NetworkManager.? It still seems that network is
the way for server class systems to handle networking
It's not that simple, at least for
On Thu, Mar 19, 2015 at 12:47:22PM -0400, Dusty Mabe wrote:
Both NetworkManager and network systemd services are enabled in F21
and F22 Atomic and this could be causing some issues we are seeing.
We should probably open a BZ for this. If no one objects I will make
one.
Opened this BZ:
I'd be in favor of pulling NetworkManager. It still seems that network is
the way for server class systems to handle networking.
-Matt M
On Thu, Mar 19, 2015 at 12:47 PM, Dusty Mabe du...@dustymabe.com wrote:
Both NetworkManager and network systemd services are enabled in F21
and F22 Atomic
On Thu, Mar 19, 2015 at 12:47:22PM -0400, Dusty Mabe wrote:
I would suggest that we adopt the approach that Fedora Cloud Base
takes by just having the Network service enabled. This would also mean
we can pull the NetworkManager packages out of atomic and make the
image smaller.
I'm in favor.
Both NetworkManager and network systemd services are enabled in F21
and F22 Atomic and this could be causing some issues we are seeing.
We should probably open a BZ for this. If no one objects I will make
one.
I would suggest that we adopt the approach that Fedora Cloud Base
takes by just
