STATUS: 

OOF (ONAP Optimization Framework):

1. High Level Component Definition and Architectural Relationships 

2. API definitions

OOF provides the following interfaces:

Note:   xxxI interface is a Component internal interface.  xxxxE interface is a component external interface

The current API documents can be found at:

• The provided UI interfaces are found at: CLAMP latest user guide

• CLAMP internal APIs can be found: clamp swagger pdf

OOF consumes the following Interfaces:

3. Component Description:

ONAP Optimization Framework (OOF) is an Umbrella project, with the primary goal of addressing the optimization needs of ONAP. OOF is a framework that supports creating and running a suite of Optimizing applications including: 
-Change Management Scheduling optimizer
-Homing/Placement optimizer
-PCI optimizer
-Route optimizer

OOF is targeted to be an optimization platform with the following goals: 
-Declarative, policy-driven approach to solving optimization problems
-Reusable components: data and policy adapters/libraries, execution environment
-Support General-Purpose as well as Custom optimizers
-Extensible to multiple optimization problems

Internally, OOF has the following components: 

• OSDF: Optimization Service Design Framework, which is a collection of APIs and libraries, along with a generic runtime optimizer
  • Status: Part of ONAP since Beijing Release.
• HAS: Homing and Allocation Service, which provides a policy based constraint driven selection optimizer
  • Status: Part of ONAP since Beijing Release.
• CMSO: Change Management Schedule Optimizer, providing schedule optimization
  • Status: Seed code up-streamed in R3
• FGPS: Fine Grained Placement Service
  • Status: Seed code up-streamed, POC in Frankfurt

4. known system limitations

5. Used Models

6. System Deployment Architecture

7. New Capabilities in this Release

-

8. References