1. Project Overview
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
2. Functional enhancements for Guilin
The key functional enhancements planned for Guilin are as follows:
- 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)
OOF Architecture - Guilin (same as in Frankfurt)
OSDF architecture in Guilin
Deployment architecture (update for ML model)
4. New and modified interfaces
OOF provides the following interfaces:
The current API documents can be found at:
The OOF user guide can be found at: OOF latest user guide
- OOF internal APIs can be found: OOF API specification
Changed interfaces
| Interface Name | Interface Definition | Interface Capabilities |
|---|---|---|
| OOFE-4 | Route Optimization | Provides an interface for Router Optimization. Support for inter-domain route optimization. |
| OOFE-6 | This interface enables slice selection recommendations (NST, NSI, NSSI, Slice Profiles). It also provides support for Slice termination (NSI, NSSI) recommendations. |
Unchanged interfaces
| Interface Name | Interface Definition | Interface Capabilities |
|---|---|---|
| OOFE-1 |
| It enables placement based on a wide variety of policy constraints including capacity, location, platform capabilities, and other service-specific constraints. |
| OOFE-2 | PCI/ANR Optimization | Enables PCI/ANR optimization API for SON. |
| OOFE-3 | Schedule Optimization | a 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-5 | OOF Model Administrator | This 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 Name | Purpose Reason For Use |
|---|---|
| SDNCE-1 | For PCI/ANR optimization, OOF Retrieves the Cellsite inventory details from the configdb API, which is hosted as part of the SDNC/R component |
| AAIE-1 | OOF interfaces with AAI to retrieve the inventory |
| MCE-5 | OOF queries Multicloud for real-time available capacity information |
| MUSICI-1 | OOF interfaces with MUSIC to persist service state. |
| SDCE-1 | OOF interfaces with SDC to retrieve slice template information |
| DESE-1 | OOF 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
6. Involved use cases, architectural capabilities or functional requirements
- Usecases
- Service/VNF instantiation
- HPA
- Change Management - Traffic Distribution
- 5G / OOF SON
- 5G / Network Slicing
- CCVPN
- MDONS
7. Platform Maturity Targets
Guilin Release Platform Maturity
In-addition, following activities are being worked for Guilin.
- Following TSC "must-haves" will also be addressed in this release(
OPTFRA-791
-
Getting issue details...
STATUS
)
- Hardcoded Certificate removal from OOM HELM charts
- Remove root access to databases
- Containers must crash properly
- Containers must not have more than one process.
1 Comment
Xin Miao
krishna moorthy
In F release + , after undeploying component OOF from ONAP cluster, which DB should we remove from /dockerfile-nfs/dev/ to clean it up?
Is this documented anywhere in ONAP wiki? It used to be grouped very well under /dockerfile-nfs/dev-<component name>. Now it is painful for user to clean up the DB files for cleaning up per component purpose. Thanks ahead of time for your tips.