** Description changed: [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/NetworkManager/conf.d/10-globally-managed-devices.conf - 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/doc/netplan/netplan.html) [Regression potential] - Any failure to work with existing configuration should be considered a regression. Any new failure of the test suite would be a regression. + 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/interfaces[2], inside a 'params' dictionary. This allows interface type specific settings such as spanning-tree and bonding modes to be specified, such as: 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. [1]: https://git.launchpad.net/netplan/tree/doc/netplan.md [2]: https://wiki.debian.org/NetworkConfiguration
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664702 Title: No documented way to pass in bond or bridge paramters To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1664702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
