...

Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

High level architecture diagram

At that stage within the ReleaseIn the reference configuration, the team Elastic Search pipeline is expected to provide more Architecture details describing how the functional modules are interacting.

TBD

Block and sequence diagrams showing relation within the project as well as relation with external components are expected.

Anyone reading this section should have a good understanding of all the interacting modules.

API Incoming Dependencies

List the API this release is expecting from other releases.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

...

API Outgoing Dependencies

API this release is delivering to other releases.

...

Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).configured to read files from persistent volumes. The impact on ONAP components is limited to logging provider configuration.  

Image Added

API Incoming Dependencies

None.

API Outgoing Dependencies

None.

Third Party Products Dependencies

...

Resources

Fill out the Resources Committed to the Release centralized page.

Release Milestone

...

The project team comply with the ONAP Charter.

Release Key Facts

Fill out and provide a link toward the centralized Release Artifacts.