Move integration xtesting Dockerfile to ONAP

All the Dockerfiles and xtesting configurations were hosted in gitlab.com [1]
The goal of this patch is to host these assets in ONAP
A jenkins jjb shall be created to generated the docker and push them on the nexus
(today the built-in registry of ONAP was used)

These xtesting dockers are referencing integration categories [2] and integration
use cases [3]
These xtesting dockers shall also simplify the way to integrate new use cases in any
CI chain (jenkins or gitlab-ci based)

[1]: https://gitlab.com/Orange-OpenSource/lfn/onap/integration/xtesting
[2]: https://wiki.onap.org/pages/viewpage.action?pageId=71835330
[3]: http://testresults.opnfv.org/onap/api/v1/projects/integration/cases

Issue-ID: INT-1366

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

1 files changed, 26 insertions, 0 deletions

diff --git a/smoke-usecases-pythonsdk/README.md b/smoke-usecases-pythonsdk/README.md
new file mode 100644
index 0000000..7f9e0b7
--- /dev/null
+++ b/smoke-usecases-pythonsdk/README.md
@@ -0,0 +1,26 @@
+# Smoke use cases
+
+## Goal
+
+The goal of this docker is to run End to End use cases on ONAP in order to
+check the solution. The testcases defined in this docker MUST be PASS to
+validate the release.
+The test cases can be run using Robot framework or onap-test (ONAP python SDK).
+Bash, python and unit test drivers also exist. Additionnal drivers can be added
+but the Dockerfile must be adapted accordingly.
+
+The tests are:
+
+* basic_vm: it onboard/distribute/deploy a single Ubuntu VM in ONAP using
+  VNF-API. The components used are SDC, SO, AA&I, SDNC.
+* freeradius_nbi: based on basic_vm, the instantiation part is done through the
+  ONAP external API (NBI) module.
+* clearwater_ims: it consists in a full deployment of an clearwater vIMS in ONAP.
+
+## Usage
+
+### Configuration
+
+### Command
+
+### Output