ONAP Beijing Release Developer Forum

While Beijing release will be focused on making ONAP carrier grade. Ease of Operations would be presumably integral part of Beijing release strategy. We have thought about several operational aspects that are listed below and intend to present during sessions in Santa Clara. Please feel free to get in touch; happy to have short call if required to explain the rational. Look forward to have our proposal accepted. a. CBR (Configuration, Backup and Restore) Solution - This Solution Proposes to Build Vendor/Service agnostic config management platform which will enable the current ONAP Platform to support config versioning, backup and config restoration features by leveraging underlying Controller platform. This platform will also add support for config comparison which would allow to compare two different version of configuration and highlight the delta and keeps the track of changes, this would also help in debugging the configuration output in case the applied configuration is not giving expected output. b. Pre-certification Solution - This Solution Proposes to Build Vendor/Service agnostic Pre-test/Service Certification platform to enable Application/Network level validation with automated workflow, test automation engine, analytics and result dashboard for end user Device and Service Certification. This platform will automate various test for L1-L3 layer validation and L4-L7 validation and health check by leveraging controller framework before moving customer premises equipment into production or before being monitored via DCAE. c. VNF Config Flexibility - This Solution Proposes to Build Vendor Agnostic generic VBS (Velocity Builder System) based custom config engine to generate VNF/PNF Configurations which will be built on CBR platform. These Config templates will be triggered by CBR Platform based on VNF/PNF type (Input received via MSO or A&AI) via controller platform. The generic configuration will have initial/base config to establish network connectivity and global configuration for initializing VNF/PNF. The rationale behind this is to reduce Vendor dependency for VNF config templates by building vendor agnostic generic configuration engine. d. Hybrid Provisioning - This Solution Proposes to Build Vendor Agnostic generic VBS based custom configuration engine to support Legacy CPE Configurations (on Physical Network Function) which will be built on CBR platform. This Configuration templates will be triggered by CBR Platform based on CPE type (Input received via MSO or A&AI) via controller platform or direct interface thru CBR Platform. The solution is to enable hybrid support to current platform by enabling current platform to support provisioning of legacy devices. e. QoS Engine - The solution proposes to build QoS Engine to store the generic QoS policies for network function type created by SD&C during design time and provide a specific QoS policy to Network controller during execution based on customer requirements that it gets from MSO. QoS Engine will have algorithms to instantiate QoS policies for a network function based on generic QoS policies; it holds during design time. And, specific customer requirements that it gets from Network controller during execution time f. Inventory Navigator - This solution proposes to build an intuitive GUI on top of ONAP A&AI component that is easily pluggable into ONAP to provide unified view of physical and virtual objects and their relationships. This UI should provide end 2 end view of Customer to Cloud i.e. Customer à customer subscription à service Instance à VNF à VM à Physical Infra