Transport PCE

Overview

Transport PCE is an application running on top of the OpenDaylight controller. Its primary function is to control an optical transport infrastructure using a non-proprietary South Bound Interface (SBI).

The controlled transport infrastructure includes a WDM (Wave Division Multiplexing) layer and an OTN (optical transport network) layer. The WDM layer is built from ROADMs (reconfigurable optical add-drop multiplexer) with colorless, directionless and contention-less features. The OTN layer is built from transponders, muxponders or switchponders which include OTN switching functionalities.

Transport PCE leverages OpenROADM Multi-Source-Agreement (MSA), which defines interoperability specifications, consisting of both optical interoperability and YANG data models.

The TransportPCE implementation includes:

Transport PCE implementation

Feature	Description
Northbound API	These APIs are for higher level applications, implemented in the Service Handler bundle. It relies on the service model defined in the MSA. A minimal experimental support of TAPI topology is also proposed but is not installed by default.
Renderer and OLM	The renderer and OLM (Optical Line Management) bundles allow configuring OpenROADM devices through a southbound NETCONF/YANG interface (based on the MSA device models). This release supports the OpenROADM devices version 1.2.1 version 2.2.1.
Topology Management	This feature is based on the defined MSA network model.
Path Calculation Engine (PCE)	PCE here has a different meaning than the BGPCEP project since it is not based on (G)MPLS. This bundle allows to compute path across the topology to create services. Impairment aware path computation can be delegated to a GNPy server (hardcoded server address configuration and limited support at that time)
Inventory	This feature is not installed by default. It proposes an experimental support for an external inventory DB currently limited to 1.2.1 OpenROADM devices.

The internal RPCs between those modules are defined in the Transport Service Path models.

Behavior/Feature Changes

TBD

Changes planned in Sulfur release stream

TBD

New Features

TBD

Deprecated Features

There are no deprecated or removed features.

Resolved Issues

The following table lists the issues resolved in this release.

Issues resolved in versions Sulfur through Sulfur (JIRA)

Type	Key	Summary	Resolution	Fix Version(s)
	TRNSPRTPCE-645	Bug in the ethernet loop of the 221 E2E tests	Done	Phosphorus, Sulfur
	TRNSPRTPCE-647	Update XPDR-C1 configuration file with a list of xponder	Done	Phosphorus, Sulfur
	TRNSPRTPCE-646	Update checks for service requests in service handler	Done	Phosphorus, Sulfur
	TRNSPRTPCE-643	Manage 100GE service terminated on a 2.2.1 XPDR with a list of xponder	Done	Phosphorus, Sulfur
	TRNSPRTPCE-572	Refactor PceOtnNode class	Done	Phosphorus, Sulfur
	TRNSPRTPCE-516	Network model 10.1	Done	Sulfur
	TRNSPRTPCE-515	Service Model 10.1	Done	Sulfur
	TRNSPRTPCE-376	PCE-GNPy adaptation for higher rates	Done	Phosphorus, Sulfur
	TRNSPRTPCE-513	Update GNPy REST implementation	Done	Phosphorus, Sulfur
	TRNSPRTPCE-639	Prepare Migration to Sulfur	Done	Sulfur
	TRNSPRTPCE-567	Functional tests RFC8040 REST API migration	Done	Phosphorus, Sulfur

Known Issues

The following table lists the known issues that exist in this release.