Eleveo Middleware Deployment Guide

Step 1: Clone the Repository

clone the repository using the following command.

CODE

git clone -b <cim-solution-branch-tag>  https://efcx:RecRpsuH34yqp56YRFUb@gitlab.expertflow.com/cim/cim-solution.git CX-<cx-version-tag>

Change the directory.

CODE

cd CX-<cx-version-tag>/cim-solution/kubernetes

Step 2: Update the Configurations

Open the helm/eleveo-middleware/values.yaml file and update the variables in extraEnvVars

CODE

vi helm/eleveo-middleware/values.yaml

Change the values as follows:

RECORDING_BACKEND: The mechanism for recording files. Leave at default ELEVEO.
LOG_LEVEL: The amount of detail in the logs. Default is INFO, and for more detailed logs the value should be DEBUG.
ELEVEO_ADMIN: The administrator username for Eleveo.
ELEVEO_PASSWORD: The administrator password for Eleveo.
ELEVEO_URL: The IP address of the Eleveo deployment in format http://IP-address.
ingressRouter: The FQDN of the host VM.

Open the helm/Middleware-cronjob/values.yaml file and update the variables in extraEnvVars

CODE

vi helm/Middleware-cronjob/values.yaml

Change the values as follows:

RECORDING_BACKEND: The mechanism for recording files. Leave at default ELEVEO.
LOG_LEVEL: The amount of detail in the logs. Default is INFO, and for more detailed logs the value should be DEBUG.
CX_FQDN: The address of EF CX. https://EFCX-FQDN. This is set automatically.
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.
RETRIEVAL_INTERVAL: The number of past days to push recording links for on startup.
ELEVEO_MAX_CALL_TIME: The maximum possible time in minutes a call is assumed to last.
ELEVEO_PASSWORD: The administrator password for Eleveo.
ELEVEO_PROCESSING_TIME: The time in minutes it takes for a call to appear in Eleveo after ending.
ELEVEO_TIMEZONE: The timezone of the Eleveo deployment e.g. Asia/Karachi
ELEVEO_URL: The IP address of the Eleveo deployment in format http://IP-address.
ELEVEO_USERNAME: The username of the Eleveo deployment.
TRUST_STORE_PASSWORD: Taken from the file CX-<cx-version-tag>/cim-solution/kubernetes/helm/Core/values.ymlunder the efConnectionVars section.
KEY_STORE_PASSWORD: Taken from the file CX-<cx-version-tag>/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

CODE

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

Check the pods by running the following command

CODE

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

CODE

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