Comment 15 for bug 1627037

After additional discussions we came to the conclusion that Juju should respect the same ideas that MAAS does. In MAAS, a nic is not "configured" until it has an IP address. Setting a fabric, or even a subnet, does not return that as "configured" in MAAS. It's still unconfigured.

Juju will not bridge all "configured" interfaces. If we want to question the definition of configured then we need to address it in our complete stack so that we're consistent and have a reasonable explanation of what users can expect as they put together our tools into a final solution.

The behavior seen in RC2 is expected, and we admit is not ideal for all cases, but we decided that it was better to be consistent and predictable and to work to get layer 2 support into Juju so that it can properly handle the additional cases that folks are looking to put into play.