Gitiles
Code Review Sign In
osm.etsi.org / osm / tests / 9fc2b84c815dbadf688a28b9ae0ca710ca71a9cd
commit9fc2b84c815dbadf688a28b9ae0ca710ca71a9cd[log] [tgz]
authorbeierlm <mark.beierl@canonical.com>Fri Jun 26 14:57:09 2020 -0400
committerbeierlm <mark.beierl@canonical.com>Fri Aug 21 13:22:39 2020 -0400
treecae3a2785ed7e5ff3429e1109069f82188175d4c
parentfce0e1a450c036ad38d07e1eebb001cf8e2a3fe3 [diff]
Merge v8.0 into master

Test contributions from master
Fix permission for devops-stages files (+x)
Adding the repository to CI/CD pipeline
Adding VIM to OSM option
Adding BRANCH_NAME variable for release tests
Adding prometheus_host env variable for ci/cd

git cherry-pick -n e1a9c5709cce246d2cca273be7d8f61b8404efea^..72556ca8d5a07199c182a586688bbebe8cf1cfad

Author: Felipe Vicens <felipe.vicens@atos.net>
Signed-off-by: beierlm <mark.beierl@canonical.com>

Adds test EPA-01 for SR-IOV

Signed-off-by: garciaale <agarcia@whitestack.com>

Retry vim-create

Sometimes it appears that the vim-create command gets issued
before LCM is properly ready, so as a workaround, this tries
a number of times to create the VIM before giving up.

Signed-off-by: beierlm <mark.beierl@canonical.com>

Fixing Logic

Breaks out of the loop once the vim is enabled

Signed-off-by: Mark Beierl <mark.beierl@canonical.com>

Added test [K8s-04] OpenLDAP

Signed-off-by: ramonsalguer <javier.ramon@telefonica.com>

==================================================================

Signed-off-by: Mark Beierl <mark.beierl@canonical.com>
Change-Id: Id436df42b735aa856e946c5c693f291bd0ba2d44
1 file changed
tree: cae3a2785ed7e5ff3429e1109069f82188175d4c
  1. .gitignore
  2. CONTRIBUTING.md
  3. Dockerfile
  4. Jenkinsfile
  5. LICENSE
  6. README.md
  7. build-debpkg.sh
  8. charm.sh
  9. clouds-local.yaml
  10. debian/
  11. devops-stages/
  12. docker/
  13. envconfig-local.rc
  14. robot-systest/
  15. sdncs-local.yaml
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>

   # 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
   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 \
       -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/

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