group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1664702@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package nplan - 0.23~16.04.1

---------------
nplan (0.23~16.04.1) xenial; urgency=medium

  * Backport netplan 0.23 to 16.04. (LP: #1688632)

nplan (0.23) artful; urgency=medium

  * Do not unbind brcmfmac, interface will be gone. (LP: #1696162)

nplan (0.22) artful; urgency=medium

  * Add support for setting a custom MAC address on all device types.
    (LP: #1690388)
  * Improved MAC/vlan integration tests; thanks for Dimitri John Ledkov for the
    changes.

nplan (0.21) artful; urgency=medium

  [ Ryan Harper ]
  * Add support for setting MTU on a device. (LP: #1668693)

  [ Mathieu Trudel-Lapierre ]
  * Don't rebind Atheros AR9271; it would confuse the driver. (LP: #1672740)
  * debian/control: Add Conflicts: against netplan; the network 'plan' daemon.
    Both ship the same /usr/sbin/netplan. (LP: #1665842)

nplan (0.20) zesty; urgency=medium

  * tests/integration.py: increase timeout for integration tests (networkd and
    NetworkManager "wait-online" checks) to account for longer bring-up times
    when dealing with stacked virtual devices.

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)

nplan (0.18) zesty; urgency=medium

  * debian/tests/integration.py: in some cases 'iw reg get' may qualify the
    reg domain results with 'global'; we must not let that trip up tests when
    they are run on Ubuntu infrastructure vs. local tests.

nplan (0.17) zesty; urgency=medium

  * New release:
    - Add support for configuring bonds.
    - Add support for configuring bridges.

nplan (0.16) zesty; urgency=medium

  [ Martin Pitt ]
  * doc/example-config: Adjust "routes:" example.
    It does not make sense to make "routes:" a global thing, they should be
    tied to an interface so that the route is only set when the corresponding
    interface exists and is up, and the config is not split in two parts.
  * doc/netplan.md: Point out that NM does not support globbing (LP: #1631018)

  [ Mathieu Trudel-Lapierre ]
  * Fix coverage for src/netplan to be 100%, and fail if coverage falls below
    that mark again.
  * Add support for specifying routes.

nplan (0.15) zesty; urgency=medium

  * tests/generate.py: Fix PEP-8 error (newly detected by -proposed
    pycodestyle).

 -- Mathieu Trudel-Lapierre <cyphermox@xxxxxxxxxx>  Tue, 06 Jun 2017
17:19:10 -0700

** Changed in: nplan (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1664702

Title:
  No documented way to pass in bond or bridge paramters

Status in netplan:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released
Status in nplan source package in Yakkety:
  Fix Committed
Status in nplan source package in Zesty:
  Fix Released

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/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]
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1664702/+subscriptions