...
- Follow up regarding Thin's proposal presented on May 6th, 2021 + e-mail from Fred - [onap-discuss] Orchestration Scenarios/ETSI Alignment Meeting (May 10)
- Dedicated meeting will be setup and summary will be shared with the CNF Task Force? Fernando Oliveira will follow up with Kenny - Monday 8am EST
- Wiki page created: CNF Descriptor Proposals
- Enhance previous ONAP CNF Vision/Roadmap, highlighting Cloud Native Capabilities provided by ONAP
- 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)
- ONAP Components are containerized and are deployed on virtual, shared and elastic infrastructure.
- Built based on DevOps Toolchain (CI/CD, Gating, etc)
- Review our ONAP DDF CNF proposals
- ONES - Call For Proposals (CFP) | Linux Foundation Events - deadline: June 20th, 2021
...