[OVSDB-379] Postman collection needs updating Created: 05/Oct/16  Updated: 02/May/19

Status: Confirmed
Project: ovsdb
Component/s: Southbound.hw_vtep
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Jeff Barnhill Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 6864

 Description   

The yang model for the hwvtep MAC tables has both mac-entry-key and logical-switch-ref for the keys; however, the Postman collection for getting/deleting these entries is only using the mac-entry-key.

Vishal mentioned that this was likely missed during recent changes to the yang model.

 Comments   
Comment by Jeff Barnhill [ 14/Oct/16 ]

For future reference...

I tried a number of ways to include the logical-switch-ref on a GET or DELETE for MAC tables. The following seems to be the correct method, but it doesn't work. Vishnal has confirmed the behavior I've observed.

Example query from APIDOC Explorer:

Section/Command:
GET /config/network-topology:network-topology/topology/

{topology-id}

/node/

{node-id}

/hwvtep:remote-ucast-macs/

{mac-entry-key}

/

{logical-switch-ref}

/

Inputs:
topology-id: hwvtep:1
node-id: hwvtep://10.68.6.203:6640
mac-entry-key: 00:00:00:01:01:01
logical-switch-ref: /network-topology:network-topology/network-topology:topology[network-topology:topology-id='hwvtep:1']/network-topology:node[network-topology:node-id='hwvtep://10.68.6.203:6640']/hwvtep:logical-switches[hwvtep:hwvtep-node-name='odlls01']

Results:
Request URL:
http://10.68.8.150:8181/restconf/config/network-topology:network-topology/topology/hwvtep%3A1/node/hwvtep%3A%2F%2F10.68.6.203%3A6640/hwvtep:remote-ucast-macs/00%3A00%3A00%3A01%3A01%3A01/%2Fnetwork-topology%3Anetwork-topology%2Fnetwork-topology%3Atopology%5Bnetwork-topology%3Atopology-id%3D'hwvtep%3A1'%5D%2Fnetwork-topology%3Anode%5Bnetwork-topology%3Anode-id%3D'hwvtep%3A%2F%2F10.68.6.203%3A6640'%5D%2Fhwvtep%3Alogical-switches%5Bhwvtep%3Ahwvtep-node-name%3D'odlls01'%5D/

Response Body:
{
"errors": {
"error": [

{ "error-type": "protocol", "error-tag": "invalid-value", "error-message": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id='hwvtep:1']/network-topology:node[network-topology:node-id='hwvtep://10.68.6.203:6640']/hwvtep:logical-switches[hwvtep:hwvtep-node-name='odlls01'] from URI can't be resolved. " }

]
}
}

This is the related output from querying the config by topology:
...
hwvtep:remote-ucast-macs": [

{ "logical-switch-ref": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id='hwvtep:1']/network-topology:node[network-topology:node-id='hwvtep://10.68.6.203:6640']/hwvtep:logical-switches[hwvtep:hwvtep-node-name='odlls01']", "mac-entry-key": "00:00:00:01:01:01", "locator-ref": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id='hwvtep:1']/network-topology:node[network-topology:node-id='hwvtep://10.68.6.203:6640']/network-topology:termination-point[network-topology:tp-id='vxlan_over_ipv4:192.168.2.200']", "ipaddr": "1.1.1.1" }

,
...

Comment by Anil Vishnoi [ 02/Feb/17 ]

Hi Vishal,

Any update on this ? I think this is important to update the postman collection and it's the only handy tool we have as of now for the user of plugin, so it's good if we can modify the collection as soon as possible.

Generated at Wed Feb 07 20:36:14 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.