Gitiles
Code Review Sign In
osm.etsi.org / osm / tests / b70ccd6f95428c28aa3d756f07b91ee23a2637fd
commitb70ccd6f95428c28aa3d756f07b91ee23a2637fd[log] [tgz]
authoraktas <emin.aktas@ulakhaberlesme.com.tr>Wed May 26 10:32:32 2021 +0300
committergarciadav <david.garcia@canonical.com>Thu Jun 24 10:23:27 2021 +0200
tree8bf27635e68c695f17e748bdd7ddf8fb0e476970
parente0a9253220aa68a0e3064cdd7f2a933fb3733860 [diff]
Feature 10509 manual scaling for native K8s charm

This robot test created for this specific package
https://osm.etsi.org/gitlab/vnf-onboarding/osm-packages/-/merge_requests/154
Test case steps:
1 - Adds packages
2 - Adds K8s Cluster
3 - Creates NS Service
4 - Gets the scale count
5 - Scale-out the NS
6 - Checks scale count
7 - Scale-in the NS
8 - Check scale count
9 - Removes the NS, K8s cluster and packages
This commit includes Juju support

Change-Id: Iba7c59a65c9ae2607b23c7104e8178e20b502c60
Signed-off-by: aktas <emin.aktas@ulakhaberlesme.com.tr>
(cherry picked from commit f47542be165ebd69b91945041697181b4df63954)
6 files changed
tree: 8bf27635e68c695f17e748bdd7ddf8fb0e476970
  1. .gitignore
  2. CONTRIBUTING.md
  3. Dockerfile
  4. Jenkinsfile
  5. LICENSE
  6. README.md
  7. README_tst010_robot_cicd.md
  8. build-debpkg.sh
  9. charm.sh
  10. clouds-local.yaml
  11. conformance-tests/
  12. debian/
  13. devops-stages/
  14. docker/
  15. envconfig-local.rc
  16. requirements-dev.in
  17. requirements-dev.txt
  18. requirements.in
  19. requirements.txt
  20. robot-systest/
  21. sdncs-local.yaml
  22. setup.py
  23. tox.ini
README.md

OSM test automation project - osm/tests

This repository contains tools and configuration files for testing and automation needs of OSM projet

Prerequisites

  • Robot Framework
  • Packages: ssh ping yq git
  • Python3 packages: haikunator requests robotframework robotframework-seleniumlibrary robotframework-requests robotframework-jsonlibrary robotframework-sshlibrary
  • Clone osm-packages from gitlab
  • Environment config file for your infrastructure [envfile.rc]

Installing

This bash script can be used to setup your environment to execute the tests.

PACKAGES_FOLDER=osm-packages
add-apt-repository -y ppa:rmescandon/yq && apt update && apt install yq git iputils-ping ssh -y
pip install haikunator requests robotframework robotframework-seleniumlibrary robotframework-requests robotframework-jsonlibrary \
    robotframework-sshlibrary
snap install charm
# Download community packages
git clone https://osm.etsi.org/gitlab/vnf-onboarding/osm-packages.git ${PACKAGES_FOLDER}

envfile.rc

# VIM Setup
OS_USERNAME=<openstack_username>
OS_PASSWORD=<openstack_password>
OS_TENANT_NAME=<openstack_tenant_name>
OS_AUTH_URL=<openstack_authorization_url>
OS_TENANT_ID=<openstack_tenant_id>

# OSM Setup
OSM_HOSTNAME=<osm_ip_address>
VIM_TARGET=<osm_vim_name>
VIM_MGMT_NET=<osm_vim_mgmt_name>

# Clouds file datacenter
OS_CLOUD=<datacenter_in_clouds_file>
# SDNCs file
OS_SDNC=<SDN_controller_in_sdncs_file>

# 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

# Folder where Robot tests are stored
ROBOT_DEVOPS_FOLDER=robot-systest

# Folder to save alternative DUT environments (optional)
ENVIRONMENTS_FOLDER=environments

# Folder where all required packages are stored
PACKAGES_FOLDER=osm-packages

# Folder where test results should be exported
ROBOT_REPORT_FOLDER=results

Deployment

It is possible to run the tests directly from the repository or using a docker container with the tests

  1. Docker container creation:
docker build -f docker/Dockerfile -t osmtests .

Options:

  • --env-file: It is the environmental file where is described the OSM target and VIM
  • -o <osmclient_version> [OPTIONAL]: It is used to specify a particular osmclient version. Default: latest
  • -p <package_branch> [OPTIONAL]: OSM packages repository branch. Default: master
  • -t <testing_tags> [OPTIONAL]: Robot tests tags. [sanity, regression, particular_test]. Default: sanity

Volumes:

  • <path_to_reports> [OPTIONAL]: It is the absolute path to reports location in the host
  • <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
docker run --rm=true -t osmtests --env-file <env_file> \
       -v <path_to_reports>:/reports osmtests \
       -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>
  1. Running the tests manually:

The way of executing the tests is via the following command:

source envfile.rc
robot -d reports -i <testing_tags> testsuite/

Test tags

All tests in the testsuites have tags. Tags allow to run only a set of tests identified by a tag. Several tags can be specified when running robot in the following way:

robot -i <tag_01> -i <tag_02> testsuite/

The following tags exist for each testsuite:

  • A tag per testsuite using its mnemonic (e.g. basic_01)
  • Cluster tag for each of the statistically similar tests:
    • cluster_main: basic_01, basic_05, basic_08, basic_09, basic_15, basic_16, basic_17,hackfest_basic,hackfest_multivdu,hackfest_cloudinit,quotas_01`
    • cluster_ee_config: basic_06, basic_07, basic_11, basic_12, basic_13, basic_14, k8s_05, k8s_06
    • cluster_relations: basic_11, basic_13, basic_14
    • cluster_epa: epa_01, epa_02, epa_03, epa_04, epa_05
    • cluster_k8s: k8s_01, k8s_02, k8s_03, k8s_04, k8s_07, k8s_08, sa_08
    • cluster_k8s_charms: k8s_05, k8s_06
    • cluster_sa: sa_01, sa_02, sa_07
    • cluster_slices: slice_01, slice_02
  • daily: for all testsuites that will run in the daily job
  • regression: for all testsuites that should pass in the current stable branch
  • sanity: for all testsuites that should be passed by each commit in the stage3 to be successfully verified by Jenkins, currently basic_07, basic_11, k8s_03, k8s_04, sa_02

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.

Built With

Contributing

Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

License

This project is licensed under the Apache2 License - see the LICENSE.md file for details

Acknowledgments