...
2. Functional enhancements for Frankfurt
The two key enhancement functional enhancements planned for Frankfurt are as follows:
...
- Moving to new Policy APIs as a part of Component Upgrades to new Policy Lifecycle API
...
- Support for E2E Network Slicing
...
- Internal re-architecture to allow streamlined onboarding of new optimization use cases.
- CCVPN route optimization
3. Architecture Diagram (Functional view)
Internal re-architecture (follow up on
| Jira | ||||||
|---|---|---|---|---|---|---|
|
Deployment architecture
4. New and modified interfaces
New interfaces
Modified interfaces
...
OOF provides the following interfaces:
| Interface Name | Interface Definition | Interface Capabilities |
|---|---|---|
| OOFE-6 | This interface enables slice selection recommendations. | |
| 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. |
Note: xxxI interface is a Component internal interface. xxxxE interface is a component external interface
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
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-4 | Route Optimization | Provides an interface for Router Optimization. |
Consumed interfaces
OOF consumes the following Interfaces:
| Interface Name | Purpose Reason For Use |
|---|---|
| SDCE-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. |
5. System limits
Please find the known system limitations in the following links
6. Involved use cases, architectural capabilities or functional requirements
...
In-addition, following SECCOM activities are being worked for Frankfurt
- Outstanding Address outstanding OJSI Jirasissues
- Java 11 Upgrade Upgrade for CMSO
- Python 2.x EOL migration support for OSDF, HAS, and FGPS
- Following additional TSC MUST have requirement "must-haves" will also be worked addressed in this release.(
)Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key OPTFRA-640 - Document current upgrade component strategy
- SECCOM Perform Software Composition Analysis - Vulnerability tables
- SECCOM Password removal from OOM HELM chartsNo DCAE impacts identified; will handle new charts contribution for MOD to align with Security needs.
SECCOM HTTPS communication vs. HTTP
| View file | ||||
|---|---|---|---|---|
|