=============
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:

.. list-table:: Transport PCE implementation
   :widths: 20 50
   :header-rows: 1

   * - **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
========================

The Argon GA version contains a number of code refactorings in order to improve the maintainability of the controller
code. Moreover, this release also covers some important code evolution, as the removal of all blueprint.xml files that
will be replaced by OSGi components, or again the migration of all unitary tests of TransportPCE project to JUnit 5.
From a business point of view, Argon release brings the management of Regenerator in OpenROADM version device 7.1.0.
It means that some transponder may be used as a simple regenerator (without client ports).

New Features
============

No new feature as such in Argon.

Deprecated Features
===================

There are no deprecated or removed features.

Resolved Issues
===============

The following table lists the issues resolved in this release.

.. jira_fixed_issues::
   :project: TRNSPRTPCE
   :versions: Argon-Argon

Known Issues
============

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

.. jira_known_issues::
   :project: TRNSPRTPCE
   :versions: Argon-Argon

Resolved Issues in SR1
======================
The following table lists the issues resolved in Service Release 1.

.. jira_fixed_issues::
   :project: TRNSPRTPCE
   :versions: ArgonSR1-ArgonSR1

Known Issues in SR1
===================
The following table lists the known issues that exist in Service Release 1.

.. jira_known_issues::
   :project: TRNSPRTPCE
   :versions: ArgonSR1-ArgonSR1

Resolved Issues in SR2
======================
The following table lists the issues resolved in Service Release 1.

.. jira_fixed_issues::
   :project: TRNSPRTPCE
   :versions: ArgonSR2-ArgonSR2

Known Issues in SR2
===================
The following table lists the known issues that exist in Service Release 1.

.. jira_known_issues::
   :project: TRNSPRTPCE
   :versions: ArgonSR2-ArgonSR2

Resolved Issues in SR3
======================
The following table lists the issues resolved in Service Release 1.

.. jira_fixed_issues::
   :project: TRNSPRTPCE
   :versions: ArgonSR3-ArgonSR3

Known Issues in SR3
===================
The following table lists the known issues that exist in Service Release 1.

.. jira_known_issues::
   :project: TRNSPRTPCE
   :versions: ArgonSR3-ArgonSR3