[Expired for netplan because there has been no activity for 60 days.]
** Changed in: netplan
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664846
Title:
[Wishl
please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664846
Title:
[Wishlist] Support for tea
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664846
Title:
[W
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.
--
You received this bug notification because you are a member of Ubuntu
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-ho
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
