Difference between revisions of "PrivateEdition/Current/TenantPEGuide/Planning"

From Genesys Documentation
Jump to: navigation, search
m (Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX")
 
(2 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
|DisplayName=Before you begin
 
|DisplayName=Before you begin
 
|Context=Find out what to do before deploying the Tenant Service.
 
|Context=Find out what to do before deploying the Tenant Service.
 +
|ServiceId=4d384b74-f61d-48f7-bace-30048213bf99
 +
|IncludedServiceId=5a34ac72-3fae-4368-afd8-5b899e1c52ba
 
|LimitationsStatus=No
 
|LimitationsStatus=No
 
|HelmStatus=No
 
|HelmStatus=No
 
|HelmText=For information about how to download the Helm charts, see {{SuiteLevelLink|helmchart}}.
 
|HelmText=For information about how to download the Helm charts, see {{SuiteLevelLink|helmchart}}.
 +
 +
See {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=VoiceMicroservicesHelm|display text=Helm charts and containers for Voice Microservices}} for the Helm chart version you must download for your release.
  
 
===Containers===
 
===Containers===
Line 26: Line 30:
 
}}{{SectionThirdPartyItem
 
}}{{SectionThirdPartyItem
 
|ThirdPartyItem=2afd763e-337c-47eb-8428-3bafcc89dbca
 
|ThirdPartyItem=2afd763e-337c-47eb-8428-3bafcc89dbca
 +
|Notes=Starting with version 100.0.100.0041, Tenant Service supports Consul 1.10.
 
}}{{SectionThirdPartyItem
 
}}{{SectionThirdPartyItem
 
|ThirdPartyItem=3aee73ed-68e0-4c70-8693-2421c68b86cd
 
|ThirdPartyItem=3aee73ed-68e0-4c70-8693-2421c68b86cd
 
}}{{SectionThirdPartyItem
 
}}{{SectionThirdPartyItem
 
|ThirdPartyItem=1a407778-58fe-4acd-8ca7-5af8eac31283
 
|ThirdPartyItem=1a407778-58fe-4acd-8ca7-5af8eac31283
−
|Notes='''NOTE:''' Genesys currently supports PostgreSQL 10.x for the Tenant Service. Testing is underway to confirm full support for version 11.x.
+
|Notes='''NOTE:''' Starting with version 100.0.100.0041, Tenant Service supports PostgreSQL 11.x.  
 
{{AnchorDiv|postgres}}
 
{{AnchorDiv|postgres}}
  
−
The PostgreSQL database is required for a Tenant Service. You can obtain the database credentials using one of the following methods:
+
Before deploying Tenant Service, you must provision a PostgreSQL database for Tenant Service using one of the following methods:
  
−
*Create its own PostgreSQL DB for a Tenant Service.
+
*Create a PostgreSQL database specifically for use by Tenant Service.
−
*Use the shared PostgreSQL DB, which is recommended in the OpenShift platform.
+
*Use the shared PostgreSQL database, which is recommended in the OpenShift platform.
  
−
Deploy a PostgreSQL database using the following commands:
+
Deploy a PostgreSQL database using the following commands:<source lang="text">
−
<source lang="text">
 
 
helm repo add bitnami https://charts.bitnami.com/bitnami
 
helm repo add bitnami https://charts.bitnami.com/bitnami
 
   
 
   
−
helm install -n voice t100postgres bitnami/postgresql
+
helm install -n voice <tenant id>postgres bitnami/postgresql
−
</source>
+
</source>During deployment, you require the database information, including credentials. For the list of database parameters that you override in the Tenant Helm chart '''values.yaml''' file, see [[Draft:PrivateEdition/Current/TenantPEGuide/Configure#backend|Backend parameters]] in {{Link-SomewhereInThisVersion|manual=TenantPEGuide|topic=Configure|anchor=OverrideValues|display text=Override Helm chart values}}.
 +
}}{{SectionThirdPartyItem
 +
|ThirdPartyItem=3e732261-b78e-4921-b6a6-08ee0a322ca1
 +
|Variation=No
 
}}
 
}}
 
|StorageStatus=No
 
|StorageStatus=No
−
|StorageText={{Notices|Notice=PEComingSoon}}
+
|StorageText=For information about storage requirements for Voice Microservices, including the Tenant Service, see {{Link-AnywhereElse|product=VM|version=Current|manual=VMPEGuide|topic=Planning|anchor=Storage|display text=Storage requirements}} in the ''Voice Microservices Private Edition Guide''.
 
