New Test Development

- api, pap (except consolidated HC), apex and acm runtime passing
on both docker and helm environment
- other simulators exposed on simulator service
- topics are checked on test with robot http support
- apex temp engine port exposed
- xacml readiness added

Issue-ID: POLICY-4125
Change-Id: I39ee8c38e70dd3a4ad26ba69d7c62e61a211469e
Signed-off-by: adheli.tavares <adheli.tavares@est.tech>
57 files changed
tree: 019fcc478bc3cda85d28ed960926a4729d0ff782
  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.