Comment 2 for bug 834012

I am untargeting this bug from Essex-1.

The following bug is a prerequisite for solving this bug: https://bugs.launchpad.net/quantum/+bug/837535

Technically, the solution to this bug is straightforward (see attached branch). However we are relying on the fact that a single call to get_network_details return all the ports for the network as well in an attribute called net-ports.

Unfortunately, this behaviour breaks what is stated in Quantum_plugin_base.

From quantum_plugin_base.QuantumPluginBase.get_network_details:

        :returns: a sequence of mappings with the following signature:
                    {'net-id': uuid that uniquely identifies the
                                particular quantum network
                     'net-name': a human-readable name associated
                                 with network referenced by net-id
                     'net-ifaces': ['vif1_on_network_uuid',
                                    'vif2_on_network_uuid',...,'vifn_uuid']
                    }

So, in order to push this change to Gerrit I first need permission from the community to change the documentation of quantum_plugin_base to:

        :returns: a sequence of mappings with the following signature:
                    {'net-id': uuid that uniquely identifies the
                                particular quantum network
                     'net-name': a human-readable name associated
                                 with network referenced by net-id
                     'net-ports': a list of port resources describing the network's ports
                                           and attached interfaces
                    }

I don't see this as samething we need to decide ASAP, but it would be great if we can get the ball rolling.