Gitiles
Code Review Sign In
gerrit.nordix.org / onap / policy / docker / 181e6c525c5e05bbb3e580fd0793b8332200659d
commit181e6c525c5e05bbb3e580fd0793b8332200659d[log] [tgz]
authorrameshiyer27 <ramesh.murugan.iyer@est.tech>Thu Mar 30 10:50:18 2023 +0100
committerrameshiyer27 <ramesh.murugan.iyer@est.tech>Thu Mar 30 14:23:07 2023 +0100
treec4f4f35f6ef3f92a96012abfed161a1e76463000
parent9acad08dfcc1e91b1640f550140e8fa625034ef2 [diff]
Disable K8s CSIT temporarily to fix timeout issue in Jenkins

The pods take longer time than usual in Jenkins vm which prevents robot
test cases getting executed. This will be fixed in the upcoming patch.
Fixing supporting docker images to be pulled from nexus

Issue-ID: POLICY-4541
Signed-off-by: zrrmmua <ramesh.murugan.iyer@est.tech>
Change-Id: If01b98bee51e36cb6104fa6eff006ad8194dc1b2
6 files changed
tree: c4f4f35f6ef3f92a96012abfed161a1e76463000
  1. compose/
  2. csit/
  3. helm/
  4. policy-db-migrator/
  5. policy-jdk/
  6. policy-jre/
  7. releases/
  8. utils/
  9. .env
  10. .gitignore
  11. .gitreview
  12. INFO.yaml
  13. LICENSE.txt
  14. pom.xml
  15. README.md
  16. version.properties
README.md

Copyright 2018-2019 AT&T Intellectual Property. All rights reserved. This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE Full license text at https://creativecommons.org/licenses/by/4.0/legalcode

This source repository contains legacy docker-compose configurations used for CSIT tests, and ONAP Heat instantiations.

Additionally, the policy-base/ and policy-common/ projects are used to generate the OS base for policy images.

Helm directory is added to include the helm chart for policy-models-simulators. To spin the kubernetes pod up:

  1. Execute the below commands: helm upgrade -i <release_name> policy-models-simulator

Running Policy CSIT in kubernetes: To run CSIT in kubernetes, docker/csit/run-k8s-csit.sh script can be invoked with the arguments {install} {project_name} When the project name is not supplied, the script only installs the policy helm charts and doesn't execute any robot tests. To teardown the kubernetes cluster, the same script can be invoked with the argument {uninstall}

Steps involved in running CSIT in kubernetes:

  1. The script verifies microk8s based kubernetes cluster is running in the system and deploys kubernetes if required.
  2. Deploys policy helm charts under the default namespace.
  3. Builds docker image of the robot framework and deploys robot framework helm chart in the default namespace.
  4. Invokes the respective robot test file for the project supplied by the user. The test execution results can be viewed from the logs of policy-csit-robot pod.