[FFe] support lxc bridge configuration

[Scott Moser]

recent changes to lxd added configuration of the lxd bridge.
We'd like to enable that in cloud-init.

The change allows the user to put config in cloud-config that will basically map to the debconf keys and thus configure their lxd bridge and lxd init on first boot making it immediately useful.

it should be safe for regression in that if there is no lxd bridge config, no change in code path will be taken.

[Stéphane Graber (stgraber)]

Sounds good to me, it's not causing any change to existing users and LXD had a granted FFe for the lxdbr0 bits. Granted.

[Scott Moser (smoser)]

fix-commited in trunk at 1202

[Launchpad Janitor (janitor)]

This bug was fixed in the package cloud-init - 0.7.7~bzr1208-0ubuntu1

---------------
cloud-init (0.7.7~bzr1208-0ubuntu1) xenial; urgency=medium

  * New upstream snapshot.
    - phone_home: allow usage of fqdn (LP: #1566824) [Ollie Armstrong]
    - chef: straighten out validation_cert and validation_key (LP: #1568940)
    - skip bridges when generating fallback networking (LP: #1569974)
    - rh_subscription: only check subscription if configured (LP: #1536706)
    - SmartOS, CloudSigma: fix error when dmi data is not availble
      (LP: #1569469)
    - DataSourceNoCloud: fix check_instance_id when upgraded (LP: #1568150)
    - lxd: adds basic support for dpkg based lxd-bridge
      configuration. (LP: #1569018)
    - centos: Ensure that a resolve conf object is written as a string.
      (LP: #1479988)

 -- Scott Moser <email address hidden> Wed, 13 Apr 2016 13:19:03 -0400

[Scott Moser (smoser)]

This is fixed in cloud-init 0.7.7

[James Falcon (falcojr)]

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/2646