Topology 2 is a "region aware" view of the topology, where the administrator can configure the network into regions and sub-regions.
In its default state (where no "regions" or "layouts" are defined), it should look and behave similarly to the "classic" Topology view.
Note that this view is currently "experimental".
The ONOS model of the network includes Region objects which can be configured with a collection of Devices (switches) "belonging" to that region.
Regions can be configured using a number of CLI commands:
To add a region to the model, the region-add command can be used..
region-add <region-id> <region-name> <region-type> <lat/Y> <long/X> <locType> <region-master>
- <region-id> is a unique identifier for the region
- <region-name> is a human readable name for the region
- <region-type> is one of the values defined in the Region.Type enumeration:
- CONTINENT, COUNTRY, METRO, CAMPUS, BUILDING, DATA_CENTER, FLOOR, ROOM, RACK, LOGICAL_GROUP
- <lat/Y>, <long/X> are the latitude / longitude (for geo layouts) or Y-coord / X-coord (for grid layouts) to be assigned to the region when it is displayed as a node in its parent layout.
- <locType> is either geo (for geographical (map) layout) or grid (for logical grid layout).
- <region-master> is a list of sets of node-IDs for mastership of the devices (see RegionAddCommand for more details).
A couple of examples:
Note that CLI commands are scriptable. One way of doing this is as follows:
Devices can be assigned to regions with the region-add-devices command:
region-add-devices <region-id> <dev1> <dev2> ... <dev-n>
- <region-id> is the region unique identifier
- <dev-...> is a device identifier