Work in progress

ONOS Topology Information model

Topology information model elements, relevant to transport network, consist from Device, Port, and Link.

Device represents network infrastructure devices, such as (Packet) switch, ROADM, etc.
Port represents a port on a Device.
Link represents a connectivity between Ports.

Each elements has fixed basic attributes common across variant of its kind. (e.g., Port's portspeed)
Additional information about elements can also be added as String-String annotations by each Providers.
This mechanism should be used to add relatively read-heavy information specific to certain technology, domain.

As of Falcon release, current implementation of optical information model does not fully utilize Annotation mechanism to add optical specific information to the topology model elements.
From Goldeneye release and beyond, we intend to gradually migrate to a model utilizing this Annotation mechanism and Projection mechanism to express following optical specific information, so that optical details does not leak into the ONOS core code.

Optical Information Model

(basically ports carrying extra attributes)

OduCLt port

Representation of ODU client port (Optical channel Data Unit).

Och port

Representation of OCh port (Optical Channel)

OMS port
- Representation of OMS port (Optical Multiplexing Section)
OTU port
- Representation OTU port (Optical channel Transport Unit)

Example representation of optical devices in Optical Information model

Vertically Integrated ROADM model

Following is vertically integrated ROADM used in the Packet-Optical demo at ONS2015, represented using ONOS optical information model.

Disaggregated ROADM model (a.k.a. OpenROADM)

Following is disaggregated ROADM (a.k.a. OpenROADM) used in the E-CORD/OpenROADM demo at ONS2016/OFC2016,
represented using ONOS optical information model.

Optical Information model in ONOS code

(TODO leave a note about where we are now at Falcon, where we want to be in Goldeneye?)