| 2017-03-06 21:48:16 |
Mathieu Trudel-Lapierre |
bug |
|
|
added bug |
| 2017-03-06 21:49:00 |
Mathieu Trudel-Lapierre |
bug |
|
|
added subscriber Ubuntu Release Team |
| 2017-03-06 22:32:34 |
Mathieu Trudel-Lapierre |
attachment added |
|
Build and test results https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1670495/+attachment/4832589/+files/netplan-build.txt |
|
| 2017-03-08 16:46:31 |
Mathieu Trudel-Lapierre |
description |
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)
- support for configuring a device MTU.
- 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. |
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. |
|
| 2017-03-08 20:34:46 |
Steve Langasek |
nplan (Ubuntu): status |
New |
Triaged |
|
| 2017-03-18 20:09:55 |
Launchpad Janitor |
nplan (Ubuntu): status |
Triaged |
Fix Released |
|
| 2017-05-12 21:22:36 |
Mathieu Trudel-Lapierre |
description |
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. |
[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.
---
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. |
|
| 2017-05-18 21:59:45 |
Brian Murray |
nplan (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2017-05-18 21:59:47 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-05-18 21:59:51 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2017-05-18 21:59:56 |
Brian Murray |
tags |
|
verification-needed |
|
| 2017-06-07 22:59:03 |
Mathieu Trudel-Lapierre |
description |
[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.
---
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. |
[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]
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. |
|
| 2017-06-07 23:00:10 |
Mathieu Trudel-Lapierre |
nominated for series |
|
Ubuntu Yakkety |
|
| 2017-06-07 23:00:10 |
Mathieu Trudel-Lapierre |
bug task added |
|
nplan (Ubuntu Yakkety) |
|
| 2017-06-13 18:32:07 |
Brian Murray |
nplan (Ubuntu Yakkety): status |
New |
Fix Committed |
|
| 2017-06-16 18:29:32 |
Mathieu Trudel-Lapierre |
tags |
verification-needed |
verification-done-xenial verification-yakkety |
|
| 2017-06-16 18:31:03 |
Mathieu Trudel-Lapierre |
description |
[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]
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. |
[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. |
|
| 2017-06-19 14:08:10 |
Mathieu Trudel-Lapierre |
tags |
verification-done-xenial verification-yakkety |
verification-done-xenial verification-done-yakkety |
|
| 2017-06-27 14:45:29 |
Launchpad Janitor |
nplan (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-06-27 14:46:03 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-06-27 15:46:26 |
Launchpad Janitor |
nplan (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2018-08-17 13:11:45 |
Marcus Wellnitz |
bug |
|
|
added subscriber Marcus Wellnitz |
