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 having the Network service enabled. This would also mean we can pull the NetworkManager packages out of atomic and make the image smaller.
Thoughts?
Dusty
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 dusty@dustymabe.com 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.
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.
Thoughts?
Dusty _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
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 bare metal, and NetworkManager
handles far more networking types than the legacy network package.
Further on bare metal, Anaconda presently only knows how to interact
with NetworkManager.
Clearly 3 networking subsystems is not long term sustainable; the good
news is that NetworkManager and networkd are sharing some code,
NetworkManager is getting smaller, etc. No one is investing in the legacy
network package though AFAIK.
The "mainline" cloud image though is a different case - I'm sure networkd
can be quite usable there, particularly if one doesn't care about the legacy
initscripts config file formats.
Given that, I'd propose for now:
@@ -19,7 +21,8 @@ firewall --disabled
bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8"
network --bootproto=dhcp --device=link --activate --onboot=on
-services --enabled=network,sshd,rsyslog,cloud-init,cloud-init-local,cloud- config,cloud-final
+services --disabled=network
+services --enabled=sshd,rsyslog,cloud-init,cloud-init-local,cloud- config,cloud-final
zerombr
clearpart --all
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 Atomic, because the *exact same* tree in Fedora 22 can also be deployed on bare metal, and NetworkManager handles far more networking types than the legacy network package.
You have a good point, but just because we have to have NetworkManager in the image does it mean we have to use it? I think we get some benefit (testing overlap, etc) by having the Fedora Atomic Cloud and Fedora Cloud Base images being pretty similar.
If the Cloud Base moves to NetworkManager then I guess this point would be moot. If it moves to systemd-networkd then I would propose that the Fedora Atomic Cloud image do the same.
Dusty
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. For F23, we should look at NetworkManager (or _possibly_ systemd-networkd) again — https://bugzilla.redhat.com/show_bug.cgi?id=863515 should be in place, so nothing will need to persist, and NetworkManager should be using the new lighter-weight dhcp client from systemd-networkd, which is a big win in runtime memory use.
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 packages out of atomic and make the image smaller.
I'm in favor. For F23, we should look at NetworkManager (or _possibly_ systemd-networkd) again — https://bugzilla.redhat.com/show_bug.cgi?id=863515 should be in place, so nothing will need to persist, and NetworkManager should be using the new lighter-weight dhcp client from systemd-networkd,
We can do this latter bit right now. Just tested and it works: https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?h=f22&id=c...
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:
-
Colin Walters -
Dusty Mabe -
Matt Micene -
Matthew Miller