5 mins Administrative Review of TR-547 1.1: Tentative scheduling of 2 hours calls for Sept 20, 22, 23, 24. Invited Ramon, Nigel, Ronald, Pedro, Arturo. Please others interested to contact Andrea. 21 Sep 2021 TAPI weeky call Preliminary agenda: 15 mins
Any follow up on TIP requirements to ONF/TAPI?
Arturo indicates that the next version of
MUST_Optical_Controller_NBI_Requirements_Document_v10_FINAL_VERSION_WEBSITE.pdf will include a backlog of prioritized use cases. The publication is foreseen in one month or so. 60 mins
Update on TAPI
2.3.1 Pre-release All Andrea Mazzini shows the main contents of pull request 515. Discussion on the OAS generation, the related script is becoming complex / circular because: TapiFm imports TapiStreaming TapiStreaming imports all core TAPI modules (tapi-common, tapi-topology, tapi-connectivity, tapi-equipment, tapi-oam, tapi-path-computation,tapi-virtual-network) Agreed to create two new modules, TapiFmNotif and TapiFmStreaming to better decouple TapiFm from both TapiNotification and TapiStreaming. These new modules will include only the fault management augments of notification and stream. Agreed to commit these modifications within pull request 515. Discussion on "feature" and "if-feature". Arturo asks whether there are news on yang2oas tool. A comment has been recently added to TAPI issues 494: "I can see that OAS folder is still present in future r2.3 release for TAPI. Again, if we are publishing something that we know is wrong to our own specifications, sounds like a very bad idea." Agreed to update the release disclaimer as follows: - TAPI OAS (OpenAPI Specifications) included in this TAPI release (v2.3.1) are an TAPI OpenAPI Specification part of the TAPI SDK informative and intended to support TR-547 Use Cases, where a subset of mandatory API is specified. 30 mins
Plan for 2.4 delivery
All Agreed to add in next week agenda the otcc2020.ND.013_Tapi-NotesOn2.4.pptx contribution. Discussion on OamJob, agreed that it can be applicable to almost all management items, we may explore a more versatile model. Andrea Mazzini informs that in MEF Resource Model Project has been proposed to apply the "if-feature" statement for "RPC support". The team confirmed the decision to remove all RPCs from TAPI 2.4 version. 30 mins
Resume of “GNPy/CCAMP – TAPI alignment” activity
Andrea Mazzini presents otcc2021.AM.001_TAPI-GNPy-extensions.pptx Huy Tran points out that new parameters have been defined related to Raman fiber impairments (co-effects) for a more accurate estimation. Explore the model solution, e.g. a new class which augments OTS/OMS links with Raman amplification. The defined data structure is an array of 96 coefficients, each one applicable to one frequency/spectrum value. Recalled that all the proposed "GNPy classes" can be considered as profiles, i.e. common for more instances of links, transceivers, amplifiers, etc. 10 mins Loopback feature Ronald
Ronald asks whether the loopback is a generic OAM job type or shall be defined in technology specific modules, e.g.
Ethernet loopback, DSR loopback, ODU loopback, etc. Agreed to add this item to next week agenda.