Project Name:

  • Common frameworks (TBD)

Project description:

The purpose of this project is a merger between several different common frameworks that will be used in all ONAP component. In order to maintain alignment between the different components, it is vital to have common repositories that will be managed by the same group.

The project will include the following infrastructure:

  1. DmaaP (project promoted to stand-alone)
  2. Extensibility (project withdrawn)
  3. Logging (project promoted to stand-alone)
  4. Authorization and Authentication Framework (project promoted to stand-alone)

In time, more frameworks can be added to be shared between the different ONAP components

The repositories in this project will define the interfaces, guidelines and code – when applicable. Those frameworks should be used by all of ONAP projects. This project should be also mentored by the architecture sub-committee, where common architecture is required across ONAP


Key Project Facts

Project Name:

  • JIRA project name: Common Frameworks
  • JIRA project prefix: TBD

Repo name: TBD
Lifecycle State: Incubation
Primary Contact: Liron Shtraichman
Project Lead: 
mailing list tag
Committers (Name - Email - IRC): 

  • No labels

2 Comments

  1. Catherine Lefevre

    Concerning the logging aspects, EELF Framework is integrated to all the existing ONAP Modules.

    Some guidelines have also been posted

    https://wiki.onap.org/display/DW/Reference+Documents?preview=%2F1015849%2F3245577%2FONAP+application+logging+guidelines.pdf


    I believe this proposal should also be linked to the OOM project to cover any Operational common framework + Security Sub-committee (AAF)


    1. Carsten Lund

      Small note the logging guide on page 11 refer to the required HTTP header as "X-ECOMP-RequestID". This project should somehow change this requirement to "X-ONAP-RequestID" or some other solution.