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
- One single ONAP CNF Session at DDF (1h) but open to cross-community sessions
- 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
- 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:
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
#1 Invite Open-Ness representatives to discuss about EMCO : Ritu Soodand Todd Malsbary to provide update on the helm charts. Guidance to address few comments. How to treat EMCOv2 (Multi Cloud K8s plugin). Some options:
- Use binary images from external repositories (Similar to databases, Vault and others) where docker images of EMCOv2 is used from Public docker repositories
- Treat it as external upstream project, but build and publish the docker images in ONAP registry.
- Go with the approach adopted for ODL (where source code is replicated in ONAP repos and constantly synchronize with upstream).
- Let the deployment admin deploy EMCOv2 before deploying rest of ONAP.
<Will be re-discussed as soon as Green light received from LFN>
#2 Upcoming ETSI NFV Workshop on April 12 - Thinh Nguyenphu
Event link not yet available
Fernando Oliveira, Byung-Woo Jun will represent the ONAP Community (ETSI & CNF Task Forces) at this event - Thank you !
#3 Discussion between ETSI NFV team and Direct path team presented by Fernando Oliveira and Byung-Woo Jun
- Common CNF packaging
Challenge: Find vendors willing to submit their commercial NF to the ONAP Community
Suggestion to use: https://www.open5gcore.org/ and https://free5gc.org/
Reference CNF: https://github.com/electrocucaracha/gw-tester
- VNF-D needed?
- Other artifacts needed?
Feb 16th, 2021 at 2pm UTC
- - 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
- OPV NFVI portal: https://nfvi-verified.lfnetworking.org/#/
- 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
- OVP: Roadmap 2021
Feb 23rd, 2021 at 2pm UTC
- Thinh Nguyenphu - Share an alternative Common CNF Packaging - postponed to March 9th - work on CNF packaging is running a bit behind schedule.
- Nokia is exploring on "CNFD", similar to the existing "VNFD" and "PNFD". A CNFD may be treated similarly to a PNFD, which is sort of a black-box, and handed over to another entity like K8S to orchestrate.
- Marian Darula commented - introducing a CNFD in addition to a VNFD creates a challenge for xNF vendors. Why not re-use the VNFD? Thinh Nguyenphu - CNFD orchestration is based on Helm charts and not TOSCA, hence a VNFD is not very useful for CNF orchestration.
- Nokia aims to separate resource orchestration (in the Helm chart) from application orchestration (in the CNFD).
- Marian Darula - There is urgency in finalizing the packaging - vendors need to deliver CNFs.
- ESTI Workshop updates - Thinh Nguyenphu - New dates: April 21st and 22nd, 2021 - Registration link to be shared as soon as available
- EMCO
- Next steps discussed on TSC 2021-02-18
- Update from Victor Morales : CNF Reference (Core Network)
- https://github.com/electrocucaracha/gw-tester/
- https://github.com/gw-tester/pgw
- Request from Lukasz Rajewskito have additional follow-ups (deployment, modelling, etc.)
March 2nd, 2021 at 2pm UTC
- CNF Reference deep-dive
- Walkthrough of the Core Network reference CNF (https://github.com/gw-tester) by Victor Morales
- The project was recently moved to new Github organization.
- Supports DANM, Multus or NSM
- Question: What kind of K8S deployment is assumed? IS it KUD/KRD? Answer: No. There is no assumption of specific K8S deployment.
- Question: What kind of K8S cluster is assumed? Is it just a single node? Answer: No assumption on number of nodes.
- Question: Is there support for a cluster running on OpenStack? Answer: Currently packaged in Vagrant. May work on OpenStack, but may require some extra work.
- Question: Are there any parameters that can be configured (Day2)? Is there any telemetry provided by the CNF? A: Not yet, but it could be added.
- Question: Which components could be scaled out using a replica set? Answer: eNodeB may be a candidate for that.
- Question: Can the CNF be used without a multiplexing CNI plugin (Using Calico or Flannel for example) Answer: In theory it might be possible with some minor modifications, but it was never tested.
- Next Step: Fernando Oliveira will work on better understanding parameterization and will work on creating an ETSI based package and VNFD.
- Walkthrough of the Core Network reference CNF (https://github.com/gw-tester) by Victor Morales
- Clock Changes: in US on March 14th, 2021; in Europe on March 28th, 2021; No change in India/China - Shall we change our CNF Task Force schedule as previously discussed?
- One hour before TSC - AI - Ranny to send a mail to the workgroup and get confirmation.
March 9th, 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?
- 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- REQ338 . https://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 1pm UTC
- Satoshi Fujii - proposal update from Fujitsu: k8s network design and config draft rev2.pptx
- Proposal deals with the challenge of migrating workloads between K8S clusters
- The approach is separating network design and CNI configuration
- According to the proposal the user will create virtual networks and ONAP will generate the CNI configuration and inject it into the Helm charts at deployment time.
- The proposal leverages EMCO (from OpenNESS). There were questions of the exact functionality provided by ONAP.
- AI for Satoshi Fujii - prepare a follow-up presentation about the use of EMCO and the value it brings.
- Update from Thinh Nguyenphuon ETSI event
- There are only 15 minutes for the entire presentation
- There is a need to submit an abstract by 3/22
- user-67d6f - ONAP CNF compliance badging
- VTP enhancements to support CNFs
- VTP needs to get the requirements for CNF packaging from ONAP
- user-67d6f - Are there ETSI SOL004 specifications? Fernando Oliveira - This is work in progress in Honolulu
- VTP test development is planned for the Istanbul release. Need to have the requirements table ready by the start of the release. Fernando Oliveira volunteered to work on that.
- Catherine Lefevre - Some of the VNF requirements might be applicable for CNFs
- The VNF requirements are at VNF TOSCA Requirements . Catherine Lefevre suggested Taskforce members take a look and provide feedback.
March 25th, 2021 at 1pm UTC
- Thinh Nguyenphu - Share an alternative Common CNF Packaging - We will wait for Thinh Nguyenphu to indicate his readiness to present
- Quick review of VNF TOSCA Requirements and VNF HEAT Requirements indicate that they are very VNF and OpenStack specific
- We need to look at the ONAP CNF artifact specifications (Helm charts, etc.), and try to derive the requirements.
- Marian Darula - AFAIK the draft for CNF artifacts has been presented by Fernando Oliveira , but not approved and accepted.
- Olivier Smith - There is no intention to rush the ONAP project to provide requirements if they are not ready yet.
April 1st, 2021 at 1pm UTC
- Thinh Nguyenphu 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
- Catherine Lefevre 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? Catherine Lefevre 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
- Lukasz Rajewski and Seshu Kumar Mudiganti will share the plans for Istanbul. May be in WIP state.
-
REQ-627Getting issue details...
STATUS
- no updates yet.
- No architectural changes expected.
- Marian Darula - Are Helm charts alone sufficient for modeling CNFs, or is there a need for external modeling. Lukasz Rajewski - Multi cluster is still a challenge.
- Byung-Woo Jun & Marian Darula - There is a need for an additional descriptor. The ETSI approach of a TOSCA descriptor on top of Helm could be a good approach. Lukasz Rajewski - The multi-cluster network connectivity is an example of a modeling aspect that needs to be handled outside the Helm charts. The Nokia proposal may hold the solution for this issue.
From user-67d6f : I have created the place holder for supporting the CNF badging from ONAP perspective here https://wiki.onap.org/display/DW/Anuket+Assured+-+ONAP+CNF+Compliance+Badge
In order to plan the same for next release, would like to get filled following items asap from CNF Task Force and Modelling team. Could you please help to identify the owners for the below items. Thank you
1. CNF Model Element Structure
This is related to our discussion on reaching consensus on packaging - it is still work in progress.
2. CNF badging requirements
We would like to get a better understanding of what the requirements should look like.
3. Sample CNF (ex: vFW) already supported in ONAP
Only existing CNF is the vFW, but it is not optimal as a "CNF reference". Other "Reference CNF" proposed by Samsung is not yet on-boarded to ONAP. Catherine Lefevre - the 5G-Super-Blueprint is working on on-boarding Magma (https://wiki.lfnetworking.org/display/LN/LFN+Demo%3A+5G+Super+Blueprint)
April 15th, 2021 at 1pm UTC
- All: 5G-Super-Blueprint - which CNF features we should utilize in this use case - impact on future requirements
- How to integrate with the Magma Orchestrator/controller
- Can ONAP treat the Magma Orchestrator as a CNF? We are assuming it is.
- The LTE version of Magma uses VNFs. The newly released 5G-SA version may be more CNF oriented.
- We need more information from the Magma side. Next ONAP-Enterprise call is planned for April 28th.
- Lukasz Rajewski presented the Honolulu CNF capabilities (
-
REQ-458Getting issue details...
STATUS
) - PLACEHOLDER - Lukasz Rajewski will upload the slides.
- CDS Day 1/2 operations
- K8S Plugin Day2
- Zu Qiang (Ericsson) - Q: How is CNF package distributed? A: Same as VNF. Q: How is configuration done - how is CDS triggered? Is it through SDNC? A:No. SO triggers the CDS directly. CDS and SDNC are both part of CCSDK.
- Lukasz Rajewski and Seshu Kumar Mudiganti will share the plans for Istanbul. May be in WIP state.
-
REQ-627Getting issue details...
STATUS
- SDC Changes - Helm validation. Alignment with ETSI CNF Package (when ready)
- A&AI - Bring information about the deployed resources from K8S and make them appear in A&AI. Requires discussion with the modeling subcommittee. Lukasz Rajewski will work with Andy Mayer on modeling changes for Istanbul.
- SO - Distribute Helm package using CNFs-adapter. CNF-adapter health check.
- K8S plugin - Switch to Helm 3.5
- New Use case - Possibly Free5GC, based on some work done by Orange.
- General comment - Plan is not finalized because there are still no confirmed resources for some of the planned functionality.
- Catherine Lefevre - recommends review of the Istanbul plan by the A&AI and SDC PTLs.
April 22nd, 2021 at 1pm UTC
- Invite CNF vendors to provide feedback on the CNF onboarding based on their experience with their CNFs.
- Kamel Idir - volunteered to provide feedback based on his experience
- Tried both types of packages - ETSI and ONAP
- Experience is with the Frankfurt release (Heat template wrapper)
- ONAP VNFD - Under TOSCA There is a namespace. If a vendor uses its own namespace it does not work out of the box. Expect to have a way to change the namespace supported by ONAP. There was a requirement for SDC to support changing the namespace. Workaround - Change the CNF package provided by the vendor to match the ONAP namespace.
- While designing a service using SDC, ran into an issue with the interfaces as defined by the vendors - use different types than the ones supported by ONAP.
- Christophe Closset - There were changes made in Honolulu - https://wiki.onap.org/download/attachments/100895762/SDCMultiModelSupport.pptx?version=1&modificationDate=1618834987000&api=v2&download=true
- Kamel Idir - Is there support for SOL007 design? Christophe Closset - It might be included in the recent changes (Honolulu). There is a way to indicate whether you are using ONAP or ETSI package.In the future it might be possible to translate between the two formats.
- SDC has a limitation on size of images in the Helm charts. SDC has a 8MB limitation. Kamel Idir indicates it is not sufficient for the CNFs he on-boarded. Workaround - Onboard images to Docker image registry and reference them. Some vendors provide embedded images which will require modification. Christophe Closset - The solution might not be having SDC handle the images. It is not designed to serve as image storage. Kamel Idir- Manipulating the package provided by a vendor to extract the images might jeopardize package integrity. Zu Qiang (Ericsson) - Extracting the images during on-boarding may not impact the integrity. Integrity validation happens before the extraction of the images. Flow is (1) Validate - signature validation (2) Extract (3) Distribute (no signature validation at this stage).
- Kamel Idir - volunteered to provide feedback based on his experience
April 29nd, 2021 at 1pm UTC
- Linux Foundation to take over Facebook's Magma | Light Reading
- Byung-Woo Jun - Initial Analysis of ONAP & Magma Architecture slide deck: ONAP-Magma-2021-04-29-v1.pptx
- Additional information can be found on the "ONAP for Enterprise" Task Force Wiki (specially on 4/28)
- Seshu Kumar Mudiganti - Magma may be treated as a 'resource orchestrator', and SO can have an adapter to control it like other resource controllers.Magma does not have LCM capabilities. Magma LCM requires some more research.
- Catherine Lefevre- SO should remain generic. We need to be consistent from an Architecture's perspective i.e. what's the scope of SO vs SDNC-C? When do we take the decision to create an adapter in SO and when SDNC is used?
- Deploying the Access GW requires running shell commands as root. This may be improved and better automated with ONAP.
- Opportunity for ONAP: Automate scaling of Magma GW; automate the "magma services" deploymentice
- Request from yan yan (CVC Committee) - Anuket Assured Re-Launch Release Plan to provide a go/no-go on their requirements / testing input to the badge launch.
- CVC received the following feedback about ONAP CNF compliance - Is it correct?
- H Release – ONAP CNF compliance requirements will be delivered by modeling subcommittee
- I Release – ONAP CNF compliance tests implementation will be delivered by VTP (under VNFSDK)
- Seshu Kumar Mudiganti - Updates or requests from the XGVela project
- Considering integration with 5G core slicing use case in ONAP.
- Observability - Looking at VES and Prometheus.
- In the process of finalizing the use case. More details to come soon.
- XGVela does no plan to introduce new requirements to ONAP, at least not for Istanbul.
- XGVela - CNF based
- Requirements are driven by Anuket community
May 6th, 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)
- SECCOM Container Logging specs - also applicable to CNF and therefore can it be used for CNF badging? (presented by Amy Zwarico)
- This is an update to the VNF security requirements
- Based on industry standards
- Applicable to CNFs and ONAP containers alike
- The requirements cover: Event types, log data, log management
- Follow-up with OVP PH2 /CNCF (https://github.com/cncf/cnf-wg/tree/main/cbpps), Anuket Communities to include some of these requirements as part of CNF Badging
- Agreed that May 13th CNF Call will be canceled
May 20th, 2021 at 1pm UTC
- Welcome Vishal Sharma (Spark New Zealand)
- Welcome Srini Rengasamy (Mavenir), Mike Sidler to the CNF TaskForce - Seshu Kumar Mudiganti - Building Network slice management that is ETSI compliant and using ONAP orchestration components.
- Share feedback regarding Thin's proposal presented on May 6th, 2021
- E-mail from Fred - [onap-discuss] Orchestration Scenarios/ETSI Alignment Meeting (May 10)
- MEC is not discussed as part of this CNF Task Force but we are interacting with MEC in the context of 5G Super Blueprint and ONAP E2E Network Slicing
- Review our ONAP DDF CNF proposals:
- 2021-06-DD - ONAP TSC Task Force: Cloud Native (Ask Us Anything) - Prepare some questions in advance to trigger the discussions
- 2021-06-DD - ONAP TSC Taskforce: Cloud Native (Demos)
- 2021-06-DD - ONAP TSC Taskforce: Cloud Native (Roadmap)
- A space for collaborating on the session material has been created here: June 2021 LFN Developer Forum Please upload your drafts to the appropriate section.
May 27th, 2021 at 1pm UTC
- Follow up regarding Thin's proposal presented on May 6th, 2021 + e-mail from Fred - [onap-discuss] Orchestration Scenarios/ETSI Alignment Meeting (May 10)
- Wiki page created: Application Service Descriptor (ASD) and packaging Proposals for CNFs
- Dedicated meetings will be setup and summary will be shared with the CNF Task Force?
- Suggestion to use the call organised on Monday at 8am EST but next week, SO meeting will be used
- Fernando Oliveira will update the bridge details on the CNF Descriptor Proposals wiki
- Moderator is requested
- Enhance previous ONAP Cloud Native Vision/Roadmap, highlighting Cloud Native Capabilities provided by ONAP also including our CNF journey (CNFO + CNF/ETSI Alignment)
- Latest "ONAP Modularity" advancement - possibility to "Pick & Choose" the components we need for a specific use case (OOM Enhancements)
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.)
Ranny Haiby , Byung-Woo Jun , Timo Perala , Seshu Kumar Mudiganti to discuss this request with Architecture, Requirement & MAC subcommittees
- Review our ONAP DDF CNF proposals:
- 2021-06-DD - ONAP TSC Task Force: Cloud Native (Ask Us Anything) - Prepare some questions in advance to trigger the discussions
- 2021-06-DD - ONAP TSC Taskforce: Cloud Native (Demos)
- 2021-06-DD - ONAP TSC Taskforce: Cloud Native (Roadmap)
- A space for collaborating on the session material has been created here: June 2021 LFN Developer Forum Please upload your drafts to the appropriate section.
June 3rd, 2021 at 1pm UTC
- Review our ONAP DDF CNF proposals - June 2021 LFN Developer Forum
- (specially "Ask Anything") – Please send any links to Ranny Haiby to consolidate our answers after the meeting - 2021-06-DD - ONAP TSC Task Force: Cloud Native (Ask Us Anything)
- Cloud Native Roadmap:
- Byung-Woo Jun , Fernando Oliveira presentation: deck - suggestion is that Seshu/Byung will start and then Fernando Oliveira, Byung-Woo Junwill grap 10 mins from the break
- Byung-Woo Junwill update the Agenda: 2021-06-DD - ONAP TSC Taskforce: Cloud Native (Roadmap)
- Lukasz Rajewski , Seshu Kumar Mudiganti
- Cloud Demos (Seshu Kumar Mudiganti, Lukasz Rajewski)
- ONES - Call For Proposals (CFP) | Linux Foundation Events - deadline: June 20th, 2021 - Catherine Lefevreto follow offline
June 17th, 2021 at 1pm UTC
- EMCO Update - Upcoming meeting on Wednesday June 23rd 6:30AM PDT
- ONE Summit - CFP Deadline is June 20th
- ONAP CNF orchestration Progress and roadmap - Catherine Lefevre 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 Byung-Woo Jun Catherine Lefevre
- Abstract submission - Thinh Nguyenphu - submit as a panel - circulate draft by email
- ONAP CNF orchestration Progress and roadmap - Catherine Lefevre Seshu Kumar Mudiganti Lukasz Rajewski Ranny Haiby Byung-Woo Jun
June 24th, 2021 at 1pm UTC
- ASD Updates (based on Monday meeting progress) - Good progress was made. Still working on modeling. There is a wiki page for collaboration - Application Service Descriptor (ASD) and packaging Proposals for CNF
- The ASD work going on in the "orchestration scenarios" workgroup, and reflected in the above mentioned wiki page, is merging both the "ETSI" and "Native" CNF orchestration paths in ONAP.
- Q: What will be the format of package that vendors will have to provide for their CNFs? Will it adhere to the SOL004 specification? A:ASD extends SOL004. The intention is to make the ASD extensions become part of SOL004.
- The interface between the VNFM and K8S should be tabled SOL018. Comment: SOL018 is not defined yet. Actually it is better to label it "K8S API". Agreed.
- Ranny Haiby - To be pragmatic, it is best to focus on existing interfaces (e.g. K8S API) and not wait for ETSI-NFV or the O-RAN alliance to define new abstraction layers. There is a need to finalize the CNF packaging as soon as possible so vendors can use it for their CNFs.
- Orchestration of Free5GC with Helm charts and CNFO (Ilhem Fajjari, Abderaouf Khichane,Lukasz Rajewski, Michal Chabiera - Orange) - 30 min
- Link to slides <to be uploaded by Lukasz Rajewski
- Q: What are the requirements for K8S - A: K8S 1.20 (for SCTP), Multus.
- Review ONAP Cloud Native Vision/Roadmap, highlighting Cloud Native Capabilities provided by ONAP also including our CNF journey (CNFO + CNF/ETSI Alignment)
- Are we OK to meet next week on July 1st, 2021?
Action Items (In Progress)
- (All) Feel free to provide feedback about ASD packaging (CNF Orchestration Functional Architecture)
- 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
- (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
- (Andy Mayer , Hui Deng ) Follow up regarding Modeling team about CVC request - Re: Request from CVC
- (Byung-Woo Jun: Bring the discussions to the ONAP Architecture Subcommittee about SO/SDNC role etc (see notes from 4/29)
- (Modeling/Requirements): Need to determine what ETSI CNF package solution we want to move forward (Fernando Oliveira, Byung-Woo Jun vs Thinh Nguyenphu)
- (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
- Kamel Idir - Will repeat onboarding with Honolulu (once he has the lab resources) and will report back
Action Items (Closed in 2021)
- (Thinh Nguyenphu) / 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 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
- (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
- Catherine LefevreFollow-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.
- Catherine Lefevre: 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