Parallel Session Integration

Purpose

This template is to be used for the “Parallel Deep Dive Sessions to Align with architecture / Use cases” at the may ONAP developers event

Instructions.

The purpose of each section is to translate the use cases and functional architecture into specific identified needs for the components, and to identify potential projects to be proposed.  There are three parts to this exercise:

1. Identify needs based on the use case and architecture on this module, and potential dependencies on other modules or external artifacts.
2. Group these into projects.  Consider that coding, documentation, and testing is required.   Include an initial scope for the project.
3. If time, mapping the needs into the projects.

The need identification table has the following columns

-          Identified need: <slogan for the identified need>

-          Brief need description: <a few sentences describing the need>

-          Driver:<Related use case or architecture change, if any>

-          Dependencies:<identify dependencies on other modules or artifacts (e.g. other onap module, models, …)

-          Project: <If time, after the projects are identified, suggest in which project the need would best fit>

Time keeping suggestion:  The exercise time is 45 minutes.  A good practice would be to split into 20 minutes on need identification and 20 minutes on project proposals.

Exercise output.

ONAP Meeting Session name: integration

Need Identification:

Project proposals.

[repeat for each project.  Note: This is not a complete project proposal skeleton, only sufficient enough for this discussion]

Project 1:

Project ID: integration

Project Name:

-          Integration

Project Description

-          Provide integration tools and processes for CI/CD of source master and release branches

Scope:

-          Quickly identify scope, consider: documentation, APIs, models, testing, integration, functionality.

-          Note of any particular deliverables to highlight.

-          If anything is out of scope, not it down

Other:

-          Identify baseline code (if any)

Project 2:

Project Name:

-          Provide a brief project name.

Project Description

-          Provide a high level description of the project

Scope:

-          Quickly identify scope, consider: documentation, APIs, models, testing, integration, functionality.

-          Note of any particular deliverables to highlight.

-          If anything is out of scope, not it down

Other:

-          Identify baseline code (if any)

Meeting Notes:

#info helen says presents Slidedeck: System Integration and Testing

#info helen says integration team is a helper project.  Not have authority to be gatekeeper.

#info we use necus, docker, slack, bitgeria, swagger

#info helen says for open-o, created many test cases

#info helen says we use test suites robot framework

#info helen shares jenkins job flow

#info danials says this looks like they are complimentary to existing in ECOMP/ONAP with end-to-end testing

#info helen says that for each project, they will create their own CSIT test suite 

#question will there be docker level test?  looking at the docker logs

• We have the base infrastructure for it.  We do not scan the logs for strings.  The robot test framework will check against the signature of the api call.

#question will there be dynamic testing?

• We trigger unit level testing triggered automatically by Jenkins at build time

#question In the microsservice, the broker based testing is getting more popular.  

• consumer driven, broker driven

#question who builds the test?

• the developer will write the test and the integration team provides the framework, but it will be up to individual projects