Table of Contents maxLevel 2
...
- 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?
...
- 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.
...
- 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
- 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
...
- Thinh Nguyenphu (Unlicensed) Fernando Oliveira Byung-Woo Jun - Share:
- what is going to be presented to ETSI-NFV on April 21st.
- Byung presented the slide deck:
- SOL004 compliant CNF package
- SOL007 Network Service package is under discussion
- Large package handling - SDC work to upload packages to ETSI repository
- SOL005/SOL003 interfaces for NFVO/VNFM
- SOL018 - Interface towards the Cloud Platform (K8S) - For now it is just K8S API. The plan is to align the ETSI and non-ETSI flows in ONAP and to use native K8S and Helm APIs in both paths.
- Draft of the slides presented: - 2021_NFV_Evolution_Presentation_ONAP_ETSI-Alignment_21042021-v9.pptx
- Byung presented the slide deck:
- What ETSI-Alignment work is planned for Istanbul? - In the context of modeling
- https://wiki.onap.org/download/attachments/93011619/ONAP%20ETSI-Alignment%20Requirements-Istanbul.pptx
- Proposed R9+ VNF/CNF Data Model Based on ETSI SOL001 v4.2.1 - no resources. Postponed to "J" release.
- [REQ-637] ETSI-Alignment for the Istanbul release - ONAP
- cl664y@att.com recommends raising awareness to the ETSI alignment work in order to recruit additional developers.
- Non-ETSI plan for Istanbul
- SDC, SO and A&AI work is planned.
- Seshu Kumar Mudiganti - Some XGVela related requirements might arise from the ONAP/XGVela integration work. The goal is to address them during Istanbul.
- Alternative CNF packaging (from Nokia) - How much time do we still have? cl664y@att.com proposes to move ahead with the packaging proposed by Fernando Oliveira and Byung-Woo Jun. Marian Darula mentioned that the current proposal has a challenge with information duplication. Andy Mayer - Discussion on CNF modeling is welcome during the Istanbul release time frame, even if implementation will come later.
- what is going to be presented to ETSI-NFV on April 21st.
April 8th, 2021 at 1pm UTC
...
- ONES - Call For Proposals (CFP) | Linux Foundation Events - deadline: June 20th, 2021
- LFN DDF Event on June 7th-10th - Proposal to be submitted by May 14th - https://wiki.lfnetworking.org/display/LN/2021+LFN+Developer+Event+Topics+June
- Review our ONAP CNF proposal for LFN DDF (1h) -
- Latest Honolulu features - Lukasz Rajewski, Seshu Kumar Mudiganti, Konrad Bańka + Fernando Oliveira, Byung-Woo Jun
- Marian Darula, Byung-Woo Jun, Thinh Nguyenphu - CNF packaging/modeling recommendations on May 6th, 2021
- Proposal covers packaging and descriptor; ETSI Compliance, Advanced Semantic Discovery (ASD) with Network Service Descriptor (NSD)
View file name ONAP_Nokia_Ericsson_K8S_application_descriptor_and_packaging_r2.pdf height 250
...
The Honolulu release has important updates to support cloud native network functions (CNF). The functionality includes configuration of Helm based CNFs and seamless day 1, 2 operations. The Configuration API allows a user to create, modify and delete Kubernetes (K8s) resource templates and their base parameters and the Profile API allows for sophisticated day 0 configuration. The Query API gathers filtered status of the CNF and the HealthCheck API executes dedicated health check jobs to verify the status of a CNF. This new functionality is implemented in the Controller Design Studio (CDS) component using dedicated templates called Controller Blueprint Archives (CBA).
- DCAE simplifies microservice deployment via Helm charts and includes a new KPI microservice. The VES-OpenAPI-Manager allows easier validation of new xNF types against supported VES StndDefined domain improving compliance with 3GPP and O-RAN
Application Programming Interface (APIs)
- Logs are redirected to SDTOUT
- ONAP Components are containerized and are deployed on virtual, shared and elastic infrastructure.
- Built based on DevOps Toolchain (CI/CD, Gating, etc.)
Additional separated key messaging: Support ORAN SC SMO + Support Enterprise business (E2E Network Slicing, etc.)
...
- EMCO Update - Upcoming meeting on Wednesday June 23rd 6:30AM PDT
- ONE Summit - CFP Deadline is June 20th
- ONAP CNF orchestration Progress and roadmap - cl664y@att.com Seshu Kumar Mudiganti Lukasz Rajewski Ranny Haiby Byung-Woo Jun
- Abstract submission - Ranny Haiby - submit as a panel - circulate draft by email
- ONAP CNF modeling and orchestration (ETSI, ASD and beyond) - Fernando Oliveira Thinh Nguyenphu (Unlicensed) Byung-Woo Jun cl664y@att.com
- Abstract submission - Thinh Nguyenphu (Unlicensed) - submit as a panel - circulate draft by email
- ONAP CNF orchestration Progress and roadmap - cl664y@att.com Seshu Kumar Mudiganti Lukasz Rajewski Ranny Haiby Byung-Woo Jun
June 24th, 2021 at 1pm UTC
...
- ONAP slide(s) for the LFN Cloud Native messaging - continue work on the slides
- Updated deck during the meeting (v4c): ONAP_Cloud_Native_v0.4c.pptx
- Byung-Woo Jun, added some update... in progress... feedback is needed
- Updated deck during the meeting (v4c): ONAP_Cloud_Native_v0.4c.pptx
- Brandon WickExample of ONAP Marketing Slides (Honolulu Release Deck)
- ONE Summit sessions - https://events.linuxfoundation.org/open-networking-edge-summit-north-america/program/schedule/
- "Building modern cloud-native network services with ONAP" - accepted. Will be a virtual session. LF events confirmed presenters may attend in-person, and present this as a virtual session.
- Schedule: Monday, October 11 • 2:40pm - 3:10pm (30 mins)
- Decide on format: Panel or presentation + Q&As – 20 mins + 10 mins
- Prepare content - re-use our Cloud Native Sales pitch and probably enhance it based on the latest capabilities available in Istanbul ???
- Pre-record
- ASD session - waitlisted - Thinh Nguyenphu (Unlicensed) will follow-up with LF event to get additional clarifications
- "Building modern cloud-native network services with ONAP" - accepted. Will be a virtual session. LF events confirmed presenters may attend in-person, and present this as a virtual session.
...
- ASD Readout (Marian Darula , Byung-Woo Jun )
- Work on our ONAP CNF_Cloud Native Roadmap_V2.pptx
- Jakarta Timeline: Kick-Off on 10/14 and submit reqs no later than 12/2 (M1)
- Plan CNF/Cloud Native Task Force readout with the ONAP TSC
- Session 1 - ASD Readout and ETSI CNF Package Evolution (45 mins) - date: Oct 7th, 2021 (TBC) - Fernando Oliveira , Marian Darula , Byung-Woo Jun , Thinh Nguyenphu (Unlicensed)
- Session 2 - Jakarta requirement candidates - Nov 4th & Nov 18th
...
- MEETING WAS CANCELED - low attendance
- Finalize new landing page
Action Items (In Progress)
- Lukasz Rajewski - Follow up with Seshu to plan EMCO integration
- (CNF Task Force): What do we need to ask to CNF Vendors to be onboarded on the ONAP Platform? These reqs could be shared with Anuket Assurance for the CNF badging
...
- December 14th, 2021 at 2pm UTC
Action Iems (Closed in 2021)
- (Thinh Nguyenphu (Unlicensed)) / Marian Darula / Byung-Woo Jun : Nokia and Ericsson share an alternative (Common CNF Packaging) to what was proposed by Fernando Oliveira , Byung-Woo Jun
- (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.
- (All): Build an ONAP proposition value to collaborate with XGVela Community
- (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 Morales/ Ranny 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 Former user (Deleted) , Lei Huang (Unlicensed) , Yan Yang can join March 9th, 2021 to discuss about OVP/ONAP & VNFSDK
- (Thinh): Share the ETSI event link when it will be available
- (Seshu): Questions for XGVela
...
- cl664y@att.comFollow-up with the Modeling Subcommittee about yan yanrequest
- @Thin to upload presentation from May 6th call
- Kenny Paul - Reach out to FB to meet us on May 12th, 2021 (ONAP For Enterprise Task Force) - request made to LF PM - just checked no name yet.
- cl664y@att.com: Introduce Amy Zwarico to Anuket, CNCF and OVP PH2 Communities and share SECCOM Container Logging specs
- (ALL): Provide feedback regarding Thin's proposal presented on May 6th, 2021
- (Andy Mayer , Hui Deng ) Follow up regarding Modeling team about CVC request - Re: Request from CVC
- Kamel Idir - Will repeat onboarding with Honolulu (once he has the lab resources) and will report back
- (Byung-Woo Jun: Bring the discussions to the ONAP Architecture Subcommittee about SO/SDNC role etc (see notes from 4/29)
- Ranny Haiby - Create a first draft of the "ONAP cloud-native" messaging slide and share with the Taskforce.
- Ranny Haiby , Byung-Woo Jun , Timo Perala , Seshu Kumar Mudiganti to discuss the enhancement of our ONAP Cloud Native Vision/Roadmap, this with Architecture, Requirement & MAC subcommittees
- Brandon Wick- will collect additional information about the ONES event (virtual, F2F present, etc.)
- cl664y@att.com: Plan CNF Task Force readout with the ONAP TSC
- Lukasz Rajewski - Ask Orange colleagues to present EMCO↔Multicloud comparison
- (All) Feel free to provide feedback about ASD packaging (Orchestration Scenarios)
- (Modeling/Requirements): Need to determine what ETSI CNF package solution we want to move forward (Fernando Oliveira, Byung-Woo Jun vs Thinh Nguyenphu (Unlicensed))
- (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
- Try to locate missing meeting recordings (Sept 30th & Oct 14th, 2021) - cl664y@att.com
- Lukasz Rajewski - Follow up with Seshu to plan EMCO integration