Refactor Integration official documentation

Issue-ID: INT-1736

Signed-off-by: mrichomme <morgan.richomme@orange.com>
Change-Id: Ia7b6425358eb9b07e293881dabd5345697af1c39

1 files changed, 38 insertions, 0 deletions

diff --git a/docs/integration-missions.rst b/docs/integration-missions.rst
new file mode 100644
index 000000000..331c92109
--- /dev/null
+++ b/docs/integration-missions.rst
@@ -0,0 +1,38 @@
+.. This work is licensed under a
+   Creative Commons Attribution 4.0 International License.
+.. _integration-missions:
+
+Integration missions
+====================
+
+.. important::
+   The Integration project is in charge of:
+
+   - Providing testing environment
+   - Supporting the use case teams
+   - Managing ONAP CI/CD chains
+   - Developing tests
+   - Providing baseline images
+   - Validating the ONAP releases
+
+The different activities may be summarized as follows (proportions are indicative):
+
+.. figure:: files/integration-project.png
+
+
+For each release, the integration team provides the following artifacts:
+
+- A daily CI chain corresponding to the release
+- Staging labs to perform the pairwise testing (when not automated) and support
+  the use case teams
+- Baseline JAVA and Python images
+- oparent library to manage Java dependencies
+- Test suites and tools to check the various ONAP components
+- Use-case documentation and artifacts
+- A testsuite docker included in the ONAP cluster to execute the robot based tests
+- Configuration files (scripts, Heat templates, csa files) to help installing
+  and testing ONAP
+- Wiki release follow-up tables (blocking points, docker versions,...)
+
+Please see the `integration wiki page <https://wiki.onap.org/display/DW/Integration+Project>`__
+for details.