1. Pages
2. …
3. OIMT
4. IISOMI
5. IISOMI Minutes

2022-01-14 IISOMI Meeting notes

21 Jan 2022 Leader: Andrea (Bernd not available) 

28 Jan 2022 Leader: Nigel

04 Feb 2022 Leader: Kam

11 Feb 2022 Leader: Bernd

18 Feb 2022 Leader: Scott

All

IISOMI Action Items review (every meeting)

Action items done

Refreshed Action Items

• Andrea Mazzini 21 Jan 2022 Create a Guideline/Tooling wiki page(s) for listing the tasks
• Scott Mansfield 18 Feb 2022 To take the gendoc examples from the guidelines and perform regression test. 
  • Also decide on version of gendoc and Papyrus
  • Version for initial regression test is p2020-06
•  Scott Mansfield 18 Feb 2022 To investigate why none of the <<cond>> is retrieved from the model (confirm with Andrea Mazzini 
  • Andrea indicated the had attempted to apply analogous rules to member-end to include other properties. Andrea tried various techniques to get client and supplier but with no success 
    • Probably need to review the UML metadata
  • Andrea was able to print the target string
• Scott Mansfield 18 Feb 2022 To investigate how to get client and server values for an abstraction association for gendoc.
  • From 2021-12-03 IISOMI Meeting Minutes
• Nigel Davis 21 Jan 2022 determine what Jira form structure etc. ONF can create IISOMI. Provide example/detail etc. for discussion.

O-RAN cooperation

October 1: O-RAN policy has changed collaboration rules. (O-RAN Alliance is registered in Germany)

October 15: Martin Skorupski checked with O-RAN the tooling funding status.  There is hope, not dead, but not moving either. 

Martin Skorupski 19 Nov 2021 Get a written statement from O-RAN leadership on state of tooling funding's

November 19 discussion: Martin reported on the progress of requesting funding from O-RAN for UML-YANG tooling. The proposal will be up for voting in O-RAN.  

• Martin Skorupski 21 Jan 2022 To update on the progress in O-RAN of getting approval of an O-RAN project on UML-YANG tooling
  INFO: Tracy van Brakle publish a document as proposal for O-RAN TSC 
  https://oranalliance.atlassian.net/wiki/download/attachments/2211414051/ATT.2021.11.30-WG10-IM-DM_Tooling_Informational_Report-v00.02.docx?api=v2
  

Papyrus Releases

• • Consider a plan for convergence of ITU-T Q14/15, ONF Common IM and TAPI to 2020-06 (4.16) version
  • Prior discussion: IISOMI 2021-09-24 Meeting Minutes
    • Reaffirmed the need to explore 2020-06 (4.16) version

November 19 discussion: The TR-512 v1.5 Core model was developed using Eclipse 2019-09. It the model can migrate to 2020-06 seamlessly, Q14/15 might move G.7711 v4.0 (12/2021 consent) also to Eclipse 2020-06. To verify the seamless migration: 

• Nigel Davis 14 Jan 2022 Try to move TR-512 v1.5 core model to 2020-06 (4.16) Eclipse
• Hing-Kam Lam Try to move TR-512 v1.5 core model to 2020-06 (4.16) Eclipse

2021-12-03: 

• from Kam - diagrams from TR-512 v1.5 core model on 2020-06 (4.16) Eclipse looks fine
• proposal for next week ITU-T: IISOMI moves to 2020-06, because gen-doc works find 
• TAPI will follow after some tests will be done by Andrea Mazzini

• Nigel Davis 21 Jan 2022 Try to move TR-512 v1.5 core model to 2020-06 (4.16) Eclipse

Prior discussion: 2021-10-29 IISOMI Meeting Minutes #2

Prior discussion pointed out that:

• a private repository is not the appropriate place for the items since not everyone has access to this
• the ONF GitHub is publicly available but not all participants are allowed to contribute to it
• there is no single ONF repository which could host such Issues; IISOMI is spread over many repositories
• it might be possible to cover the discussions in Wiki pages
• new discussions should be captured in the Meeting Minutes and then copied to the Wiki pages
• Bernd Zeuner 08 Oct 2021 Draft an example Wiki page that capture an discussion item

Proposal wiki page from Bernd for capturing discussion items:

• IISOMI Discussions

2022-01-07:

• Follow-up after progress made with Jira ( 14 Jan 2022 ) as per action for Nigel Davis 

Andrea Mazzini

Hing-Kam Lam

Prior discussion: 2021-10-29 IISOMI Meeting Minutes #5

• Bernd Zeuner 15 Oct 2021 Update the Mapping Guidelines with a rule that artefact names within the descriptions should be converted to YANG style.

2022-01-07:

• Bernd will upload the draft (IISOMI Deliverables)
  • Bernd Zeuner 14 Jan 2022  Upload latest mapping guidelines to IISOMI Deliverables
    → Done: IISOMI 531 UML to YANG Mapping Guidelines (new editor Karthik)

Prior discussion: IISOMI 2021-09-24 Meeting Minutes #9 and 2021-10-01 IISOMI Meeting Minutes #8

Prior discussion: IISOMI 2021-09-24 Meeting Minutes #10

All
Hing-Kam Lam

Prior discussion: 2021-05-28 IISOMI Meeting notes #6

• Scott Mansfield  18 Feb 2022  Provide  gendoc  examples  to  implement  the  first  two bullets
  • 2021-05-28 IISOMI Meeting notes #6
  • GenDoc didn't generate constraint
  • GenDoc OstigOTtpSource::txti:EByte multiplicity [64] is not generated correctly
  • Discussion Needed:  To agree on a specific format for operation, then implement

2021-12-03

from OIMT

CoreModel FD - to of the tree

Composed FC-Switch .... with no sense if independent

.

Driver of Model structure (arrangement)

usage of stereo-types

• aggregate
• leaf
• admin relationships
• Chris has nice ideas - but needs to be further analyzed.

First try of "modelling profiles" on CoreModel

Target:

• Split CoreModel in "smaller" parts - decoupling 
• Rules needs to be described/defined/documented.

Further details:

• https://wiki.opennetworking.org/download/attachments/266141701/ONF_T64_DddAggregates.pptx?api=v2

2022-01-07:

• Nigel Davis noted that OIMT have agreed to develop the profile and apply to a part of the core as an example. This can be presented to IISOMI in February.

• Nigel Davis 18 Feb 2022 Provide an overview of the DDD trial profile and show application to the core model.

Andrea Mazzini Italo Busi