Tenant Provisioning

• Administrator

Learn how to provision Genesys Pulse.

Related documentation:

• How Reporting works
• Suite-level guide
• All services
• Genesys Pulse Release Notes

RSS:

• For private edition

Prerequisites

Please complete Before you begin instructions.

Information you will need:

• Versions:
  • <image-version> = 9.0.100.10
  • <chart-versions>= 9.0.100+10
• K8S namespace <namespace> (e.g. 'pulse')
• Project Name <project-name> (e.g. 'pulse')
• Postgres credentials
  • <db-host>
  • <db-port>
  • <db-name>
  • <db-user>
  • <db-user-password>
  • <db-superuser>
  • <db-superuser-password>
  • <db-ssl-mode>
• Docker credentials
  • <docker-email>
  • <docker-password>
  • <docker-user>
• OpenShift credentials
  • <openshift-url>
  • <openshift-port>
  • <openshift-token>
• Redis credentials
  • <redis-host>
  • <redis-port>
  • <redis-password>
  • <redis-enable-ssl>
• Tenant service variables
  • <tenant-uuid>
  • <tenant-sid>
  • <tenant-name>

Fill appropriate placeholders in .shared_tenant_variables:

export PROJECT_NAME='<project-name>'
export NAMESPACE='<namespace>'
export CHART_VERSION='<chart-version>'
export DB_HOST='<db-host>'
export DB_PORT='<db-port>'
export DB_NAME_SHARED='<db-name>'
export DB_USER_SHARED='<db-user>'
export DB_PASSWORD_SHARED='<db-user-password>'
export DB_NAME_SUPERUSER='<db-superuser>'
export DB_PASSWORD_SUPERUSER='<db-superuser-password>'
export DB_SSL_MODE='<db-ssl-mode>'
export DOCKER_REGISTRY_SECRET_NAME='<docker-registry-secret-name>'
export DOCKER_REGISTRY='<docker-registry>'
export DOCKER_TAG='<image-version>'
export REDIS_ENABLE_SSL='<redis-enable-ssl>'
export REDIS_PASWORD='<redis-password>'
export REDIS_PORT='<redis-port>'
export REDIS_HOST='<redis-host>'
export TENANT_UUID='<tenant-uuid>'
export TENANT_DCU='2'
export TENANT_NAME='<tenant-name>'
export TENANT_SID='<tenant-sid>'
export PV_STORAGE_CLASS_RW_MANY='<rw-many-storage-class>'
export PV_STORAGE_CLASS_RW_ONCE='<rw-once-storage-class>'

Tenant provisioning

Content coming soon

Troubleshooting

Check init-tenant helm chart manifests

Run to output manifest into helm-template directory:

source .tenant_init_variables
 
envsubst < ./values-override-init-tenant.yaml | \
helm template \
     --version="${CHART_VERSION}" \
     --namespace="${NAMESPACE}" \
     --debug \
     --output-dir helm-template \
     "${CHART_NAME_TENANT_INIT}" pe-jfrog-stage/init-tenant \
     -f -

Check dcu helm chart manifests

Run to output manifest into helm-template directory:

source .tenant_init_variables
 
envsubst < ./values-override-dcu.yaml | \
helm template \
     --version="${CHART_VERSION}" \
     --namespace="${NAMESPACE}" \
     --debug \
     --output-dir helm-template \
     "pulse-dcu-${TENANT_SID}" pe-jfrog-stage/dcu \
     -f -

Check lds helm chart manifests

Run to output manifest into helm-template directory:

source .tenant_init_variables
 
envsubst < ./values-override-lds.yaml | \
helm template \
     --version="${CHART_VERSION}" \
     --namespace="${NAMESPACE}" \
     --debug \
     --output-dir helm-template \
     "pulse-lds-${TENANT_SID}" pe-jfrog-stage/lds \
     -f -

Check permissions helm chart manifests

Run to output manifest into helm-template directory:

source .tenant_init_variables
 
envsubst < ./values-override-permissions.yaml | \
helm template \
     --version="${CHART_VERSION}" \
     --namespace="${NAMESPACE}" \
     --debug \
     --output-dir helm-template \
     "pulse-permissions" pe-jfrog-stage/permissions \
     -f -

Do Not Publish

List any provisioning needed to deploy, run, or manage the service. For example:

• Designer: Create an Access Group specific to Designer Developer, Admin.
• Agent Setup: Create Agent Setup options to provide access to Administrator, Supervisor. or Ops.
• Genesys Info Mart: Update the CTL_CONFIG table in the GIM DB to control ETL and DB maintenance behavior.