ONAP R6 Resource IM Call 2019-7-29

Owned by Xu Yang
Last updated: Jul 30, 2019
1 min read

General Information:

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

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

  • Meeting Recording: 

  • Meeting Chat Log: 

Agenda:

  • AAI reverse engineering discussion

  • Modeling Process discussion

  • R6 high level requirements - brainstorm

Material:

Minutes:

  • Agenda bashing:

    • Kevin mentioned he is working on the license model, and hopefully to share in 2 or 3 weeks' time

    • Ben shared a wiki page: LICENSING MANAGEMENT for R6 use case on license management

      • already have several weeks' discussion

      • no progress yet

  • AAI reverse engineering discussion:

    • PNF instance model:

      • suggest to also include a comparison between SDC internal PNFD model with the AAI model

        • according to the discussion, SDC doesn't utilise all the information from the onboarding PNFD (e.g., version, security are not used), and create several properties itself (e.g., SDC allocate PNFD id and invariant id by itself, ignoring the ones provided in the onboarding model)

        • AAI fetch the necessary information from what SDC publish

        • mapping among onboarding model, internal model and AAI instance model is interesting topic to capture (and the gaps are obvious)

      • maybe it's enough to have AAI team to help understand how the AAI model instantiated and get values

    • CCVPN use case:

      • filter out the models in the AAI which are used by the CCVPN use case

      • next step:

        • check if customer branch is correct according to the latest schema

        • adding more details like attributes there

  • Modeling Process:

    • review the M0 bullets

    • modify the catogeries for the high level requirements

  • R6 high level requirements - brainstorm / no discussion due to time limit

    • candidates per last call:

      • AAI reverse engineering

      • continue policy discussion

      • SDC gap analysis

      • further ETSI alignment