Integration Dublin M3 Architecture Review

Brief Project Overview

The ONAP Integration is responsible for integration test of ONAP platform and all use cases, functional and non-functional requirements. 

New component capabilities for Dublin (i.e. the functional enhancements)

Two non-functional requirements are added to Integration, they are footprint optimization and CI/CD. Strictly speaking, these two new requirements shouldn't change any component capabilities. 

Footprint Optimization

• Refer to CIA project CIA- Container Images - Best Practices and Tools

• In Dublin release, the main focus of CIA project is to reduce docker image size so that ONAP deployment can be faster.  Here are some results of image size reduction Reduction effort between Casablanca and Dublin

CI/CD

The following efforts aim to improve ONAP code quality

• Work led by Orange team/LF to add pre-merge verification

• Daily Integration sanity test
  
  
  

New or modified interfaces

Integration does not provide any external APIs.

If they are modified, are they backwards compatible?

N/A

Interface naming (point to an example)

N/A

Reference to the interfaces.

N/A

What are the system limits?

N/A

Involved use cases, architectural capabilities or functional requirements.

Integration tests ONAP platform (including deployment, healthcheck, and S3P), and all use cases, functional/non-functional requirements listed on Dublin Release Requirements

Listing of new or impacted models used by the project (for information only).

Integration does not ingest the ONAP data model directly