Project Maturity Review for OOF
- krishna moorthy
- Swaminathan Seetharaman
- 1 Information for PTL
- 2 Review Submission Date: Jul 8, 2020
- 3 Project Description:
- 4 Project Landing Page:
- 5 Optimization Framework Project
- 6 Project Meeting Minutes:
- 7 OOF Meeting Minutes
- 8 Leadership Resources :
- 9 Project & Release History
- 10 Architecture Alignment:
- 11 Artifact Information:
- 12 Other Information:
Information for PTL
This template is to be filled out for any project wishing to move to the "Mature" phase of the ONAP project lifecycle.
Once completed, remove this info box and the send the link for this page to onap-tsc@lists.onap.org to initiate the maturity review.
Per the ONAP Technical Community Document, the metrics for maturity review are:
›Successful participation in releases: The project demonstrates stable output (code base, documents) within its history of releases in accordance with the release policy.
›Architecture has been reviewed by the Architecture Committee
›Project is active and contributes to ONAP: The project demonstrates a stable or increasing number of contributions across recent releases. Contributions are commits which got merged to a repository of an ONAP project or a related upstream project. Commits can for example be patches to update the requirements document of a project, code addition to an ONAP or upstream project repository, new test cases and so forth.
›Mature artifacts produced: The project demonstrates that the artifacts produced by the project are deployable (where applicable) and have been successfully deployed, configured and used by end users (typically, service providers).
Review Submission Date: Jul 8, 2020
Project Description:
The OOF provides a policy-driven and model-driven framework for creating optimization applications for a broad range of use cases.
It is being developed based on the following core principles:
Most optimization problems can be solved in a declarative manner using a high-level modeling language.
Recent advances in open source optimization platforms allow the solution process to be mostly solver-independent.
By leveraging the library of standard/global constraints, optimization models can be rapidly developed.
By developing a focused set of platform components, we can realize a policy-driven, declarative system that allows ONAP optimization applications be composed rapidly and managed easily
Policy and data adapters
Execution and management environment
Curated "knowledge base" and recipes to provide information on typical optimization examples and how to use the OOF
More importantly, by providing a way to support both "traditional" optimization applications and model-driven applications, we can provide a choice for users to adapt the platform based on their business needs and skills/expertise.
The highly modular architecture of OOF to cater to different kinds of optimization problem requirements of various use cases is depicted in the following figure.
The architectural updates done in Frankfurt release provides a lot of benefits from a platform capability perspective. This is described in the followed illustration. It enables easy extension of the platform to be able to support new use cases more easily.
Project Landing Page:
Optimization Framework Project
Project Meeting Minutes:
OOF Meeting Minutes
Leadership Resources :
Role | Name | Linux Foundation Login (LFID) | Email Address |
|---|---|---|---|
PTL | @krishna moorthy | krishnaa96 | |
Committers | @Shankaranarayanan Puzhavakath Narayanan | snarayanan | |
@Vikas Varma | vrvarma | ||
@Arthur Martella | amartell | ||
@dhebeha mj | dhebeha | ||
Sarat Puthenpura | sarat |
Project & Release History
How long the project has been an active: TSC approval date for OOF project is June 23, 2017. The project has been active since Beijing release and has participated in all releases through Frankfurt.
Release Participation: OOF project has been part of Release R2 through Release R6.
Engagement levels for past releases (up to 3):
Commits per Release: See table below
Contributors per Release: See table below
Companies per release: See table below
Release name and time frame | Commits | Authors | Companies |
118 | 18 | 7 | |
142 | 18 | 7 | |
219 | 12 | 6 | |
42 | 9 | 5 | |
184 | 21 | 9 |
Bitergia statistics for the last 2 years (since July 1, 2018):
Use Cases: The Key uses cases that OOF Project has contributed so far are:
5G OOF SON use case
5G E2E Network Slicing use case
CCVPN use case
Change Management (CM)
HPA
Homing and Placement use cases
Service/VNF instantiation (e.g., vCPE)
Multi-cloud
VNF Scale out
MDONS use case (from Guilin release)
Architecture Alignment:
Last Architecture review was done on Jan 7, 2020 as part of the Frankfurt release: OOF Frankfurt (R6) Architecture Review.
Artifact Information:
Artifact | Repo | Docs link | Line Coverage | Test suites | Description |
|---|---|---|---|---|---|
optf/osdf | https://docs.onap.org/projects/onap-optf-osdf/en/latest/index.html | ONAP Optimization Service Design Framework (OSDF) is a model- and policy-driven optimization framework that makes it easier to build, deploy, and manage optimization applications for different use cases. | |||
optf/has | https://docs.onap.org/projects/onap-optf-has/en/latest/index.html#master-index | OOF-HAS is a policy-driven placement optimizing service (or homing service) that allows ONAP to deploy services automatically across multiple sites and multiple clouds. | |||
optf/cmso | https://docs.onap.org/projects/onap-optf-cmso/en/latest/index.html#master-index | OOF-CMSO is an optimizing service that allows for the scheduling of VNF change management workflows to be executed at a time in the future. It enables a 3rd party client to provide SO workflow requests for multiple VNFs to be executed within a provided change window. |
To our knowledge, OOF has been deployed and used in AT&T production, and it is also used internally in companies such as Wipro.
Other Information:
CII badging score currently at 180%
More detailed architecture and developer guide can be found under:
For E2E Network Slicing use case, OOF plays an important role in the implementation of 3GPP TS 28.531 procedures for slice and slice sub-net orchestration.