Control Loop Objectives (Goals) - DRAFT

Dynamic creation of Control Loops

Control Loop designers should be able to build and deploy Control Loops out of the box when installing a release of the ONAP Platform. The steps should be clearly documented and easy to do. With an initial installation of an ONAP release, the Control Loop designer should be able to use existing pre-built and loaded ONAP DCAE analytics, Control Loop Policy Types, Policy PDP applications and CLAMP tools.

Enhance the configurability of the ONAP Platform to support customization for Control Loops as well as building more complex Control Loops

• Ability to integrate proprietary and/or build complex DCAE Enable the usage of proprietary analytics
• Design and integrate custom policy models
• Build and deploy new runtime policy applications Simplification of building and deploying Control Loopsto support custom/complex Control Loops
• Introduce new proprietary Actors for use during Control Loop Operational runtime

Ability to support multiple Control Loops for multiple domains

• Supports both Service and PNF Control Loops
  • Some examples of use cases: 5G, Slicing, Scale Up/Down
• Sharing of Control Loop components across multiple control loops
• Support for Control Loop Coordination services/resources

Testing Automation

of Control Loops

Edge deployment of ONAP Control Loop Components to support performance/resiliency/scalability requirements

Control Loop Monitoring

• Tools to support monitoring of Control Loops running on the platform
components
• Supports both Service and PNF Control Loops
• Easily build and integrate applications into the ONAP platform to support more complex Control Loops
  • eg. AI/ML/Policy Learning etc.
• Control Loop Monitoring

Control Loop Target Architecture - DRAFT

Control Loop Constraints