Versions Compared

Key

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

...

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

...

The key functional enhancements planned for Guilin are as follows:  

  • Support Enhancements for E2E Network Slicing use case
  • Support for MDONS use case
  • Support for ML based SON optimization 
  • CCVPN route optimization for Transport Slicing

3. Architecture Diagram (Functional view)

Image Removed

Internal re-architecture (follow up on 
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyONAPARC-406
)

Image Removed

Deployment architecture

OOF Architecture - Guilin (same as in Frankfurt)

Image Added


OSDF architecture in Guilin

Image Added

Deployment architecture (update for ML model)

Image AddedImage Removed

4. New and modified interfaces

...

interfaces

OOF provides the following interfaces:

...

Network Slicing

...

This interface enables slice selection recommendations.  

...

...

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

The current API documents can be found at:

Changed interfaces

Interface NameInterface Definition Interface Capabilities
OOFE-4Route Optimization

Provides an interface for Router Optimization.

Support for inter-domain route optimization.

OOFE-6

Network Slicing

This interface enables slice selection recommendations (NST, NSI, NSSI, Slice Profiles). It also provides support for Slice termination (NSI, NSSI) recommendations.

Unchanged interfaces

4Provides an interface for Router Optimization
Interface NameInterface Definition Interface Capabilities
OOFE-1
  • Homing
  • Traffic Distribution

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-Route Optimization5OOF 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.

Consumed interfaces

OOF consumes the following Interfaces:

Interface NamePurpose Reason For Use
SDCESDNCE-1For PCI/ANR optimization, OOF Retrieves the Cellsite inventory details from the configdb API, which is hosted as part of the SDNC/R component
AAIE-1OOF interfaces with AAI to retrieve the inventory
MCE-5

OOF queries Multicloud for real-time available capacity information

MUSICI-1OOF interfaces with MUSIC to persist service state.
SDCE-1OOF interfaces with SDC to retrieve slice template information
DESE-1OOF interfaces with DES to retrieve the KPI data of the cells for ML-based decision making.

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

5.  System limits

Please find the known system limitations in the following links

...

  • Usecases
    • Service/VNF instantiation
    • HPA
    • Change Management - Traffic Distribution
    • 5G / OOF SON 
    • 5G / Network Slicing
    • CCVPN
    • MDONS 

7. Platform Maturity Targets

Frankfurt Guilin Release Platform Maturity

In-addition, following SECCOM activities are being worked for FrankfurtGuilin.

  • Following
  • Address outstanding OJSI issues
  • Java 11 Upgrade for CMSO
  • Python 2.x EOL migration for OSDF, HAS, and FGPS
  • Following additional TSC "must-haves" will also be addressed in this release(
    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyOPTFRA-640791
    )
    • Document current upgrade component strategy
    • SECCOM Perform Software Composition Analysis - Vulnerability tables
    • SECCOM Password Hardcoded Certificate removal from OOM HELM charts
    • SECCOM HTTPS communication vs. HTTP

...

    • Remove root access to databases
    • Containers must crash properly
    • Containers must not have more than one process.