Versions Compared

Key

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

...

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

    Action Items (In Progress)

      • Update from Olivier Smith - Change of chair in the OVP program. OVP 2.0 is being rebranded as "Anuket Assured". First badge will be released this summer, aligned with Anuket RA2. Working with the CNCF on cloud-native behavior for network functions. That will take some time to mature. OVP 2.0 is not writing  requirements. It is coordinating the tests and requirements between the various communities. Expectations from ONAP is to  have well-defined CNF modeling and a set of tests for verification. Validation tests in ONAP may exist in VVP or VNFSDK. No preference from the "Anuket Assured" side.
      • Update from user-67d6f - During Frankfurt, The "CNF Conformance" tool from the CNCF was integrated into VNFSDK. Based on the CNF modeling approach chosen by ONAP, VNFSDK may need to be updated. This was part of the CNTP effort. REQ335- REQ338https://wiki.onap.org/display/DW/Guilin+Release+Requirements
      • user-67d6f may continue serving as the main ONAP contact point, representing the VNFSDK.
      • VVP contact point -  steven stark
      • What kind of validation should ONAP require for CNFs? Packaging and on-boarding only?
        • On-boarding=SDC. SDC can now ingest and distribute Helm charts. In future releases it will also be validated. In Honolulu there is work to support ETSI packaging (SOL004).
      • Do we want to cover more (E.g. the application layer functionality of the CNF)?
        • We should probably not go into the application layer. This means we will follow the same approach we used for VNFs.
      • There will probably be different badges for different levels of conformance.
    • ETSI Event - April 21st - https://www.etsi.org/events/upcoming-events/1892-nfvevolution

    March 18th, 2021 at 2pm UTC


    Action Items (In Progress)

    •  (Seshu): Check if user-67d6f , Lei Huang , Yan Yang can join March 9th, 2021 to discuss about OVP/ONAP & VNFSDK
    •  (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.

    ...

    •  (Timo): Ask the Nokia team to present preview material on 1/26
    •  (Catherine): Contact Policy/DCAE/AAI/SO PTLs to attend January 26th CNF Task Force call to review Satoshi FujiiCNF Closed Loop proposal
    •  (Catherine): Send Calendar invite - every Tuesday @2pm UTC
    •  (Catherine): Reconnect with the CNF sub-Task force: Modeling/AAI (Andy Mayer) and ETSI (Byung-Woo Jun and Fernando Oliveira ) to understand their 2021 goals on January 19th 
    •  (Kenny): Follow up with EUAG in order to determine if any particular CNF reqs (or 2021 ONAP requirements including an update to the ONAP TSC)
    •  (Seshu/Lukasz): Invite EMCO representatives
    •  (Olivier): Organise a call with Trevor Lovettand any interested CNF team members to determine how ONAP could contribute to the OVP 2021 activities
    •  (Ranny): Post the topic for the event
    •  (Catherine) Check with Olivier Smithif we can postpone OVP/ONAP discussion to another week so CNF PDN Gateway discussions can be scheduled on  March 2nd, 2021
    •  (Victor MoralesRanny Haiby): Setup additional follow-ups about CNF PDN Gateway
    •  (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)
    •  (Seshu): Check if user-67d6f , Lei Huang , Yan Yang can join March 9th, 2021 to discuss about OVP/ONAP & VNFSDK
    •  (Thinh): Share the ETSI event link when it will be available