Project Maturity Review for OOF (WIP)

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:

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 ideas:

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
1. Policy and data adapters
2. Execution and management environment
3. 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.

Project Landing Page:

Optimization Framework Project

Project Meeting Minutes:

OOF Meeting Minutes

Leadership Resources :

add lines if necessarry

Role	Name (must use @ macro )	Linux Foundation Login (LFID)	Email Address (if different from @ macro)
PTL	krishna moorthy	krishnaa96	krishna.moorthy6@wipro.com
Committers	Shankaranarayanan Puzhavakath Narayanan	snarayanan	snarayanan@research.att.com
	Vikas Varma	vrvarma	vv8305@att.com
	Arthur Martella	amartell	arthur.martella.1@att.com
	dhebeha mj	dhebeha	dhebeha.mj71@wipro.com
	sarat	sarat	sarat@research.att.com

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 timeframe	Commits	Authors
Dublin ( 12/1/2018 to 7/9/2019 )	219	12
El Alto ( 7/10/2019 to 10/24/2019 )	42	9
Frankfurt ( 10/25/2019 to 6/18/2020 )	183	20

Use Cases: The Key uses cases that OOF Project has contributed are as follows
- 5G SON use case
- 5G Network Slicing use case
- CCVPN use case

Architecture Alignment:

Last Architecture review was done on Jan 7, 2020 as part of the Frankfurt release

Artifact Information:

Code, Test cases and Documentation