[TRNSPRTPCE-496] OLM timers cannot be configured Created: 31/Aug/21  Updated: 22/Oct/21  Resolved: 22/Oct/21

Status: Verified
Project: transportpce
Component/s: None
Affects Version/s: None
Fix Version/s: Phosphorus

Type: Improvement Priority: Medium
Reporter: Guillaume Lambert Assignee: Guillaume Lambert
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 3 days
Original Estimate: 2 days


 Description   

OLM timer values are defined by OpenROADM whitepar specifications.
For this reason, they are hardcoded in 2 constants in the OlmUtils class.
But there are at least 2 reasons to make configurable via OSGi blueprint or lightyCLI

Although the value recommended by the white paper is 20 seconds, at least one vendor product needs 60 seconds because it is not supporting GainLoss with target-output-power.

The OlmUtils constant are patched in functional tests to speed-up tests because the simulators needs less time to set the OLM up than real devices.


Generated at Wed Feb 07 20:43:14 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.