[CONTROLLER-20] '@' symbols returned in flow programmer rest api Created: 20/Jun/13  Updated: 25/Jul/23  Resolved: 19/May/16

Status: Resolved
Project: controller
Component/s: adsal
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Dale W. Carder Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC

External issue ID: 26

 Description   

In the REST API documentation I found here:
https://jenkins.opendaylight.org/controller/job/controller-merge/ws/opendaylight/northbound/flowprogrammer/target/site/wsdocs/el_ns0_flowConfigs.html

It says the formatting of the json output should look like:
"node" :

{ "id" : "...", "type" : "..." }

, ...and so on

When I look at a flow via the REST api that I have configured via
> curl -u admin:admin http://10.10.10.80:8080/controller/nb/v2/flow/default/OF/00:00:00:50:56:9b:32:28/public-firewall-ipv4-in_to_out

I get this output:
{"installInHw":"true","name":"public-firewall-ipv4-in_to_out","node":

{"@id":"00:00:00:50:56:9b:32:28","@type":"OF"}

,"ingressPort":"2","priority":"500","etherType":"0x800","actions":"OUTPUT=1"}

Note the '@' characters in the flow node 'id' and 'type' fields
which conflict with the names in the documentation.

I also note that when trying to add (POST) a new flow via the rest
api the controller also seems to want those '@' symbols in the 'id'
and 'type' fields.

 Comments   
Comment by Dale W. Carder [ 21/Jun/13 ]

After some googling it looks like maybe something like this is happening?
http://badgerfish.ning.com/

I personally think that format stinks bit because a json rest api
user should not have to care about the server-side's implementation
details. It also may not be that great for anyone using dot
notation in javascript, but then again I am not a javascript guy.

At a minimum the documentation should be updated to be correct.

Comment by Carol Sanders [ 04/May/15 ]

This bug is part of the project to Move all ADSAL associated component bugs to ADSAL

Comment by Robert Varga [ 19/May/16 ]

AD-SAL has been removed, this issue will not be fixed.

Generated at Wed Feb 07 19:51:59 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.