Comment 17 for bug 1592811

So is the root comment just this:
  Spoke to Ryan Harper about this issue. These address are from LXD and per my observation and my conversation with Ryan, it looks like juju is not briding the "lxd containers with the base network adapter".

Some open questions about how things "should" work:

1) There are many cases of providers where this is just not allowed (most of the big clouds don't like extra MAC addresses in their network that aren't the machines that were explicitly provisioned.)
2) Where are the IP addresses getting assigned if we did bridge to the host adapter? Just DHCP provided addresses? Is this stable, standard practice with vSphere?
3) Because of (1) we *don't* default to bridging to the host adapter. We have had a couple of requests to do so (another request for it has to do with manually provisioned machines).

There is quite a bit of work to be done to make reasoned, determined choice to select a host device to bridge. Things to deal with what device when there is more than one device, etc. We don't currently track "spaces" in vSphere. If we implement that, and then have a better feel for whether we have an explicit location for where we get IP addresses (2), then it would be reasonable to bridge when we have an expectation for it to work.