(Content moved from SE Gitlab to IfI Gitlab, origin author: Pitor)

Changes introduced after the meeting on 12.02.2016:

• rename SoftwareComponent -> Software
• removed IPosition interface that was implemented by the End and the Intermediate . Now
• Source/Destination Flow is now represented as Flow with single source Software and 1+ destination Software
• FlowRoute is not exposed to the modeller. Only Direction s should be used from now to model routes.
• Switching in SDN-mode can be done in three ways (depending on SdnFlowRule):
  1. Using Hardware switching table with probability defined for each tuple ( Flow, Node)
  2. Using Software switching table with probability defined for each tuple ( Flow, Node)
  3. Using SdnController with probability defined for each tuple ( Flow, Node)
• SdnController serves only as a software container for SdnControllerApplication s
• Performance of switching using SdnController depends on:
  • Mapping of SdnControllerApplication to: SdnController, Flow, Node (using SdnFlowRule ). SdnControllerApplication X will be activated only for a given combination: Flow, Node and Controller (if many) SdnControllerApp example pngsdnapp-example.png SdnControllerApp example PDFsdnapp-example.pdf SdnControllerApp example2 pngsdnapp-example2.png SdnControllerApp example2 PDFsdnapp-example2.pdf
  • SdnController should have at least one SdnControllerApplication (the default one) that works for all flows

Current state (ecore):

• ecore

Current state:

• Routing view (including FlowRule): Routing-view PDFrouting-view.pdf

• SDN view: SDN-view PDFsdn-view.pdf

• Compact representation of important entities (Node, IType, IPosition, Flow, Direction): Compact PDFcurrent-compact.pdf

Examples:

• Load Balancing (three cases): Load balancing examples PDFthree-examples.pdf

• Switching using SdnController and SdnControllerApp s : SDN Controller App PDFsdnapp-example.pdf

• Selecting SdnControllerApp : Selecting SDN Controller App PDFsdnapp-example2.pdf