HVVES

Historically hvves is relying on hardcoded config parameters retrieved from the robot configmap.

This test could not work anymore with Kafka evolutions.

In fact the kafka credentials will be created at installation and available in a secret. As a consequence, they cannot be harcoded in the test.

Current processing

Future processing

The hvves test is launched as follows:

So the evolution of the use case could be done according to the following procedure:

1. add an ansible task to retrieve the secret and decode it to create 2 var dmaap_login and dmaap_pwd – need to know the secret name..
   https://gitlab.com/Orange-OpenSource/lfn/onap/xtesting-onap/-/blob/master/roles/xtesting-healthcheck/tasks/prepare.yaml
2. Improve the manifest file to give these variables to the test: https://gitlab.com/Orange-OpenSource/lfn/onap/xtesting-onap/-/blob/master/roles/xtesting-healthcheck/defaults/main.yaml

  - name: GLOBAL_DMAAP_KAFKA_JAAS_USERNAME

value: "{{ dmaap_login }}"

- name: GLOBAL_DMAAP_KAFKA_JAAS_PASSWORD

value: "{{ dmaap_pwd }}"

1. Cleanup the OOM config file (remove GLOBAL_DMAAP_KAFKA_JAAS_USERNAME and GLOBAL_DMAAP_KAFKA_JAAS_PASSWORD)

It should be transparent for the test...