Skip to content

2025‐01‐21 TAPI Meeting Minutes

Jump to bottom
Brian Johnson edited this page Jan 25, 2025 · 1 revision

Attendees

  • Arturo Mayoral
  • Roshan Joyce
  • Esther Le Rouzic
  • Scott Mansfield
  • Gabriele Galimberti
  • Dacian Demeter
  • Juan Pablo Agredo
  • Kam Lam
  • Ramon Casellas
  • Nigel Davis
  • Kishore Kumar Kowthalam Gajula
  • Brian Johnson

Previous Actions

  • All: (ongoing) review current TAPI content on github and prepare suggestions for near term activities and next TAPI release

create a new issue for proposed content / activities here: https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI/issues

  • All: (ongoing) The following document has references to many documents that were lost prior to the move to the LF. Please check to see if you have any of the referred documents stored locally.

https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI/blob/tapi-team-activities/TAPI-TEAM-ACTIVITIES/Plan/Candidate%2BFeatures%2Bfor%2BFuture%2BReleases%2Bof%2BTAPI%2BSDK%2Band%2BRIA.doc

  • Namespace references in Yaml of TAPI 2.5.1, is missing. Need to find a tool to generate such Yaml files to align between Yang & Yaml.

Discussion topics

  • Welcome back Nigel
  • In-meeting signup to new google group
  • Reminder about populating "issues" with enhancements
  • Process for releasing 2.6 discussed:

Content listed at the end of the RIA Should review internally (prefer to list RCI as adjustments could cause other issues, given the inexperience of new team) Tag repository and create branch from main for patches Seek approval from steering committee

Scott's Tooling Presentation:

UML Guidelines: https://github.com/Open-Network-Models-and-Interfaces-ONMI/onmi-iisomi-uml-common?tab=readme-ov-file

Core model (moved to ITU-T) TAPI builds on the core model (TAPI UML to core model mapping not trivial) iETF and ITU provide additional coverage Presentation on core mode / TAPI model / Tooling https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Activities/blob/main/ContributionsForDiscussions/oimt2018.ND.035.02_IntroOimtProjects.pptx https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Activities/blob/main/ContributionsForDiscussions/oimt.2019.KL.005.01_Tutorial_(P4)_Guidelines-Tooling.pptx https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Activities/blob/main/ContributionsForDiscussions/oimt.2019.KL.004.00_Tutorial_(P2)_CoreModel.pptx https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Activities/blob/main/ContributionsForDiscussions/oimt.2019.KL.003.00_Tutorial_(P0)_Introduction.pptx

  • UML to Yang
 https://github.com/Open-Network-Models-and-Interfaces-ONMI/onmi-iisomi-uml-yang
 Written in Javascript - would be nice to move to more modern libraries
  • TAPI Tool User Guide
 https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Documentation/blob/v2.6.0-RC1/ToolingGuidelines/UML2Yang2Oas%20Tool%20User%20Guide.docx

*Papyrus, tool in Eclipse

 Papyrus is evolving (new dependencies) --> old models may not be compatible > 24.06
 If XMI files change, then it's more disruptive
 Could remain using 24.06 so that Gendoc will work
  • Gendoc - integral to our process, replacing this could be expensive
 Uses a data dictionary model
 Not much training info
  • TAPI uses UML --> Yang --> YAML (also called openAPI)
  • Recommendation would be to keep TAPI process intact, need to test tooling
  • Watch the Zoom recording for detailed discussion!
Clone this wiki locally