...
| Track | Key Points | Challenges | Next Steps / AIs |
|---|---|---|---|
| LF Staff | Be respectful of everyone's time |
|
|
| Testing | |||
| CNTT | |||
| OPNFV | |||
| ONAP | Change Management support | Presented what is done in Frankfurt and what is planned in Guilin | Build and Replace worklfow schould allow to modufy existing instances of the VNFs on the fly. Lack of VNFC level reconfiguration is one if the missing features on SO/Controller side which is not suppoirted today. We want to solve this issue in the Guilin release PNF support by ONAP Change Management is the key challenge, planned to extend in Guilin Schema/VSP Update is a chalange in the Upgrade process in ONAP. We want to addres this issue and to enable update of the schema with adequate modification of the existing instnces of services - for PNFs, VNFs and CNFs Integration with CDS and K8s workloads as one of the key drivers for improvements of change management porocess in ONAP as K8s provides scaling, upgrades and traffic distribution capabilities by itself. For Frankfurt integration with CDS for CNFs creation is introduces. IN further releases K8s scaling and upgrade capabilities should be introduced. |
| Transport slicing support by ONAP | One possible implementation is presented by Huawei IETF work to define it has started, but it is draft only Work which has been done is presented | Get it as a requirement for Guilin Release and then get several ONAP implementation proposals and decide | |
| Network slicing (core network) ongoing support by ONAP | CSMF and NSMF part of ONAP. External NSSMF to be used. Demo for Frankfurt:
| Challenges on whether this is the only possible implementation or there may be more Alignment on API with 3GPP and ORAN A1 Discussion on communication-service-profile introduced in ONAP Warning on templates that are deprecated within 3GPP Impacts
| |
| SECCOM: Password removal | All passwords should be stored only in Kubernetes secrets, users should be allowed to provide their own secrets for the deployment and allow to generate passwords at the deployment time. | Further exchanges with ONAP community on best practice approval and implementation - sessions at the PTLs and TSCs calls. | |
| SECCOM: Ingress controller | Ingress Controller introduced for Frankfurt as an option deployment Effort on passing knowledge to ONAP teams on ingress controller and service mesh | Sessions at the PTLs calls. | |
| ONAP SECCOM ISTIO opportunity for common continuation discussion | Coexistance of AAF and Service Mesh in a long term security solution | AAF and ISTIO to be treated as two separate tracks | |
| Use Case Cross-Carrier 5G | Get the Community Aligned on Slicing - AP for Architecture/Requirements subcommittee + Magnus (ONAP TCC) What are the "baby steps" to build a "Slicing" roadmap Promote ONAP through #1 use cases that does not require changes in ONAP; #2 POC so Innovation can continue while focus on ONAP Core. |
...