Feature 10908: Update charm in running VNF instance

[osm/tests.git] / README.md

diff --git a/README.md b/README.md
index 1d7d5dc..0bb2493 100644 (file)
--- a/README.md
+++ b/README.md
@@ -64,9 +64,6 @@ OS_SDNC=<SDN_controller_in_sdncs_file>
 # K8S config file
 K8S_CREDENTIALS=<path_to_kubeconfig>
 
 # K8S config file
 K8S_CREDENTIALS=<path_to_kubeconfig>
 

-# Juju data file
-JUJU_DATA=<path_to_jujudata>
-

 # The following set of environment variables will be used in host
 # of the robot framework. Not needed for docker execution
 
 # The following set of environment variables will be used in host
 # of the robot framework. Not needed for docker execution
 


@@ -106,7 +103,6 @@ Volumes:
 * <path_to_clouds.yaml> [OPTIONAL]: It is the absolute path to the clouds.yaml file in the host
 * <path_to_sdncs.yaml> [OPTIONAL]: It is the absolute path to the sdncs.yaml file in the host
 * <path_to_kubeconfig> [OPTIONAL]: It is the kubeconfig file to be used for k8s clusters
 * <path_to_clouds.yaml> [OPTIONAL]: It is the absolute path to the clouds.yaml file in the host
 * <path_to_sdncs.yaml> [OPTIONAL]: It is the absolute path to the sdncs.yaml file in the host
 * <path_to_kubeconfig> [OPTIONAL]: It is the kubeconfig file to be used for k8s clusters

-* <path_to_jujudata> [OPTIONAL]: It is the jujudata file to be used for juju cli

 
 ```bash
 docker run --rm=true -t osmtests --env-file <env_file> \
 
 ```bash
 docker run --rm=true -t osmtests --env-file <env_file> \


@@ -114,7 +110,6 @@ docker run --rm=true -t osmtests --env-file <env_file> \
        -v <path_to_clouds.yaml>:/robot-systest/clouds.yaml \
        -v <path_to_sdncs.yaml>:/robot-systest/sdncs.yaml \
        -v <path_to_kubeconfig>:/root/.kube/config \
        -v <path_to_clouds.yaml>:/robot-systest/clouds.yaml \
        -v <path_to_sdncs.yaml>:/robot-systest/sdncs.yaml \
        -v <path_to_kubeconfig>:/root/.kube/config \

-       -v <path_to_jujudata>:/root/.local/share/juju \

        -o <osmclient_version> \
        -p <package_branch> \
        -t <testing_tags>
        -o <osmclient_version> \
        -p <package_branch> \
        -t <testing_tags>


@@ -164,6 +159,19 @@ In addition, the tag "cleanup" exists in those tests that perform
 any deletion. In that way, it can be invoked to retry the deletion if
 the tests were forcefully stopped.
 
 any deletion. In that way, it can be invoked to retry the deletion if
 the tests were forcefully stopped.
 

+- For helping in the migration tests and other scenarios in which you don't want
+to destroy the deployments immediately, the following tags are used:
+  - prepare: for the tests that are used to deploy the network
+  services under test
+  - verify: for the tests that perform the actual testing, or changes for
+  additional verifications (e.g. scaling).
+  - cleanup: already described above.
+
+  So, for instance, you could first deploy a number of network services executing
+  the tests with "prepare" tag, migrate to another OSM version, and then
+  check the behavior executing with the "verify" tag. Finally, use the "cleanup"
+  tag. 
+

 ## Built With
 
 * [Python](www.python.org/) - The language used
 ## Built With
 
 * [Python](www.python.org/) - The language used