We slimmed down the Server default configuration to remove some NM packages we don't need, but we also excluded the relatively-new NetworkManager-team package which provides support for "team" devices (a newer kind of user-space bonding interface). This is probably worth including in the default configuration, since a sizeable percentage of real-world servers will want to bond their network devices together for better throughput.
If the Server WG agrees, I'll patch comps.xml.
On Wed, 20 Apr 2016 14:48:46 -0400 Stephen Gallagher sgallagh@redhat.com wrote:
We slimmed down the Server default configuration to remove some NM packages we don't need, but we also excluded the relatively-new NetworkManager-team package which provides support for "team" devices (a newer kind of user-space bonding interface). This is probably worth including in the default configuration, since a sizeable percentage of real-world servers will want to bond their network devices together for better throughput.
If the Server WG agrees, I'll patch comps.xml.
+1 from me... having team there would be helpful
kevin
On Wed, Apr 20, 2016 at 7:48 PM, Stephen Gallagher sgallagh@redhat.com wrote:
We slimmed down the Server default configuration to remove some NM packages we don't need, but we also excluded the relatively-new NetworkManager-team package which provides support for "team" devices (a newer kind of user-space bonding interface). This is probably worth including in the default configuration, since a sizeable percentage of real-world servers will want to bond their network devices together for better throughput.
If the Server WG agrees, I'll patch comps.xml.
I think it's worth including but it's not needed to do bonding, you can still do the old school bonding without it.
Peter
On 04/20/2016 01:51 PM, Peter Robinson wrote:
On Wed, Apr 20, 2016 at 7:48 PM, Stephen Gallagher sgallagh@redhat.com wrote:
We slimmed down the Server default configuration to remove some NM packages we don't need, but we also excluded the relatively-new NetworkManager-team package which provides support for "team" devices (a newer kind of user-space bonding interface). This is probably worth including in the default configuration, since a sizeable percentage of real-world servers will want to bond their network devices together for better throughput.
If the Server WG agrees, I'll patch comps.xml.
I think it's worth including but it's not needed to do bonding, you can still do the old school bonding without it.
I'm a +1 on the change.
-- Major Hayden
On Wed, 2016-04-20 at 14:06 -0500, Major Hayden wrote:
On 04/20/2016 01:51 PM, Peter Robinson wrote:
On Wed, Apr 20, 2016 at 7:48 PM, Stephen Gallagher sgallagh@redhat.com wrote:
We slimmed down the Server default configuration to remove some NM packages we don't need, but we also excluded the relatively-new NetworkManager-team package which provides support for "team" devices (a newer kind of user-space bonding interface). This is probably worth including in the default configuration, since a sizeable percentage of real-world servers will want to bond their network devices together for better throughput.
If the Server WG agrees, I'll patch comps.xml.
I think it's worth including but it's not needed to do bonding, you can still do the old school bonding without it.
I'm a +1 on the change.
+1
On 04/20/2016 03:12 PM, Simo Sorce wrote:
On Wed, 2016-04-20 at 14:06 -0500, Major Hayden wrote:
On 04/20/2016 01:51 PM, Peter Robinson wrote:
On Wed, Apr 20, 2016 at 7:48 PM, Stephen Gallagher sgallagh@redhat.com wrote:
We slimmed down the Server default configuration to remove some NM packages we don't need, but we also excluded the relatively-new NetworkManager-team package which provides support for "team" devices (a newer kind of user-space bonding interface). This is probably worth including in the default configuration, since a sizeable percentage of real-world servers will want to bond their network devices together for better throughput.
If the Server WG agrees, I'll patch comps.xml.
I think it's worth including but it's not needed to do bonding, you can still do the old school bonding without it.
I'm a +1 on the change.
+1
OK, I went ahead and added the package to the default set. Should show up on the Beta media.
On Thu, Apr 21, 2016 at 10:09 AM, Stephen Gallagher sgallagh@redhat.com wrote:
OK, I went ahead and added the package to the default set. Should show up on the Beta media.
belated +1, seems like a good idea to me.
On 04/20/2016 01:51 PM, Peter Robinson wrote:
On Wed, Apr 20, 2016 at 7:48 PM, Stephen Gallagher sgallagh@redhat.com wrote:
We slimmed down the Server default configuration to remove some NM packages we don't need, but we also excluded the relatively-new NetworkManager-team package which provides support for "team" devices (a newer kind of user-space bonding interface). This is probably worth including in the default configuration, since a sizeable percentage of real-world servers will want to bond their network devices together for better throughput.
If the Server WG agrees, I'll patch comps.xml.
I think it's worth including but it's not needed to do bonding, you can still do the old school bonding without it.
Peter _______________________________________________ server mailing list server@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/server@lists.fedoraproject.org
+1 from me.
While old school bonding is still available using the kernel module, teaming provides a lot more functionality[1]. To name a few:
D-Bus interface Port Priorities Separate per-port link monitoring IPv6 link monitoring LACP active and load balance modes
[1]http://rhelblog.redhat.com/2014/06/23/team-driver/
server@lists.fedoraproject.org
-
Dan Mossor -
Jon Stanley -
Kevin Fenzi -
Major Hayden -
Peter Robinson -
Simo Sorce -
Stephen Gallagher