Meetings connection details

available at TransportPCE meetings
https://wiki.opendaylight.org/display/ODL/TransportPCE+meetings

2024-02-15

General information

  • Next DTF Development and testing Forum will be hold in San Jose, collocated with ONE summit the 2nd and 3rd of May

Code Review

Changes merged  since last meeting

  • FixConvertORToTapiTopology Upper/lower Freq: bug detected during the code refactoring step.

Changes transportpce-models under review:

  • “Add OpenROADM device 13.1.0 models” could be merged
  • “Update the iana-afn-safi import in lldp module”: could also be merged, and no objection were formulated during the meeting.
  • “Bump upstream dependencies to Ca” was pushed by Gilles this week to start the migration to Ca, and no specific issues were identified on this side.

Changes transportpce under review:

  • Smartoptics provided 2 changes to correct RollBack function : “New package dealing with device Rollback” & “Refactoring Rollback when service create fails”. Bala has been asked to review. The new functionality may be easier to test on devices than simulator. Gilles confirms that we can wait before merging it. In this change, multiple interfaces/classes were proposed to handle the rollback process. It is not that easy to figure out whether the new rewritten callback function will work, and the best option to test these changes is to test them on real equipment.
  • “Fix OLM rollback” could be merged now. Not really dependent on the previous relation chain
  • “False warning message when service creation fails” could be merged.
  • “Only verify PreFEC BER if end node is Xponder” pushed by Jonas avoids reading PreFEC BER from end nodes when creating a ROADM-to-ROADM. Need to be check because one Junit test fails... Issue on the gate?
  • “Add SpectrumFillingRule check in postAlgoValidator” : Olivier shall cleanup the Junit test before we merge it.
  • Gilles initiated the migration to Ca with “Bump upstream dependencies to Ca”.
  • “Add a Tox profile to install lightynode”, “Switch all func tests to lightynode”, “Upgrade LightyNode sim version” are still under review.
  • “complement sims configuration files” passed the gate but seems to fail right now with the same issue that we experience with some other changes. Christophe continues debugging the OpenConfig xml configuration files. He experiences some issues with some augmentations, especially for components, and more specifically psu.

2024-02-08

General information

  • ODL distribution for K-SR2 is released. Release notes have been updated.

  • Gilles started the migration of master branch to Ca (targeted mid-March) which seems to have important side-effects on TransportPCE current implementation. Hope it will not be too much difficult to adapt...

Code Review

Changes merged  since last meeting

  • Olivier's relation chain on tapi 2.4 models migration. TPCE is now implementing T-API 2.4 models.

Changes under review:

  • Guillaume has initiated a refactoring activity on TAPI code:
    • “Refactor Tapi Connectivity Utils” which simplifies the code style has been reviewed by Gilles,

    • “RefactorTapi ConvertORTopoToTapiTopo” has been reviewed by Gilles,

    • “RefactorTapi ConvertORToTapiTopology” : Gilles has reviewed it, Olivier started reviewing it but has not finished,

    • “Outsource TAPI test constants from test utils” has been reviewed by Gilles who provided some comments,

    • “Refactor Tapi ConvertORTopoToTapiTopo junit” & “Refactoring some Tapi Junit tests code ” have been reviewed by Gilles and merged in session

  • Smartoptics provided 2 changes to correct RollBack function: “New package dealing with device Rollback” & “Refactoring Rollback when service create fails”. Bala has been asked to review. The new functionality may be easier to test on devices than simulator.
  • New changes from Olivier related to the wavelength selection issue raised by NTT: “Add Customer name to path Computation”, and “Add SpectrumFillingRule check in postAlgoValidator” are 2 changes to handle a service creation according to a specific wavelength. As wavelength can not be provided as a constraint in service-create, we propose to leverage the spectrum-filling feature of Controller-behaviour-settings which was initially proposed to partition the spectrum across customers. Thus the wavelength constraint can be expressed as a specific customer profile (using customer-name in service-create) for which we dedicate a specific spectrum as specified in spectrum-filling-rules.
  • Functional tests migration to lightynode:
    • “Add a Tox profile to install lightynode”: Gilles pushed this change to allow installing lightynode according to any version (specific release or specific snapshot binaries)
    • “Switch all func tests to lightynode”: Christophe's change allows to switch from Honeynode to Lighty for all the tests (1.2.1, 2.2.1, and 7.1). In tox.ini , it allows adopting lightynode sims for remaining 7.1, hybrid and  with_docker tests. It also adapts tests using netconf connector instead of restconf one as soon as Lightynode does not support restconf api
    • “Upgrade LightyNode sim version” upgrades Lightynode version to manage notifications for 1.2.1 and 7.1.0. Now integrated inside the previous one. Will be abandonned.
    • “Complement sims configuration files” is complementing configuration files for 7.1 configuration (pm description and pm list)

2024-02-01

General information

  • Potassium SR2 has just been approved by the TSC and the ODL distribution shall be released soon. For TransportPCE, the last changes that were pending (release note update in docs project) have been merged by Guillaume.

  • Gilles will probably start the migration of Master branches to Ca next week.

  • Robert informed the community about a migration to Java 21st planned in Ca SR1, and imposed in Scandium.

