Wrong mapping of flow-list entry attributes (ipdscp, protocol, icmptype, icmpcode) from VTN Coordinator to VTN manager.

Issue Scenario :

The dscp,protocol,icmp type,icmp code values from the Coordinator flowlistentry are wrongly mapped in the VTN Manager

Reproduce the Bug:

First get a set-up for vtn manager and coordinator using the example:
Create Flowlistentries as shown on the below page:

https://wiki.opendaylight.org/view/OpenDaylight_Virtual_Tenant_Network_(VTN):VTN_Coordinator:RestApi:How_to_configure_Flow_Filters_using_VTN.

In the flowlistentry command give the ipdscp,protocol,icmptype and icmpcode attributes as given below:

curl -v --user admin:adminpass -H 'content-type: application/json' -X POST -d '{"flowlistentry": {"seqnum": "233","macethertype": "0x800","ipdstaddr": "10.0.0.1","ipdstaddrprefix": "32","ipsrcaddr": "10.0.0.3","ipsrcaddrprefix": "32","dscp": "17", "ipproto": "1", "icmptypenum": "200", "icmpcodenum": "10" }}' http://127.0.0.1:8083/vtn-webapi/flowlists/flowlist1/flowlistentries.json

The Request body in the Coordinator logs :

2015-03-18 23:43:12.817474: [12796]: INFO: restjsonutil: requestbody : : { "index": 233, "ethernet":

{ "type": 2048 }

, "inetMatch": { "inet4":

{ "protocol": 17, "src": "10.0.0.3", "dst": "10.0.0.1" }

}, "l4Match": { "icmp":

{ "type": 10 }

} }

The below mentioned is from the VTN Manager obtained by GET command :

{"name":"flowlist1","match":[{"ethernet":

{"type":2048}

,"inetMatch":{"inet4":{"protocol":17,"src":"10.0.0.3","dst":"10.0.0.1"}},"l4Match":{"icmp":{"type":10}},"index":233}]}

THE IPDSCP and ICMP CODE Values are mismatched with IPPROTOCOL and ICMP TYPE in the VTN Manager

Occurrence of the issue :

Occurs every time during creation of flowlistentries with the ipdscp,protocol,icmptype,icmpcode attributes