...
- 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: CNF Descriptor Proposals
- Dedicated meetings 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
- 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 Enhance previous ONAP CNF Vision/Roadmap, highlighting Cloud Native Capabilities provided by ONAPONAP 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")
- ONES - Call For Proposals (CFP) | Linux Foundation Events - deadline: June 20th, 2021
- Review ONAP Cloud Native Vision/Roadmap, highlighting Cloud Native Capabilities provided by ONAP also including our CNF journey (CNFO + CNF/ETSI Alignment)
- EMCO
June 17th, 2021 at 1pm UTC
- EMCO
Action Items (In Progress)
...