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

Support of "non-standard" modes (service type/rate/width)

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • None
    • None
    • None

      Require changes to the PCE and service handler code

      Rework in the PCE, the PostAlgoPathValidator.

       First we need Service Model 10.1 (pushed by Gilles) and Network Model 10.1 (ongoing). Having this, we will have the specification catalog in the datastore, and the supported Operational mode (for any kind of node) in the topology (if we complement the code). The plan is then to develop generic function to retrieve physical parameters from the catalog, pointing to an operational mode (which can be OR or Specific non-standard mode). Having this we will be able to derive width and spacing associated with any mode. Thus we will be able to change the way MC width is calculated (from OM rather than service type). It will be more generic, and will avoid hardcoding some functions. Update not only the PostAlgoPathvalidator but also the renderer accordingly.

            Unassigned Unassigned
            b95quare Balagangadhar Bathula
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: