No documented way to pass in bond or bridge paramters
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Netplan |
Fix Released
|
Medium
|
Mathieu Trudel-Lapierre | ||
nplan (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
Undecided
|
Unassigned | ||
Zesty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Documentation is important for users to know how to write the required configuration file for bond or bridge device parameters.
[Test case]
- Run nplan integration tests on the release
- Validate that netplan generate && netplan apply alone, without config, behave as expected (no result)
- Validate that netplan generate && netplan apply with minimal config writes /run/NetworkMan
- Validate that netplan generate && netplan apply works with any existing configuation.
- Validate that documentation shipped with netplan includes information about the allowed parameters for bond and bridge devices (see /usr/share/
[Regression potential]
This is a new feature related to bond and bridge device parameters and support for these interface types. Existing configurations of bond/bridge devices that are "unconfigured", not including the extra parameters should not change in pre-existing behavior (for instance, bridge priority should not change by upgrading netplan). Existing bond and bridge configurations should continue to be brought up correctly.
---
According to the current documentation[1], there is no way to set bond or bridge parameters. This is a requirement for the MAAS use case.
MAAS passes these parameters in the v1 YAML the same way as they are represented in /etc/network/
br0:
params:
bridge_stp: on
...
bond0:
params:
bond-mode: 4
(Note the quirk there with '-' being used for the bond and '_' for the bridge; this is due to to an inconsistency regarding the /e/n/i syntax.)
I'm tentatively thinking of passing them in the same way, to prevent information loss. But perhaps this could be standardized; a 'params' dictionary could be used for generic OS or renderer-specific settings where there is no guarantee of support, but netplan could standardize commonly-used settings and present them in an "official" after they each parameter has been fully specified.
Changed in netplan: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Mathieu Trudel-Lapierre (cyphermox) |
Changed in netplan: | |
status: | In Progress → Fix Committed |
description: | updated |
description: | updated |
Changed in nplan (Ubuntu Zesty): | |
status: | New → Fix Released |
This landed in nplan 0.19:
nplan (0.19) zesty; urgency=medium
* Add support for unordered definition of network devices: you can now
specify a virtual devices before their member devices. (LP: #1670495)
* Allow setting up the STP state for a bridge. (LP: #1665088)
* Document bond/bridge parameters support. (LP: #1664702)