Cisco nexus plugin port-binding table needs to be redesigned
Bug #1244777 reported by
Baodong (Robert) Li
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-cisco |
New
|
Undecided
|
Unassigned |
Bug Description
In the current implementation, the table cisco_nexusport
cisco_nexusport
id = sa.Column(
port_id = sa.Column(
vlan_id = sa.Column(
switch_ip = sa.Column(
instance_id = sa.Column(
There should be one-to-one mapping between entries in the table and neutron ports. However, based on the above definition, such relationship is not properly maintained. Instead, neutron port id should be used as the table's primary key. Such change will improve the plugin design and code.
tags: | added: cisco |
Changed in neutron: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
no longer affects: | neutron |
tags: | added: nexus |
To post a comment you must log in.
Also, the vlan_id should not be nullable. /review. openstack. org/#/c/ 55411/6/ neutron/ plugins/ cisco/db/ nexus_models_ v2.py
See the review comments here:
https:/