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", although the longer term plan is to bring it up to par with the "classic" view, which it will eventually replace.
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>
where:
A couple of examples:
region-add rUK "United Kingdom" COUNTRY 52.206035 -1.310384 geo "192.168.56.101 / 192.168.56.102" region-add rRack1 "Primary Rack" RACK 15.0 20.0 grid 10.0.0.5 |
Note that CLI commands are scriptable. One way of doing this is as follows:
#!/bin/bash host=${1:-localhost} onos ${host} <<-EOF region-add rUK "United Kingdom" COUNTRY 52.206035 -1.310384 geo ${host} region-add rIT "Italy" COUNTRY 44.447951 11.093161 geo ${host} region-add rFR "France" COUNTRY 47.066264 2.711458 geo ${host} EOF |
Devices can be assigned to regions with the region-add-devices command:
region-add-devices <region-id> <dev1> <dev2> ... <dev-n>
where
For example:
region-add-devices rUK \ of:0000000000000001 \ of:0000000000000002 \ of:0000000000000003 |
The currently configured regions can be listed with the regions command:
regions
onos> regions id=rDE, name=Germany, type=COUNTRY master=[localhost] of:0000000000000013 of:0000000000000014 of:0000000000000015 of:0000000000000016 of:0000000000000017 id=rES, name=Spain, type=COUNTRY master=[localhost] of:0000000000000018 ... |
(Another region command we'll look at is region-add-peer-loc, but we'll defer that until we have covered layouts).
Note that regions do not have any notion of hierarchy; they are simply "collections of devices". The hierarchy is expressed using Layouts.
Layouts are used to define a "containment" hierarchy for the regions, as well as provide configuration information for the UI, such as which background decoration to use when displaying the layout; for example a geographical map.
A Layout is a "UI construct" that has an associated region "backing" it. Layouts define some other layout as its parent (except the root layout, of course), thereby allowing a hierarchy of layouts to be constructed.
This could be pictured as shown here:
Note that the "root" (default) layout does not have a backing region. Any devices (and their attached hosts) that have not been assigned to a region will appear in the topology view at this top level.
Layouts can be configured using a number of CLI commands:
Layouts can be added to the model with the layout-add command.
layout-add <layout-id> <bg-ref> <region-id> <parent-layout-id> <scale> <offset-x> <offset-y>
where
Some examples:
layout-add root @europe . . 4.66 -2562.93 -412.56 layout-add lUK @europe rUK root 11.63 -6652.54 -938.04 layout-add lIT @europe rIT root 7.15 -4818.73 -1330.36 layout-add lFR @europe rFR root 8.98 -5378.99 -1334.77 layout-add lMilan +segmentRouting rMilan lIT 0.86 68.58 54.71 |
Note that currently the <scale>, <offset-x>, <offset-y> values can be determined by trial and error. See the section on Useful Techniques below for more details.