mrichomme | 9643b0c | 2020-11-14 22:36:57 +0100 | [diff] [blame] | 1 | .. This work is licensed under a |
| 2 | Creative Commons Attribution 4.0 International License. |
| 3 | .. _integration-missions: |
| 4 | |
| 5 | Integration missions |
| 6 | ==================== |
| 7 | |
| 8 | .. important:: |
| 9 | The Integration project is in charge of: |
| 10 | |
| 11 | - Providing testing environment |
| 12 | - Supporting the use case teams |
| 13 | - Managing ONAP CI/CD chains |
| 14 | - Developing tests |
| 15 | - Providing baseline images |
| 16 | - Validating the ONAP releases |
| 17 | |
| 18 | The different activities may be summarized as follows (proportions are indicative): |
| 19 | |
| 20 | .. figure:: files/integration-project.png |
| 21 | |
| 22 | |
| 23 | For each release, the integration team provides the following artifacts: |
| 24 | |
| 25 | - A daily CI chain corresponding to the release |
| 26 | - Staging labs to perform the pairwise testing (when not automated) and support |
| 27 | the use case teams |
| 28 | - Baseline JAVA and Python images |
| 29 | - oparent library to manage Java dependencies |
| 30 | - Test suites and tools to check the various ONAP components |
| 31 | - Use-case documentation and artifacts |
| 32 | - A testsuite docker included in the ONAP cluster to execute the robot based tests |
| 33 | - Configuration files (scripts, Heat templates, csa files) to help installing |
| 34 | and testing ONAP |
| 35 | - Wiki release follow-up tables (blocking points, docker versions,...) |
| 36 | |
mrichomme | 7eecfb3 | 2020-11-26 15:24:27 +0100 | [diff] [blame] | 37 | Please see the `integration wiki page <https://wiki.onap.org/display/DW/Integration+Project>`_ |
mrichomme | 9643b0c | 2020-11-14 22:36:57 +0100 | [diff] [blame] | 38 | for details. |