Changes between Version 6 and Version 7 of Internal/OpenFlow/topoMapping


Ignore:
Timestamp:
Aug 13, 2012, 6:34:26 AM (8 years ago)
Author:
akoshibe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Internal/OpenFlow/topoMapping

    v6 v7  
    2222  * ''network'' : via !OpenFlow e.g. a Floodlight module that takes a topology description and pushes static flows, or even CLI. 
    2323
    24 The overall architecture will possibly work as follows:
     24== Components Overviews ==
     25This section contains some initial design considerations for the various components listed above. The overall architecture will possibly work as follows:
    2526
    26 [[Image(topologizer.png)]]
     27[[Image(topopologizer.png)]]
    2728
    28 == Components Overviews ==
    29 This section contains some initial design considerations for the various components listed above.
     29The file parser will produce two outputs, the node:edge information needed by the topology setup component, and a set of hints provided to a component that would initialize the base topology, which the final topology will be enforced upon using dpctl. Initialization would include actions such as starting up VMs and virtual switches, and checking that they are up and are in a configurable state. 
     30
    3031==== !OpenFlow topology setup ====
    3132It was assumed that [http://floodlight.openflowhub.org Floodlight] will be used for development. Several methods to enforce topology using SDN methods come to mind: