Page Comparison

DRAFT

This template should be filled out for any project wishing to move to the "Mature" phase of the ONAP project lifecycle. It should be copied under the Project Maturity Reviews page & completed.  Once complete, the requestor should send the link to the onap-tsc mailing list to initiate the maturity review.  Further information: Project Reviews

FYI, 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).

Project Name:

Project Description:

• Provide high level description of the project 

Leadership Resources :

...

Role

...

First Name Last Name

...

Linux Foundation ID

...

Email Address

...

...

...

...

...

Project & Release History

The Policy Framework Project has been an active ONAP Project since Amsterdam and has participated in ALL releases through Frankfurt.

Use Case Participation

The key use cases that the Policy Framework project has contributed to are the following:

vFirewall

Scale Out

vCPE

CCVPN

5G OOF SON

BBS

Bitergia Statistics from the Last 2 Years

Image Removed

Architecture Alignment:

Last Architecture Review was for Frankfurt on 12/17/2019 with the results posted here: Policy R6 Frankfurt Architecture Review

Artifact Information:

• Describe & provide links to the artifacts (code, test cases, documentation) that the project has created.
• Describe the project's success & contributions in integration testing

The Policy Team supports the Integration vFirewall Use Case Testing every release and contributes changes to the Integration Robot Framework and Testsuite when updates are necessary.

Some example JIRA's for this:

integration/oparent support

Policy team members support the Integration oparent project

Team actively supports oparent checkstyle in all our repos. Our verify jobs will fail on any checkstyle violation.

Companies that run ONAP Policy internally

To our knowledge, the following companies have used ONAP Policy Framework internally: AT&T, Ericsson, Bell Canada, Tech Mahindra, Wipro.

Other Information:

ONAP Policy Framework has had topics and demo's at the ONAP Developer and LFN ONES conferences. Here is a list of recent demo's:

2019-06-12 LFN DDF Plugfest Kista, Sweden - won Best Demo award!

2019-09-23-25 ONS at Antwerp, Belgium Policy Framework Demonstration

2020-01-15 LF ONAP Prague DDF Policy Framework - Frankfurt Improvements

2020-04-23 LF Virtual Technical Event - Policy Framework Overview

Control Loop Sub Committee:

The Policy Framework Project has been active in the Control Loop subcommittee from its inception. Working very closely with CLAMP and DCAE to support the automation and enhancement of Control Loops in ONAP.

The project shares weekly meetings with the CLAMP Project.

Review Submission Date: TBD

Project Description

ONAP Command Line Interface (CLI) project provides ONAP commands required to perform ONAP operations from Linux or Web command console. It enables automation among ONAP operations like end-end service provisioning.

Project Landing Page:  Command Line Interface Project

Project Meeting Minutes: CLI meetings 

Leadership Resources https://github.com/onap/cli/blob/master/INFO.yaml

talasila

itohan

Project & Release History

• How long the project has been an active:  At launch
• Release Participation:  All Releases except Frankfurt
• Engagement levels for past releases (up to 3): 
  • Commits per Release:  see below
  • Contributors per Release: see below

  • Companies per release: see below

Statistics taken from Bitergia : Bitergia

Use Cases:  All use cases for various releases supported by A&AI can be seen here: Proposed Use Cases & Functional Requirements

Architecture Alignment

• ARC AAI Component Description - Frankfurt

Artifact Information

• AAI GUI Documentation
• AAI REST API Documentation
• AAI Design Documentation
• AAI Repositories
• AAI project team members, contributed, in all ONAP releases, in the successful completion of integration team testing (various use cases see Proposed Use Cases & Functional Requirements)
• AAI is used by AT&T and Amdocs in production (may be others, Tech Mahindra, Bell Canada, Huawei, China Mobile, Orange, Yoppworks have shown interest and contributed)

Other Information

• Code Coverage stats - https://sonarcloud.io/organizations/onap/projects?search=aai

  • aai-aai-common
    • Image Added
  • aai-babel
    • Image Added
  • aai-cacher
    • Image Added
  • aai-data-router
    • Image Added
  • aai-event-client
    • Image Added
  • aai-graphadmin
    • Image Added
  • aai-model-loader
    • Image Added
  • aai-resources
    • Image Added
  • aai-rest-client
    • Image Added
  • aai-router-core
    • Image Added
  • aai-schema-service
    • Image Added
  • aai-sparky-be
    • Image Added
  • aai-traversal
    • Image Added
  • aai-validation
    • Image Added
• AAI Bitergia (below was taken for last 90 days)

Image Added

Image AddedImage Added

• James Forsythpresented "Visualizing the schema" at one of the DDFs

• James Forsyth presented a report on community efforts for visualization at the Stockholm DDF

• As a collaboration of ONAP partners working toward a standards-based data model for ONAP, graphgraph schema visualization and papyrus was worked with the modeling subcommittee. 

• Many use case owners impact A&AI for their inventory/topology needs, we discuss all aspects of design/development on the AAI Weekly meetings
• We have made strides to comply with SECCOM & TSC requirements.
• https://wiki.onap.org/display/DW/Frankfurt+Release+Platform+Maturity