Versions Compared

Key

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

...

Feb 16th, 2021 at 2pm UTC

  • ONAP/OVP - Interested in pursuing badging for ONAP CNF workloads in 2021?
    • OVP: Roadmap 2021
      • Q1: Infrastructure, in alignment with Reference Architecture 2 (Anuket)
      • Q2-Q3:
        • #1 Reference Architecture 2 Interoperability (Anuket);
        • #2 Compliance in alignment with ONAP CNF On-boarding/Instantiation capabilities
        • #3 Cloud Native workload
    • Badging will also evolve based on requirements, testing
    • Initial ONAP Community Request(s)
      • Validate if Common CNF packages are in alignment with ETSI including providing information to OVP team about outcomes from our ONAP VNF-D solution; split k8s vs CNF packages, etc.
      • Requirements related to k8S ? Maybe provided based on CNCF
    • Any request from OVP To ONAP Community to support OVP Badging?
      • Any VNFSDK requirement?
      • Any SDC requirement (onboarding)?
    • ONAP should remain "Cloud Agnostic", not tight to any RA2 requirement (Infrastructure perspective)
    • OVP is gathering requirements from the different communities; acting as "Bridge" Lead for CNF activities
    • CNCF: Focus on CNF for Telcos, best practices

Feb 23rd, 2021 at 2pm UTC

March 2nd, 2021 at 2pm UTC

  • ONAP/OVP - Inputs from/to ONAP/OVP Community in addition to what was discussed on 2/16.
  • What are the other functionalities, test coverage are available with OVP today?
  • What other communities (in addition to Anuket, CNCF, ONAP) collaborate with OVP?

Action Items (In Progress)

  •  (Seshu): Check if user-67d6f , Lei Huang , Yan Yang can join March 2nd, 2021 to discuss about OVP/ONAP & VNFSDK
  •  (Timo/Catherine): Promote 2021 goals from OVP program and collect any particular requirement through ONAP Requirement and TSC meetings
  •  (Kenny): Contact EUAG about any CNF badging requirement (OVP)
  •  (Thinh): Share the ETSI event link when it will be available
  •  (Thinh): Share an alternative (Common CNF Packaging) to what was proposed by Fernando Oliveira , Byung-Woo Jun
  •  (Olivier): Check with CNCF if any cross-meeting with ONAP could be scheduled 
  •  (All): Collect feedback about our current CNF onboarding capabilities from 3rd party vendors
  •  (All): Build an ONAP proposition value to collaborate with XGVela Community
  •  (Seshu): Questions for XGVela
    • It would be great to highlight more clearly the purpose of XGVela as a platform to build CNFs and get feedback from 3rd party vendors, who are today already creating CNFS for carriers, to assess the value proposition
    • After the CNF is created via XGVela – can we then deploy the CNF on any Cloud environment without using XGVela at run-time?
    • If we need XGVela then have we performed an analysis to demonstrate the value proposition vs K8S and its ecosystem?
    • Build a slide to highlight how XGVela (i.e. create  CNF) is complementary to ONAP (onboard CNF/orchestrate CNF, etc.) and how it will fit to the CNCF Landscape
  •  (All) Try to identify where we are on the CNCF Trail Journey - Needs clarification to comment, need to dig into the details of the actual ask.

...