[CONTROLLER-260] Example MD-App that uses existing models Created: 01/Apr/14  Updated: 25/Jul/23  Resolved: 08/Apr/14

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

Type: Improvement
Reporter: Ed Warnicke Assignee: Amit Mandke
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Mac OS
Platform: PC


 Description   

At the MD-SAL working group meeting there was a request for a simple example app that uses the existing models:

Topology
Flow
Stats
etc

to do something simple but interesting.

 Comments   
Comment by Tony Tkacik [ 02/Apr/14 ]

Changed importance to enhancement, since it is not bug in the code, but documentation improvement.

Comment by Amit Mandke [ 07/Apr/14 ]

Resolution Comments:
https://git.opendaylight.org/gerrit/#/c/5918/
Contributing a sample implementation of a learning switch with optimizations in how packet is forwarded.
Link to detail documentation: https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:L2_Switch
It has following components that interact with existing data models(operation and Configuration both):

AddressTracker stores the Mac-Port pairings in the MD-SAL data tree.
InventoryService provides information about the nodes and node connectors in the network.
FlowWriterService adds packet forwarding (mac-to-mac) flows to the MD-SAL data tree.
-uses NetworkGraphDijkstra to determine all the intermediate nodes along a path.
TopologyLinkDataChangeHandler listens to topology updates and informs NetworkGraphDijkstra of these updates.
NetworkGraphDijkstra maintains the network graph and computes the shortest path between each node.

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