[Wishlist] Support for teaming driver

Bug #1664846 reported by Mike Pontillo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Netplan
Expired
Wishlist
Unassigned
systemd (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

The MAAS team is supporting a customer who is using the 'teaming' driver rather than the 'bonding' driver. This is essentially a bonding driver which also delivers some additional features, and has additional userspace runtime control.

Netplan should allow for bonds to be configured with the teaming driver in addition to the bonding driver.

summary: - Support for teaming driver
+ [Wishlist] Support for teaming driver
Changed in netplan:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Is this really supported using MAAS right now? AIUI, there wouldn't be anything in ifupdown to do this.

This is going to need some engineering effort. From what I can tell it is currently only working with NetworkManager (no support in systemd at all), and there is no netplan code to handle this yet (but that wouldn't necessarily be all that hard).

Revision history for this message
Steve Langasek (vorlon) wrote :

I guess lack of ifupdown support is worked around with {pre,post}-{up,down} scripts.

The first thing to do is figure out whether / how this needs to be represented in the network yaml. Is there a reason to treat this as a different kind/class of network config than a bond using the bonding driver? Or should the choice of bonding driver (bonding vs. teaming) be a decision made at a completely different level than netplan?

Once that's determined, we would need to work out how this can be represented in the networkd renderer. Opening a task on systemd for this.

Changed in netplan:
status: Triaged → Incomplete
Revision history for this message
Mike Pontillo (mpontillo) wrote :

If we decide to implement this (I think it's still a wishlist item), I would prefer it to be more of a 'preferred driver choice' type of option. That is, model it like a normal bond in the YAML, but have something like a "preferred-driver: teaming" or similar, with a way to pass in additional ad-hoc custom parameters for that driver. (Only options very specific to that particular driver should ever be used in this ad-hoc manner. Bonds should be modeled as generically as possible, with industry-standard options exposed in the generalized YAML.)

My $0.02.

Revision history for this message
Josh England (jjengla) wrote :

I'm curious if there has been any movement on this. We switched to using the 'team' driver over the 'bonding' driver some time ago. Having an abstracted network configuration capability through netplan would be very nice.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
Revision history for this message
Dan Streetman (ddstreet) wrote :

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for netplan because there has been no activity for 60 days.]

Changed in netplan:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.