Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

STATUS: 

OOF (ONAP Optimization Framework):

...

Drawio
bordertrue
diagramNameoof_r5
simpleViewerfalse
width
linksauto
tbstyletop
lboxtrue
diagramWidth936755
revision24

2. API definitions

OOF provides the following interfaces:

Interface NameInterface Definition Interface Capabilities
OOFE-1
  • Homing
  • Traffic Distribution
  • Network Slicing

It enables placement based on a wide variety of policy constraints including capacity, location, platform capabilities, and other service specific constraints. 

OOFE-2PCI/ANR OptimizationEnables PCI/ANR optimization API for SON.
OOFE-3Schedule Optimizationa policy driven workflow schedule optimizer for change management planning. This interface schedule workflows in time to maximize parallel change management activities, while respecting dependency between the workflows.
OOFE-4Route OptimizationProvides an interface for Router Optimization.
OOFE-5OOF Model AdministratorThis is for the OOF Model Administrator API.  This API is a way to dynamically change the optimization models that will be used to find solutions for various optimization problems.  This API will be used to Create, Update or Delete Models.
OOFE-6

Network Slicing

This interface enables slice selection recommendations.  

...

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: 

...

OOF doesn't directly create models, but indirectly consumes them via AAI, Policy and Multi Cloud. 

  • Service and Resource Info, from: AAI
  • Network Topology for CM: AAI
  • HPA Flavors/Capabilities/CapacityInfo, from : AAI
  • Policy Models (homing, PCI) from: Policy
  • Infrastructure Metrics Info (capacity), from: MultiCloud
  • Cloud agnostic Intent Info, from: MultiCloud
  • AZ level capacity Info, from: MultiCloud (for F-GPS)
  • PCI configuration data(not yet part of SDC model)
  • Slice/Subnet Profile and Slice/Subnet Instance models, from AAI

6. System Deployment Architecture

...