CNF 2021 Meeting Minutes

Jan 7th, 2021 at 3.30pm UTC 

• Review our Calendar - Decision to setup CNF Task Force call every Tuesday at 2pm UTC until Daylight saving time will end in March
• Review (and refine if necessary) this taskforce goals. Other than the on-going work, what is the next big thing we want to tackle as a taskforce?

#1 Define/Implement CNF Release Requirements

#2 Promote what we have developed

#3 Define new use cases considering latest Industry/Vendor/Open Source solutions i.e. XGVela, Anuket

• Continue discussion between Aarna and SO team to figure out if some of the Aarna work can be re-used by SO
• Any topic we want to submit for the February DDF event?
  • What will be ONAP priorities to remain in alignment with Industry/Standards?
  • What would be our ONAP 2021 CNF Task Force priorities (after Honolulu) - brainstorming?
  • Video Guilin CNF?
  • CNF Task Force Office Hours
    • Have the leaders of this activity (Seshu Kumar Mudiganti Lukasz Rajewski Fernando Oliveira Byung-Woo Jun) and other members of the Taskforce available for Q&A from the community.
    • The priorities brainstorming (suggested above) can be part of this session.

Jan 12th, 2021 at 2pm UTC 

• Recap what was discussed last week
• Review CNF Event submission
  • One single ONAP CNF Session at DDF  (1h) but open to cross-community sessions
    • (20 mins) - Where we are - covered through demo or video? Lukasz Rajewski, Seshu Kumar Mudiganti
    • (10 mins) - Recap Honolulu requirements (ETSI ) Fernando Oliveira, Byung-Woo Jun + (CNF Orchestration) Seshu Kumar Mudiganti, Lukasz Rajewski
    • (30 mins) - Open discussions - Ranny Haiby
      • Collecting feedback from the ONAP Community or external Communities/SDOs about 2021 CNF priorities
      • Call for new requirements?
      • Call for developers
• EAUG - is there any CNF requirement in their 2021 wish list?
• Reconnect with the CNF Sub-tasks (ETSI & CNF modeling/AAI)
• New CNCF principles - probably to check in February 2021
• OVP - Badging for the infrastructure - anything we should consider for ONAP this year?
• Review Satoshi Fujii- Presentation - CNF Control Loop

Jan 19th, 2021 at 2pm UTC 

• Reconnect with ETSI CNF Team and CNF Modeling/AAI
  • VNF/CNF Data Model Based on ETSI v3.3.1 SOL001 plus CNF Enhancements
  • ETSI IFA011 v3.3.1 & v4.1.1 Changes to ONAP Resource Model.
  • Additional feedback from Fernando Oliveira about Honolulu release:
    • SDC focus, SO work will be kicked-off but will be finalized in Istanbul
    • AAI model change - not yet fully developed, AAI model finalized in Istanbul
    • Creation of the CSAR 
    • Presentations planned during the DDF event
      • ONAP ETSI NFV joint container data model workshop and latest modeling subcommittee process update
      • ONAP ETSI-Alignment NS, VNF/CNF Orchestration Architecture for Honolulu
      • ONAP 5G Slicing using ONAP Service(s) and ETSI Network Service(s)
• DDF Topic submitted by Timo Perala: ONAP MultiCloud k8s plugin enhancement for CNF deployment
  • Nokia Team has been prototyping in this space and would like to share their findings during the DDF event
  • Timo will contact the team and will ask them to provide some preview material on 1/26
• Lukasz Rajewski - Use of EMCO instead of k8splugin
  • The Edge Multi-Cluster Orchestrator (EMCO) is a software framework for intent-based deployment of cloud-native applications to a set of Kubernetes clusters, spanning enterprise data centers, multiple cloud service providers and numerous edge locations. It is architected to be flexible, modular and highly scalable. It is aimed at various verticals, including telecommunication service providers.
  • Discussion about GitHub - open-ness/EMCO
  • Shall we continue to use it even if it is not part of ONAP umbrella?
  • No control of the code, it is not a library neither a docker - dependency on open-ness release cycle  
  • EMCO License is Apache 2.0
  • Need to check if security requirements are aligned with ONAP SECCOM (i.e. test coverage, critical vulnerability, ONAP global requirements, ONAP approved best practices, S3P, etc.) => We might need to fix any concern ourselves directly to open-ness repositories
  • EMCO Architecture & Design

• DDF Event: 
  • ONAP Cloud-Native (CNF) Taskforce - open discussion on current state and future plans
  • Please vote - https://lists.onap.org/g/onap-discuss/message/22742
    

Jan 26th, 2021 at 2pm UTC 

• Review  ONAP MultiCloud k8s plugin enhancement for CNF deployment DDF topic witht the CNF Task Force

• Review CNF Closed Loop proposal (Satoshi Fujii) with PTLs (SO, AAI, DCAE and Policy)
   
  
  • Consider EMCO as part of the CNF Closed loop
  • Great Feedback provided by AAI/DCAE/Policy/SO Project Team members (listen to the recording )

No CNF meeting on Feb 2nd, 2021 (DDF event)

Feb 9th, 2021 at 2pm UTC

• Invite Open-Ness representatives to discuss about EMCO
• Upcoming ETSI NFV Workshop on April 12 - Thinh Nguyenphu  
• Schedule discussion between ETSI NFV team and Direct path team.
  • Common CNF packaging
  • VNF-D needed?
  • Other artifacts needed?

Action Items (In Progress)

• (Olivier): Check with CNCF if any cross-meeting with ONAP could be scheduled 
• (Olivier): Organise a call with Trevor Lovettand any interested CNF team members to determine how ONAP could contribute to the OVP 2021 activities
• (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 3^rd 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.

Action Items (Closed in 2021)

• (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
• (Ranny): Post the topic for the event