Eleveo Middleware Deployment Guide

Step 1: Clone the Repository

clone the repository using the following command.

git clone -b CX-4.8  https://efcx:RecRpsuH34yqp56YRFUb@gitlab.expertflow.com/cim/cim-solution.git CX-4.8

Change the directory.

cd CX-4.8/cim-solution/kubernetes

Step 2: Update the Configurations

Run the following commands:

helm show values expertflow/eleveo-middleware > helm-values/cx-middleware-custom-values.yaml  --version 4.8.0
helm show values expertflow/middleware-cronjob  > helm-values/cx-middleware-cronjob-custom-values.yaml --version 4.8.0

Open the helm-values/cx-middleware-custom-values.yaml file and update the variables:

Under global set the following value:

1. ingressRouter: The FQDN of the host VM.

Under extraEnvVars set the values as follows:

1. RECORDING_BACKEND: The mechanism for recording files. Leave at default ELEVEO.

2. LOG_LEVEL: The amount of detail in the logs. Default is INFO, and for more detailed logs the value should be DEBUG.

3. ELEVEO_ADMIN: The administrator username for Eleveo.

4. ELEVEO_PASSWORD: The administrator password for Eleveo.

5. ELEVEO_URL: The IP address of the Eleveo deployment in format http://IP-address.

6. ingressRouter: The FQDN of the host VM.

Open the helm-values/cx-middleware-cronjob-custom-values.yaml file and update the variables:

Under global set the following value:

1. ingressRouter: The FQDN of the host VM.

Under extraEnvVars set the values as follows:

1. RECORDING_BACKEND: The mechanism for recording files. Leave at default ELEVEO.

2. LOG_LEVEL: The amount of detail in the logs. Default is INFO, and for more detailed logs the value should be DEBUG.

3. CX_FQDN: The address of EF CX. https://EFCX-FQDN. This is set automatically.

4. MIDDLEWARE_API: The API link of the recording middle-ware that will provide recording files. Format: http://EFCX-FQDN/recording-middleware. This is set automatically.

5. RETRIEVAL_INTERVAL: The number of past days to push recording links for on startup.

6. ELEVEO_MAX_CALL_TIME: The maximum possible time in minutes a call is assumed to last.

7. ELEVEO_PASSWORD: The administrator password for Eleveo.

8. ELEVEO_PROCESSING_TIME: The time in minutes it takes for a call to appear in Eleveo after ending.

9. ELEVEO_TIMEZONE: The timezone of the Eleveo deployment e.g. Asia/Karachi

10. ELEVEO_URL: The IP address of the Eleveo deployment in format http://IP-address.

11. ELEVEO_USERNAME: The username of the Eleveo deployment.

12. TRUST_STORE_PASSWORD: Taken from the file CX-4.8/cim-solution/kubernetes/helm/Core/values.ymlunder the efConnectionVars section.

13. KEY_STORE_PASSWORD: Taken from the file CX-4.8/cim-solution/kubernetes/helm/Core/values.ymlunder the efConnectionVars section.

Once all the variables are updated, update the ingressRouter variable in global section with the FQDN.

Step 3: Deploy the Eleveo Middleware Helm Chart

Deploy the helm chart using the following command

helm upgrade --install --namespace expertflow  --set global.efCxReleaseName="ef-cx"  eleveo-middleware  --values helm-values/cx-middleware-custom-values.yaml expertflow/eleveo-middleware --version 4.8.0

Check the pods by running the following command

kubectl get pods -n expertflow | grep eleveo-middleware

Step 4: Deploy the Eleveo Middleware Cronjob Helm Chart

Deploy the Eleveo Middleware Cronjob helm chart using the following command

helm upgrade --install --namespace expertflow  --set global.efCxReleaseName="ef-cx"  middleware-cronjob --debug --values helm-values/cx-middleware-cronjob-custom-values.yaml   expertflow/middleware-cronjob  --version 4.8.0