Versions Compared

Key

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

...

  •  Feedback from OVP PH2 meeting: https://wiki.lfnetworking.org/display/LN/2020-03-09+OVP+2.0+Meeting+notes
  •  Do we need to extend our ONAP VNFReqs to consider CNF Reqs or shall we suggest a "LFN CNF Reqs" Board or will it be driven by CNCF?
    •  Need to connect with CNCF to avoid duplicated effort, divergence effort Suggestion to extend our VNFRqs team to represent our CNF needs to the CNCF divergent effort
    •  Architecture, Modeling, Security reqs will feed VNFReqs+  to define what it is requested to onboard CNFs on ONAP — Shall we draft a Diagram flow?
    •  Need also to consider CNF Security reqs from SECCOM
    •  Need to consider the Architecture perspective
    •  ETSI Activities to define packages - candidate for the Guilin Release
      • ESTI reqs/packages availability - End of Q4
      • Need to define an intermediate Helm chart (TOSCA) then try to push back our findings to ESTI
    • Hydrid approach (supporting all together - CNFs, VNFs, PNFs) - need to address the network part
  • Review "Features/Capabilities - How We complement each other?"

...

  •  ONES CFP - Srinivasa Addepalli will work with Alla Goldner  on the abstract - Key item - "the value that ONAP can bring"
  •  Kenny Paulset up doodle pole for meeting cadence and 2 or 3 per week  
  •  

    Sylvain Desbureaux - Start to work on our ONAP response to Dan (CNCF)

  •  

    Try to identify where we are on the CNCF Trail Journey

  •  

    Fill in the table - how we complement each other

  •  

    Consolidation our message about ONAP Role - should be linked to our ONAP Response to Dan (CNCF)

  •  Check with Kenny, David - how to record our upcomign discussions?
  •  Attend the next VNFReQs meeting and to discuss the extension of the team's scope - Trevor Lovett
  •   Follow-up with SECCOM about CNF Security reqs
  •  Kenny Paul , create a recording section and add the recordings (2x 3/12)