|NetworkStatus=No
 
|NetworkStatus=No
−
|NetworkText={{Notices|Notice=PEComingSoon}}
+
|NetworkText=For general network requirements, review the information on the suite-level [[PrivateEdition/Current/PEGuide/ConfigNetwork|Network settings]] page.
 
|BrowserStatus=No
 
|BrowserStatus=No
 
|DependenciesStatus=No
 
|DependenciesStatus=No
Line 73: Line 80:
 
*Voice Config Service
 
*Voice Config Service
 
|GDPRStatus=No
 
|GDPRStatus=No
−
|GDPRText={{Notices|Notice=PEComingSoon}}
+
|GDPRText=Not applicable.
 
|PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167
 
|PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167
 
}}
 
}}

Latest revision as of 14:45, October 7, 2022

This topic is part of the manual Tenant Service Private Edition Guide for version Current of Genesys Multicloud CX Private Edition.

Find out what to do before deploying the Tenant Service.

Limitations and assumptions

Not applicable

Download the Helm charts

For information about how to download the Helm charts, see Downloading your Genesys Multicloud CX containers.

See Helm charts and containers for Voice Microservices for the Helm chart version you must download for your release.

Containers

The Tenant Service has the following containers:

  • Core tenant service container
  • Database initialization and upgrade container
  • Role and privileges  initialization and upgrade container
  • Solution specific: pulse provisioning container

Helm charts

  • Tenant deployment
  • Tenant infrastructure

Third-party prerequisites

For information about setting up your Genesys Multicloud CX private edition platform, see Software Requirements.

The following table lists the third-party prerequisites for the Tenant Service.

Third-party services
Name Version Purpose Notes
Kafka 2.x Message bus.
Consul 1.13.x Service discovery, service mesh, and key/value store.Starting with version 100.0.100.0041, Tenant Service supports Consul 1.10.
Redis 6.x Used for caching. Only distributions of Redis that support Redis cluster mode are supported, however, some services may not support cluster mode.
PostgreSQL 11.x Relational database.NOTE: Starting with version 100.0.100.0041, Tenant Service supports PostgreSQL 11.x.


Before deploying Tenant Service, you must provision a PostgreSQL database for Tenant Service using one of the following methods:

  • Create a PostgreSQL database specifically for use by Tenant Service.
  • Use the shared PostgreSQL database, which is recommended in the OpenShift platform.
Deploy a PostgreSQL database using the following commands:
helm repo add bitnami https://charts.bitnami.com/bitnami
 
helm install -n voice <tenant id>postgres bitnami/postgresql
During deployment, you require the database information, including credentials. For the list of database parameters that you override in the Tenant Helm chart values.yaml file, see Backend parameters in Override Helm chart values.
A container image registry and Helm chart repository Used for downloading Genesys containers and Helm charts into the customer's repository to support a CI/CD pipeline. You can use any Docker OCI compliant registry.

Storage requirements

For information about storage requirements for Voice Microservices, including the Tenant Service, see Storage requirements in the Voice Microservices Private Edition Guide.

Network requirements

For general network requirements, review the information on the suite-level Network settings page.

Browser requirements

Not applicable

Genesys dependencies

For detailed information about the correct order of services deployment, see Order of services deployment.

The following prerequisites are required before deploying the Tenant Service:

  • Voice Platform and all its external dependencies must be deployed before proceeding with the Tenant Service deployment.
  • PostgreSQL 10 database management system must be deployed and database shall be allocated either as a primary or replica. For more information about the sample deployment of a standalone DBMS, see Third-party prerequisites.

In addition, if you expect to use Agent Setup or Workspace Web Edition after the tenant is deployed, Genesys recommends that you deploy GWS Authentication Service before proceeding with the Tenant Service deployment.

Specific dependencies

The Tenant Service is dependent on the following platform endpoints:

  • GWS environment API
  • Interaction service core
  • Interaction service vq

The Tenant Service is dependent on the following service component endpoints:

  • Voice Front End Service
  • Voice Redis (RQ) Service
  • Voice Config Service

GDPR support

Not applicable.

Retrieved from "https://all.docs.genesys.com/PrivateEdition/Current/TenantPEGuide/Planning (2025-08-07 15:28:11)"
Comments or questions about this documentation? Contact us for support!