ONAP R4 Resource IM Call 2019-6-24

General Information:

• Date and Time: 2019, June 24th, 9pm~10pm Beijing Time, 9am~10am US Eastern

• Meeting Room: https://zoom.us/j/645982535

• Meeting Recording: zoom_0.mp4

• Meeting Chat Log: meeting_saved_chat.txt

Agenda:

• PNF software version proposal update

• AAI reverse engineering discussion

Material:

• ONAP R6+ Onboarding VNF/PNF package format, non-MANO artifacts set definition

Minutes:

• PNF software version proposal update

  • the detailed proposal has been updated on page ONAP R6+ Onboarding VNF/PNF package format, non-MANO artifacts set definition

    • options for file directories:

      • option 1: a single directory containing all ONAP non-MANO artifacts (i.e., files)

      • option 2: each category of ONAP non-MANO artifacts may have one dedicate directory

      • maybe option 2 is preferred

    • file name needs feedback

    • what would be like if a package including both MANO and non-MANO artifacts

      • example is available on 5G - PNF Pre-Onboarding & Onboarding

      • non-MANO artifacts have a tag in the manifest

        • should MANO artifacts also have a tag in the manifest? 

    • CSAR structure

      • currently only support option 1, not precluding option 2 in the future

    • security aspectes

      • VNFSDK has done some implementations, some are left for Frankfurt release, may need further check

  • ONAP hasn't fully established the registration process with ETSI (ETSI ask to provide more examples to show how to use the registry/artifacts)

    • Andrei/Michela are working on it

  • Andrei suggest to keep track of updates to the non-MANO artifacts

    • wiki pages are created per release now

  • Next step:

    • try to finalize the open questions this week

    • ask for a poll (if the proposal is ready) on next week's modeling subcommittee call

• AAI reverse engineering discussion

  • problems: AAI has a large data model, not sure which part are common to be put into IM

  • AAI data model visualization results:

    • PlantUML:

      • AAI OXM Schema UML

      • AAI EdgeRules UML

    • Papyrus:

      • Reverse-engineering AAI data model to Papyrus information model

  • Jacquiline's view: point to AAI's UML model, IM team working on part of the model which are considered as "common"( ? )

    • AAI can update their own model simultaneously

    • figure out the common model is not feasible

  • Keong: AAI's data model is designed to be shared, though which projects are using the model isn't documented well; track DMaaP events/AAI logs could be helpful

    • AAI Schema Producer-Consumer Pairings

  • Andy: analysis of APIs would be helpful

  • Questions:

    • could we make the assumption AAI provides a common model for the runtime?

      • seems yes

      • IM may help provide mappings between AAI model and standards

  • Keong and Jacquiline would help give presentations on the tools and results of AAI reverse engineering next week