Verification-done on both xenial and yakkety:

I verified that netplan 0.23~ does correctly parse configuration in the
order described: where complex interfaces are defined before their
interface members in the YAML file.

** Tags removed: verification-needed
** Tags added: verification-done-xenial verification-yakkety

** 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.
+ - Validate that netplan generate && netplan apply works with complex 
configuration building a bridge or bond device, as defined before its interface 
members. A configuration such as the one below is a good example:
+ 
+ network:
+   version: 2
+   bridges:
+     br0:
+       interfaces: [ethbn1, ethbn2]
+       parameters:
+         forward-delay: 21
+       addresses: [ 10.10.10.1/24 ]
+   ethernets:
+     ens3:
+       addresses: [ 192.168.253.6/24 ]
+       gateway4: 192.168.253.1
+       mtu: 1500
+     ethbn1:
+       match:
+         macaddress: 52:54:00:31:01:5f
+     ethbn2:
+       match:
+         name: ens10
+ 
  
  [Regression potential]
  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.

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to