plugins do not comply with quantum_plugin_interface

Bug #837535 reported by Salvatore Orlando
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Won't Fix
Medium
Unassigned

Bug Description

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']
                    }

Plugins return a 'net-ports' attribute instead of net-ifaces.
The net-ports sequence describes id, state, and attachment for each port, where as the net-ifaces attribute requires a list of interface identifiers.
Quite interestingly, all the plugins behave in the same way.

Possible fixes:
1) Change the plugins to fulfill the spec of QuantumPluginBase
2) Change QuantumPluginBase and accept the current implementation in the plugins as "de facto" standard.

Fixing this bug is a prerequisite for Bug #834012. Targeting diablo-RBP for this reason.

Related branches

Changed in quantum:
milestone: none → diablo-rbp
importance: Undecided → Medium
Changed in quantum:
status: New → In Progress
assignee: nobody → Salvatore Orlando (salvatore-orlando)
Revision history for this message
Salvatore Orlando (salvatore-orlando) wrote :

Untargeting bug as it deserves discussion and clarification.

Changed in quantum:
milestone: diablo-rbp → none
Revision history for this message
Salvatore Orlando (salvatore-orlando) wrote :

Unassigning myself. Hopefully this will go away as part of the work Brad is currently doing.

Changed in quantum:
assignee: Salvatore Orlando (salvatore-orlando) → nobody
Revision history for this message
dan wendlandt (danwent) wrote :

Salv, did this bug get addressed by Brad's changes or is there still work required? Thanks.

Changed in quantum:
status: In Progress → New
Revision history for this message
dan wendlandt (danwent) wrote :

this is a v1 issue, and we need to focus on v2.

Changed in quantum:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.