...
| Track | Key Points | Challenges | Next Steps / AIs |
|---|---|---|---|
| Testing | |||
| CNTT | |||
| OPNFV | |||
| ONAP | Change Management support Transport slicing support by ONAP Network slicing (core network) ongoing support by ONAP SECCOM: Password removal SECCOM: Ingress controller | Presented what is done in Frankfurt and what is planned in Guilin 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 Effort on passing knowledge to ONAP teams on ingress controller and service mesh | 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. Get it as a requirement for Guilin Release and then get several ONAP implementation proposals and decide Challenges on whether this is the only possible implementation or there may be more |
...