Skip to end of metadata
Go to start of metadata
- Date and Time: 2019, July 1st, 9pm~10pm Beijing Time, 9am~10am US Eastern
- Meeting Room: https://zoom.us/j/645982535
- Meeting Recording:
- Meeting Chat Log:
Agenda:
- agenda bashing
- AAI reverse engineering discussion
Material:
Minutes:
- agenda bashing
- start to work under "R5 workspace"
- should we combine R5 and R6 discussion?
- update of PNF non-MANO artifact proposal
- AAI reverse engineering discussion
- Keong's presentation on PlantUML tool
- source file is the swagger API document
- result contains two parts: classes and edge rules (relationships)
- AAI is working on integrating the tool into the model browser
- suggestion:
- may use the tool to show other project's models
- may help generate xml to put into papyrus
- pro: automatic way to generate diagram, independent on schema changes, easy to navigate the whole model
- Jacqueline's presentation on Papyrus tool
- source file is XSD, edge rule file (json) and possibly traversal information (json)
- only shows classes now, no edge rules
- pro: could be directly put into papyrus, automatically show all attributes (though no descriptions now)
- question:
- attribute multiplicity/cardinality seems losing some information (e.g., pnfName should be required attribute, but the corrent result shows 0..1 for multiplicity)
- currently working on swagger → UML (a tool named wapiml)
- how to proceed:
- Xu:
- 2 approaches in mind:
- top down: start from investigating hierachy tree and work on details lately
- bottom up: start from individual targets/topics e.g., PNF, VNF instances and build the tree
- side questions:
- whether modeling subcommittee or AAI team should handle updates of the instance model (after the model alignment)
- suggestion:
- categorize by use cases, try to cover all models used by use cases
- how aai model is related to IM discussion, need to do some comparison and analysis
- AP: start with PNF instance model next week, analyze the attributes, class hierarchies, etc.; Xu will investigate on the hierarchy tree (from CCVPN) for further discussion