Versions Compared

Key

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

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Page Status: Copied from

...

Guilin-R7 - Aug-24-2020
Component Status: Pending PTL

...

updates and ArchCom Review

Last Reviewed on:   

Certified by: krishna moorthy

OOF (ONAP Optimization Framework):

1. High Level Component Definition and Architectural Relationships 

Drawio
bordertrue
diagramNameoof_r7
simpleViewerfalse
width
linksauto
tbstyletop
lboxtrue
diagramWidth1225
revision1

2. API definitions

OOF provides the following interfaces:

...

Interface NamePurpose Reason For UseAPI Spec (Swagger)
SDNCE-1For PCI/ANR optimization, OOF Retrieves the Cellsite inventory details from the configdb API, which is hosted as part of the SDNC/R componenthttps://github.com/onap-oof-pci-poc/sdnc/blob/master/ConfigDB/swagger-json/swagger.json
AAIE-1OOF interfaces with AAI to retrieve the inventory

OOF consumes a wide variety of inventories from AAI. It can be found under the API section of AAI

https://docs.onap.org/projects/onap-aai-aai-common/en/latest/platform/offeredapis.html

MCE-5

OOF queries Multicloud for real-time available capacity information

https://docs.onap.org/projects/onap-multicloud-framework/en/latest/MultiCloud-APIv0-Specification.html
MUSICI-1OOF interfaces with MUSIC to persist service state.
SDCE-1OOF interfaces with SDC to retrieve slice template informationhttps://docs.onap.org/projects/onap-sdc/en/latest/offeredapis.html
DESE-1OOF interfaces with DES to retrieve the PM/KPI data of the cells for ML-based decision making.DES Swagger reference


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
  • Slice selection

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

Please find the known system limitations in the following links

5. Used Models

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 SDNC model)
  • Slice/Subnet Profile and Slice/Subnet Instance models, from AAI

6. System Deployment Architecture

Image RemovedImage Added

7. New Capabilities in this Release

  • Updates to E2E Network Slicing (refer OOFE-6)
  • Support for inter-domain route optimization (refer OOFE-4)
  • Introduction of offline trained ML model for the SON use case (refer OOFE-2 which has not changed, as well as DESE-1)
  • Integrate Generic Optimization Engine into OOF Helm charts (refer OOFE-5)

8. References

OOF Guilin (R7) Architecture Review

...