Thanks, if I had to do this from within a Java app, I assume I'd have to use the SalFlowService. Is that not deprecated ? If so, what is the MdSal alternative?
Regads, Ranga On Thu, Jul 12, 2018 at 4:45 PM, Luis Gomez <[email protected]> wrote: > You can send openflow RPC like the example below: > > POST http://192.168.0.101:8181/restconf/operations/sal-flow:add-flow > { > "input": { > "opendaylight-flow-service:node":"/opendaylight- > inventory:nodes/opendaylight-inventory:node[opendaylight- > inventory:id='openflow:1']", > "priority": 2, > "flow-name": "flow1", > "table_id": 0, > "hard-timeout": 0, > "instructions": { > "instruction": [ > { > "order": 0, > "apply-actions": { > "action": [ > { > "order": 0, > "output-action": { > "output-node-connector": "1" > } > } > ] > } > } > ] > }, > "idle-timeout": 0, > "match": { > "ipv4-destination": "10.0.10.0/24", > "ethernet-match": { > "ethernet-type": { > "type": 2048 > } > } > } > } > } > > > > > On Jul 12, 2018, at 12:09 PM, M. Ranganathan <[email protected]> wrote: > > > > I am using OpendDaylight Nitrogen. In order to send a flow to the > switch, I write to the CONFIG database - which winds up sending the flow to > the switch. However, I want faster performance for ephemeral flows . How > can I send the flow to the switch without involving the CONFIG database? > > > > Thanks, > > > > Ranga > > > > -- > > M. Ranganathan > > > > _______________________________________________ > > openflowplugin-dev mailing list > > [email protected] > > https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev > > -- M. Ranganathan
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
