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
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1664846
Title:
[Wishlist] Support for teaming driver
Status in netplan:
Incomplete
Status in systemd package in Ubuntu:
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1664846/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