Code Review

Changes merged  since last meeting

  • Changes related to the K-SR2 release and backported from stable/potassium branch
  • Matej's change that was pending for a while (“Don’t use notificationListener (NodeRegistration)”)
  • Removal of transportPCE swagger feature that was an old workaround for developer that is not needed anymore.
  • Synchronisation of master branch of transportpce-modes to K-SR2

Changes under review:

  • Olivier's relation chain on tapi 2.4 model migration
    • The relation has been reworked end of last week. Gilles reviewed it, and Olivier has addresed most important comments made by Gilles, and then reabsed again the chain. Gilles is about to merge them if nobody has any objection.
  • Tapi code refactoring: Guillaume has initiated a refactoring activity with several changes:
    • “Refactor Tapi Connectivity Utils” which simplifies the code style,
    • “Outsource TAPI tests constants from tests utils” and “Refactoring some Tapi Junit tests ” which simplifies the structure of the tests
  • Gilles pushed several changes on transprtpce-models
    • “Add OpenROADM device 13.1.0 models” allows to have 13.1 OpenROADM device models for future developments in tpce.
    • “Update the iana-afn-safi import in lldp module” is solving the issue of relying on an obsolete model. Long discussion about possible impact of having a change of namespace with the iana-routing-types model...
    • “Add a set OpenConfig yang models” is adding a set of OpenConfig models to tpce, which correspond to what we see in some pre R1.0 equipment. It is still under review.

General topic

  • Olivier has provided a draft of the OpenConfig device configuration for Lighty, which consistency shall be tested.
  • reminder: url to use to have swagger is http://<server>:8181/openapi/explorer/index.html

2024-01-25

General information

  • Gilles released TransportPCE artifacts for K-SR2 + prepare its integration inside ODL distribtuion + prepare the release note on docs project

Code Review

Changes merged  since last meeting

  • New relation chain from Gilles on stable/potassium related to the K-SR2 release preparation

Changes under review:

  • Same Gilles's K-SR2 related relation chain backported from stable/potassium branch to master
  • Olivier's work on tapi 2.4 migration
    • Olivier shall rebase the T-API relation chain after Gilles's changes are merged
    • Guillaume considers that the relation chain can be merged. Gilles will have a look at it before.
  • Addition of a set of openconfig yang models in transportpce-models repo which corresponds to what we see in some pre R1.0 equipment.

General topic

  • Olivier is working on correcting and completing the OpenConfig device configuration for the lightynode simulator, making it closer to what we observe with equipment in the labs.

2024-01-18

Code Review

No change merged  since last meeting

transportpce changes under review:

  • “Don’t use notification Listener (Node registration)”:  The missing Netconf features will be added in AR-SR4, K-SR2 and Ca-GA. Could be merged after the dependency bump
  • Status on Olivier's work on tapi 2.4 migration

    • Olivier addressed Guillaume's comments in the relation chain associated with migration and refactoring. Some of the tests do not pass. It will be corrected according to the results of the gate that will help identify where (at which level of the chain) the bug was introduced

General topic

  • Sprint 34 was initiated. All non-closed issues of previous sprint have been included. An additional issue #774 was introduced : Create an OpenConfig configuration file. Some JIRA ticket describing OpenConfig models to be introduced in tpce models need also to be created.

  • Christophe made a small project to illustrate the bug we have in lightynode for openroadm-device 7.1 models (handling when statement). He reported the issue on the odl-kernel list. The Issue is identified in the yangtools project, but it seems difficult to solve it, and no solution will be provided in a short time. 2 workarounds have been proposed.

  • Bala is trying to fix the way we are building A and Z end containers in service-create and temp-service-create so that he can retrieve the operational mode supported by external pluggables to address IPoWDM case.

  • He also started to implement the power control RPC to address IPoWDM use case.

  • Bug: When we specify the port to use in the service-create (for SRGs ending an optical tunnel), tpce is currently picking the port based on first port available, not considering the port specified in the service-create. Gilles started to work on this bug but did not have the time to work on any use case. He asked Bala to create a JIRA ticket to better understand the associated use case.

2024-01-11

Code Review

changes merged  since last meeting:

  • 3 changes related to the bug TRNSPRTPCE-772 reported by Joakim

    • “Spectrum assignment skipped the last node in path ” proposed by Joakim
    • “PCE graph spectrum assignment slight refactoring”: small refactoring pushed by Guillaume
    • “Add new functional PCE test to check bug 722”: new small pce functional test suite proposed by Gilles to check the effective correction of the bug.

transportpce changes under review:

  • Status on Olivier's work on tapi 2.4 migration

    • It's a bit of a mess in its relation chain: Gilles will help to realign correctly the different changes.

    • Still in work in progress. Need to address Guillaume's comments on few changes

General topic

  • Bala mentions that we may need to implement OpenROADM 13.1 device models in TransportPCE. Gilles mentions that it is not an issue to add device models 13.1 in transportpce-models repo. He is also in favor of deprecating the oldest ones (1.2.1) which are not used except in TransportPCE functional tests. Gilles will communicate the intention to cancel the support for R 1.2.1 models on the dev list.
  • No labels