Details
-
Story
-
Status: Verified
-
Medium
-
Resolution: Done
-
None
-
None
-
None
Description
Until now, OTN use cases managed by TransportPCE are only simple network configurations, where supported OTU4 and structured ODU4 are terminated on the same termination points.
Introducing an intermediate otn-switch imposes to manage more complex network configurations, as for example:
- one end-to-end structured ODU4 supported by several OTU4
- one end-to-end 1GE or 10GE service supported by several sturctured ODU4.
With such configurations, PCE must compute a paht, renderer must be able to configure interfaces (with sapi/dapi, etc), and network module must update correctly link bandwidth of otn-topology.
Attachments
1.
|
Create a new functional test suite testing OTN end-to-end services in network configuration with intermedaite otn-switch |
|
Verified | Unassigned |
|
|||||||
2.
|
Update device-renderer YANG model to use a-end-api-info and z-end-api-info containers in service-path rpc |
|
Verified | Unassigned |
|
|||||||
3.
|
Rationalize the OpenRoadmInterface creations |
|
Verified | Unassigned |
|
