Skip to content
Antonio Gomez Vergara edited this page Jun 7, 2017 · 1 revision

Control Orchestration Protocol:

The COP is defined with yang models, and the topology server code (export) and client (import) are autogenerated with the Pyang and Swagger tools.

The instructions to generate the code of the java server (JAX-RS) are here.

The integration of the generated code as a package inside the Topology Module (TM) has been arduous because of the dependencies, thanks to Maven this process has been simplified and the list of dependencies can be found in the pom.xml.

If the need of generate a fresh new server following another yang model, the libraries are included, so the process should be nice and easy. The autogenerated code should be completed with the package server.api.impl including the necessary translation to adjust the information inside our TopologyDataBase to the model (also autogenerated in the package server.model). An example of this process can be found here.

BGP-LS:

The import and export of the TEDB (Traffic Engineering DataBase) by the BGP-LS protocol is done through bgppeer developed in the bgp4Peer package. Also this plugin can be executed along the Topology Module and the PCE, thus it allows the PCE the to speak with another PCE in order to obtain the information of the TEDB from the PCE sender.

XML:

The Topology Module includes an information importer of the topology from an XML file, describing both a TEDB and a TopologyDataBase. The XML plugin can be found here.

OSPF:

The Open Shortest Path First (OSPF) allows to update the information of the TopologyDataBase reading the OSPF packages.

TAPI:

The Transport API (TAPI) plugin obtain the dopology of the network and export it to TAPI. It can be found here

Clone this wiki locally