** Description changed:
[Impact]
Any complex configuration requiring layering of devices currently requires
that "lower" layers are defined above "upper" layers. Ordering of configuration
should not matter in netplan.
[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.
[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.
+ Netplan should continue applying pre-existing configuration successfully
despite the changes in the evaluation strategy for the configuration files.
---
-
I'd like to upload a new release of netplan; notable changes include:
- forward-definition support (the underlying ethernet devices of bridges and
bonds no longer need to be defined before the bridge or bond they are a member
of)
- add missing configuration knob for toggling STP for a bridge.
nplan is seeded on most flavors, but not used my default. It provides an
alternate way for people to configure their network devices.
** Also affects: nplan (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670495
Title:
[FFe] netplan with forward-definition support
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1670495/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
