Hello Ranga, assing openflowplugin-dev and genius-dev, as this question is more relevant to those projects than mdsal-dev :
On Wed, Aug 22, 2018 at 7:25 PM M. Ranganathan <[email protected]> wrote: > Hello, > > In my application I am writing some flows when a switch connects. There > are two ways of getting the flows to the switch: > > 1. Write to MD-SAL (use a transaction and DataBroker). > 2. Write to switch using SalFlowService. > > The latter is more efficient (it does not write to persistent store) but > since I am generating my flow each time a switch connects, it does not > matter anyway. When would one pick one approach vs. the other (other than > performance)? > > Just looking for a use case to understand the intended design. > > Thanks for your insights. > I'm no expert in this matter, but my understanding it that you can write the YANG model for flows by the openflowplugin directly, and it (the openflowplugin) will write out those flows to the switch. On top of this, some projects simply have built some helpers and abstractions. I'm not sure what the SalFlowService is (from which project). The genius project has the IMdsalApiManager service, see https://javadocs.opendaylight.org/org.opendaylight.genius/fluorine/org/opendaylight/genius/mdsalutil/interfaces/IMdsalApiManager.html, which is another such helper. If you look into its implementation, it ultimately still just write the YANG model to MD-SAL using a transaction and DataBroker. HTH? Tx, M. -- Michael Vorburger, Red Hat [email protected] | IRC: vorburger @freenode | ~ = http://vorburger.ch
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
