Child pages
  • 2022-02-17 OIMT Meeting notes

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

Attendees

Agenda

  • Admin: vF2f dates, outgoing LS 
  • TAPI and Wireless transport: Moving away from simple packaging (ND, AM, MS) 
  • Discuss the intent grammar, spec grammar. Explore mechanism converting explicit property sentence into constraint statements. (ND) Only briefly introcued. Will continue next week.
  • Example for separate occurrence (as per action item) and update on modeling of occurrence (ND) Deferred to next week due to running out of time.
  • Equipment property model sketch (KL, ND) Deferred to next week due to running out of time.
  • AOB

Discussion items

Time

Item

Who

Notes

5 minAdminAll

OIMT 2022 Virtual F2F in 2022. 

Draft LS to SG15 and MEF on the  ONF open github https://github.com/OpenNetworkingFoundation/CoreInfoModel for the TR-512 releases 

50  minTAPI and Wireless transportND, AM, MS

TAPI and Wireless transport: Moving away from simple packaging (ND, AM, MS) 

  • Two usages of the TR-512 Core model.
  • Wireless uses the pruned/refactored Core model as the Wireless core model
  • TAPI refactored the Core model significantly
  • Both of them used the uml-yang mapping tooling to generate the Yang.
  • TAPI requires its model to be in particular package-structure & model arrangement in order to generate the Yang from the tooling. 
  • Wireless is based on v1.4 of the Core model. If the Core model structure packaging changed, Wireless needs to adapt to that.
  • Potential impact on TAPI: On the new items, such as the control model. TAPI to decide whether need to do the same refactoring or not.  
  • CH: The Aggregate should help the mapping; it relates to the Yang containment. 
  • OIMT is now taking the DDD (Domain Driven Design) Aggregate as the driver to re-packaging the Core model appropriately, so that 
    • Have independent small model units 
    • Allow independent parallel working on the model units
    • On the Core Network model: grouping around the key classes, e.g., LTP (Lp and association), FC (....)
  • Breaking down the model into smal units/trees
    • ForwardingConstruct.
    • New stereotypes: <AggRoot> for global classes,  <AggLeaf> for local classes
    • Refactored the model to remove aggregate violations.
    • FC (AggRoot) has four AggLeaf: FcRoute, FcPort, FcSwitch, FcCasc. 
    • Leaf is not accesible from outside. The Root is.
    • Leaf can access out (out to a Root is fine)
    • Can reference out from a Leaf. Cannot reference into a Leaf.
    • Still investigating FcPort  
  • Wireless is using CASC relating to some protection switching schema. Didn't use it, but things broke. Then use it and worked.
  • Casc has been breaking down to FcCase, FcSwitchCasc, CascCore, CascCoordinate, ...
  • Clarification of the collection of the global classes (aggregates) and local classes.
  • Re-Packaging the CoreNetworkModel:
    • The packaging is goruping around the aggregate root, e.g., ForwardingConstruct. Each aggregate has its own root and Leaves. No split of associations, datatype, 
    • And also refactoring some parts of the model, if it violated the aggregate structure.
    • No renaming things
  • CH: Mapping spreadsheet. Old path to New path. 
  • AM: Will this repackaging change the final result?
  • CH: Similar to Java. Proper path name.
  • CH: Yang is not using packaging 
  • AM: On implementation, people is looking to YANG, not UML. Will this improve the resulting yang?
  • CH: https://wiki.opennetworking.org/download/attachments/266141701/ONF_T13_Model%20Structure%20Overview.pptx?api=v2
  • ND: Here is a forest of trees. TAPI one big tree.
  • The Tapi model consists of a set of model files. These model files are related through augmentation. 
    • E.g., Topology, Connectivity. Each generates Tapi yang file.  
    • LTP is in Topology and also in Connectivity
  • MS: One big Wireless Core model, then have separate technology-specific augmentations. 
  • ND
  • MS: Pursuing Tooling funding. One time funding. Big enough to support couple years 
  • ND: refactor/re-package the model and need to ensure the uml/yang tooling is still work
  •  Nigel Davis  Martin Skorupski To prune/clean-up LTP and FC modle into two interrelated small models (aggregates) and then generate YANG from them.


5  minIntent/Spec grammarND, MS

Discuss the intent grammar, spec grammar. Explore mechanism converting explicit property sentence into constraint statements. (ND)  

Only briefly introcued. Will continue next week.

  • MS: will be good to see some concrete examples
0  minOccurrenceND

Example for separate occurrence (as per action item) (ND) Deferred to next week due to running out of time.

0  minEquipment model KL, ND

Equipment property model sketch (KL, ND) Deferred to next week due to running out of time. 

0 minAction item

Actions

Action items completed

  • Nigel Davis    Discuss with the TAPI and Wireless transport: Moving away from simple packaging, e.g., object class, datatype, to a much deeper structure. This will not work with the uml2yang tool. Therefore the model will need to be refactored into object/datatype for uml2yang tool. Action item from 2020 OIMT Virtual Face to Face - Week of April 13

Action items re-dated 

The following are proposed dates for the past actions. The action list has been updated to reflect this. The actions can be reverted/adjusted as necessary. Only actions that have been moved are listed.

Note that now provided in the bullet under each action item is the link to the source minutes that created the action item.

 0 minNext calls

 

  • Discuss the intent grammar, spec grammar. Explore mechanism converting explicit property sentence into constraint statements. (ND) 
  • Example for separate occurrence (as per action item) and update on modeling of occurrence (ND) 
  • Equipment property model sketch (KL, ND) 
  • Papyrus model migration (for LtpPort) (ND, MS)

Future calls agenda items

  • TIP/MUST papers (CH, ND)
  • Catalog / inventory storage application (CH, ND)
  • MEF W130 device physical & environmental specification. OIMT may need to engage MEF on that. (CH)
  • IETF work on physical inventory model (ND)
  • RBAC vs ABAC (June 2021 F2F meeting Tue 1.2 ) 
  • Finalize the write up on Multi-point Media Channel (later call) (Candidate for v1.6)
  • To recap the previous OIMT discussion on synchronization management IM (later call)
  • YANG augmenting 
  • Leo on location model

Action items

  •