Uploaded image for project: 'transportpce'
  1. transportpce
  2. TRNSPRTPCE-496

OLM timers cannot be configured

    XMLWordPrintable

Details

    • Improvement
    • Status: Verified
    • Medium
    • Resolution: Done
    • None
    • Phosphorus
    • None
    • None

    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.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            guillaume.lambert Guillaume Lambert
            guillaume.lambert Guillaume Lambert
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 2 days Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 3 days
                3d