Hi Jamo,
I very much appreciate your reply. I was not aware of this behaviour.
However, I did test it yesterday and I was getting a 201 created for the
Configuration DataStore REST call. So it must not be this. I will continue
digging to see what the problem is.
Thanks.
> Le 29 mars 2017 à 16:01, Jamo Luhrsen <[email protected]> a écrit :
>
> I doubt this is your issue, but just double check that you are not adding the
> flow when it already exists in config. doing that will give a friendly 20x
> response, but it doesn't (last time I checked) trigger an add flow.
>
> just a thought
>
> JamO
>
> On 03/29/2017 12:33 PM, yann bourdeau wrote:
>> Hi All,
>>
>>
>> I have made some progress with my experimenters. It started working today.
>> However, I have noticed that if I add the flow to
>> the Configuration Data Store, the flow does not get pushed to the switch.
>> However, if I send the flow via the Operational
>> Data Store RPC (add flow), it got added to the switch. I’d like to know the
>> if this is the normal behaviour or not?
>>
>> Here are the REST requests:
>> Config Data Store:
>> URL:
>> http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:1/table/2/flow/1234
>> Verb: PUT
>>
>> Body:
>> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>> <flow xmlns="urn:opendaylight:flow:inventory">
>> <barrier>false</barrier>
>> <cookie>10</cookie>
>> <cookie_mask>10</cookie_mask>
>> <flags>SEND_FLOW_REM</flags>
>> <flow-name>FooXf1</flow-name>
>> <hard-timeout>0</hard-timeout>
>> <id>1234</id>
>> <idle-timeout>0</idle-timeout>
>> <installHw>false</installHw>
>> <instructions>
>> <instruction>
>> <apply-actions>
>> <action>
>> <order>0</order>
>> <nx-action-set-payload-ip
>> xmlns="urn:opendaylight:openflowplugin:extension:noviflow:action">
>> <payload_size>1</payload_size>
>> <payload_offset>0</payload_offset>
>> <hasmask>0</hasmask>
>> <data>9</data>
>>
>> </nx-action-set-payload-ip>
>> </action>
>>
>> </apply-actions>
>> <order>0</order>
>> </instruction>
>> </instructions>
>>
>> <priority>2</priority>
>> <strict>false</strict>
>> <table_id>2</table_id>
>> </flow>
>>
>> Operational Data Store:
>> URL: http://localhost:8181/restconf/operations/sal-flow:add-flow
>> Verb: POST
>> Body:
>> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>> <input xmlns="urn:opendaylight:flow:service">
>> <barrier>false</barrier>
>> <node
>> xmlns:inv="urn:opendaylight:inventory">/inv:nodes/inv:node[inv:id="openflow:1"]</node>
>>
>> <cookie>55</cookie>
>> <flags>SEND_FLOW_REM</flags>
>> <hard-timeout>0</hard-timeout>
>> <idle-timeout>0</idle-timeout>
>> <installHw>false</installHw>
>>
>> <instructions>
>> <instruction>
>> <order>0</order>
>> <apply-actions>
>> <action>
>> <nx-action-set-payload-ip
>> xmlns="urn:opendaylight:openflowplugin:extension:noviflow:action">
>> <payload_size>1</payload_size>
>> <payload_offset>0</payload_offset>
>> <hasmask>0</hasmask>
>> <data>91</data>
>>
>> </nx-action-set-payload-ip>
>> <order>0</order>
>> </action>
>> </apply-actions>
>> </instruction>
>> </instructions>
>> <priority>0</priority>
>> <strict>false</strict>
>> <table_id>0</table_id>
>> </input>
>>
>> Thanks in advance. Any help will be greatly appreciated.
>>
>> ps: I will rename the nx to nfx in the body in a later time (Needs to change
>> YANG file).
>>
>> Yann Bourdeau, M.Ing.
>> Senior Software Developer
>> 438-499-4607
>> [email protected] <mailto:[email protected]>
>> <mailto:[email protected] <mailto:[email protected]>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> openflowplugin-dev mailing list
>> [email protected]
>> <mailto:[email protected]>
>> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
>> <https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev>
Yann Bourdeau, M.Ing.
Senior Software Developer
438-499-4607
[email protected]
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
