Gitiles
Code Review Sign In
gerrit.nordix.org / onap / policy / docker / 21c3a2bfe23cbcf007def49e51191c40b98fa978
commit21c3a2bfe23cbcf007def49e51191c40b98fa978[log] [tgz]
authoradheli.tavares <adheli.tavares@est.tech>Thu Oct 31 16:01:59 2024 +0000
committeradheli.tavares <adheli.tavares@est.tech>Wed Nov 13 13:50:32 2024 +0000
tree4a493e6438cc7831cb692b68dd78ecb0c664b7c4
parent79ccac3162d05b4797450836c669e81465d3fa2d [diff]
Fix issues with grafana dashboards after multiple micrometer
and spring actuator uplifts.

- changed the metrics that have been renamed automatically
- changed the irate functions range to the same used on each
dashboard instead of fixed
- apex_healthcheck function wasn't being called when running
csit script because it was declared after usage

Issue-ID: POLICY-5155
Change-Id: I993f022937f6e2041a6c50dc5037c559da087849
Signed-off-by: adheli.tavares <adheli.tavares@est.tech>
15 files changed
tree: 4a493e6438cc7831cb692b68dd78ecb0c664b7c4
  1. compose/
  2. csit/
  3. helm/
  4. policy-db-migrator/
  5. policy-jdk/
  6. policy-jre/
  7. policy-regression-tests/
  8. releases/
  9. utils/
  10. .env
  11. .gitignore
  12. .gitreview
  13. INFO.yaml
  14. LICENSE.txt
  15. pom.xml
  16. README.md
  17. 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.

Running Policy CSIT in docker: To run CSIT in docker, docker/csit/run-project-csit.sh script can be invoked with the argument {project_name}.

Running Policy Regression Tests: ACM regression tests can be invoked using the script docker/csit/run-acm-regression.sh with the arguments {ACM-R release name} {participant release name} For example, if ACM-R and participants needs to be tested for backward compatbility between montreal and london versions, the script can be invoked with the command "./run-acm-regression.sh montreal london" This will deploy ACM-R and other policy components in montreal version and the participants in london version before invoking the test suite. The script can also be invoked without any arguments to deploy all the components in the default version of the repo.