Before you begin

From Genesys Documentation
Revision as of 19:04, June 30, 2021 by Karl abraham.abel@genesys.com (talk | contribs) (Published)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
This topic is part of the manual Genesys Voice Platform Private Edition Guide for version Current of Genesys Voice Platform.

Find out what to do before deploying Genesys Voice Platform.

Limitations and assumptions

  • Third-party integrations like ASR/TTS or recording use cases are not supported in this initial release.
  • Resource Manager does not use gateway LRG configurations. Instead, it uses the contact center ID coming from SIP Server as gvp-tenant-id in the INVITE message to identify the tenant and pick the IVR Profiles.
  • Only single MCP LRG is supported per GVP deployment.
  • Only the specific component configuration options documented in Helm values.yaml overrides can be modified. Other configuration options can't be changed.
  • DID/DID groups are managed as part of Designer applications (Applications)
  • SIP TLS / SRTP are currently not supported.

Download the Helm charts

You will have to download the following GVP related Docker containers and Helm charts from the JFrog repository:

  • Docker containers
    • Media Control Platform - 9.0.048.65
    • Resource Manager - 9.0.048.31
    • Service Discovery - 9.0.000.52
    • Reporting Server - 9.0.048.18
    • GVP Configuration Server - 9.0.000.16
  • Helm charts
    • Media Control Platform - gvp-mcp-9.048.65.tgz
    • Resource Manager - gvp-rm-9.048.31.tgz
    • Service Discovery - gvp_sd-9.000.52.tgz
    • Reporting Server - gvp-rs-9.048.18.tgz
    • GVP Configuration Server - gvp-configserver-9.000.16.tgz

For more information on JFrog, refer to the Downloading your Genesys Engage containers topic in the Setting up Genesys Engage cloud private edition document.

Third-party prerequisites

Media Control Platform

Name Version OpenShift Operator Hub OpenShift Operator URL Purpose Configuration mode Notes
Consul 1.9.5 N/A N/A Service discovery, service mesh, and key/value store. The following features must be enabled in Consul:

Service Discovery – to register MCP service for auto discovery of MCP pods by RM

Resource Manager

Not applicable

Service Discovery

Name Version OpenShift Operator Hub OpenShift Operator URL Purpose Configuration mode Notes
Consul N/A N/A N/A

Reporting Server

Name Version OpenShift Operator Hub OpenShift Operator URL Purpose Configuration mode Notes
SQLServer 2016 N/A N/A

GVP Configuration Server

Name Version OpenShift Operator Hub OpenShift Operator URL Purpose Configuration mode Notes
PostGreSQL 11 N/A N/A

Storage requirements

Media Control Platform

Storage requirement for production (min)

Persistent Volume Size Type IOPS Functionality Container Critical Backup needed
recordings-volume 100Gi RWO high Storing recordings, dual AZ, gvp-mcp, rup Y Y
rup-volume 40Gi RWO high Storing recordings temporarily, dual AZ, rup Y Y
log-pvc 50Gi RW medium storing log files gvp-mcp Y Y

Storage requirements for Sandbox

Persistent Volume Size Type IOPS Functionality Container Critical Backup needed
recordings-volume 50Gi RWO high Storing recordings, dual AZ, gvp-mcp, rup Y Y
rup-volume 20Gi RWO high Storing recordings temporarily, dual AZ, rup Y Y
log-pvc 25Gi RW medium storing log files gvp-mcp Y Y

Resource Manager

Storage requirement for production (min)

Persistent Volume Min Size Type IOPS Functionality Container Critical Backup needed
billingpvc 20Gi RWO high billing gvp-rm Y Y
log-pvc 50Gi RW medium storing log files gvp-rm Y Y

Storage requirements for Sandbox

Persistent Volume Min Size Type IOPS Functionality Container Critical Backup needed
billingpvc 20Gi RWO high billing gvp-rm Y Y
log-pvc 10Gi RW medium storing log files gvp-rm Y Y

Service Discovery

Not applicable

Reporting Server

Storage requirement for production (min)

Persistent Volume Min Size Type IOPS Functionality Container Critical Backup needed
billing-pvc 20Gi files-standard-zrs High Stores ActiveMQ data and config information gvp-rs Y Y

Storage requirement for Sandbox

Persistent Volume Min Size Type IOPS Functionality Container Critical Backup needed
billing-pvc 10Gi files-standard-zrs High Stores ActiveMQ data and config information gvp-rs Y Y

GVP Configuration Server

Not applicable

Network requirements

Media Control Platform

Ingress

Not applicable

HA/DR

MCP is deployed with autoscaling in all regions. For more details, see the section Auto-scaling.

Calls are routed to active MCPs from GVP Resource Manager (RM) and in case of a MCP instance terminating, the calls are then routed to a different MCP instance.

Cross-region bandwidth

MCPs are not expected to be doing cross-region requests in normal mode of operation.

External connections

Not applicable

Pod Security Policy

All containers running as genesys user (500) and non-root user. 

podSecurityContext:
  fsGroup: 500
  runAsUser: 500
  runAsGroup: 500
  runAsNonRoot: true

SMTP Settings

Not applicable

TLS/SSL Certificates configurations

Not applicable

Resource Manager

Ingress

Not applicable

HA/DR

Resource Manager is deployed as the Active and Active pair.

Cross-region bandwidth

Resource Manager is deployed per region. There is no cross region deployment.

External connections

Not applicable

Pod Security Policy

All containers running as genesys user (500) and non-root user. 

podSecurityContext:
  fsGroup: 500
  runAsUser: 500
  runAsGroup: 500
  runAsNonRoot: true

SMTP Settings

Not applicable

TLS/SSL Certificates configurations

Not applicable

Service Discovery

Ingress

Not applicable

HA/DR

Service Discovery is a singleton service which will be restarted if it shuts down unexpectedly or becomes unavailable.

Cross-region bandwidth

Service Discovery is not expected to be doing cross-region requests in normal mode of operation.

External connections

Not applicable

Pod Security Policy

All containers running as genesys user (500) and non-root user. 

podSecurityContext:
  fsGroup: 500
  runAsUser: 500
  runAsGroup: 500
  runAsNonRoot: true

SMTP Settings

Not applicable

TLS/SSL Certificates configurations

Not applicable

Reporting Server

Ingress

Not applicable

HA/DR

Reporting Server is deployed as a single pod service.

Cross-region bandwidth

Reporting Server is deployed per region. There is no cross region deployment.

External connections

Not applicable

Pod Security Policy

All containers running as genesys user (500) and non-root user. 

podSecurityContext:
  fsGroup: 500
  runAsUser: 500
  runAsGroup: 500
  runAsNonRoot: true

SMTP Setting

Not applicable

TLS/SSL Certificates configurations

Not applicable

GVP Configuration Server

Ingress

Not applicable

HA/DR

GVP Configuration Server is deployed as a singleton. If the GVP Configuration Server crashes, a new pod will be created. The GVP services will continue to service calls if the GVP Configuration Server is unavailable and only new configuration changes, such as new MCP pods, will not be available.

Cross-region bandwidth

GVP Configuration Server is not expected to be doing cross-region requests in normal mode of operation.

External connections

External service Functionality
PostGresSQL database

Pod Security Policy

All containers running as genesys user (500) and non-root user. 

podSecurityContext:
  fsGroup: 500
  runAsUser: 500
  runAsGroup: 500
  runAsNonRoot: true

SMTP Settings

Not applicable

TLS/SSL Certificates configurations

Not applicable

Browser requirements

N/A

Genesys dependencies

Media Control Platform

Service Functionality
Consul Consul service must be deployed before deploying MCP for proper service registration in GVP Configuration Server and RM.

Resource Manager

Service Functionality
GVP Configuration Server GVP Configuration Server must be deployed before deploying RM for proper working.

Service Discovery

Service Functionality
Consul Consul service must be deployed before deploying Service Discovery for proper service registration in GVP Configuration Server and Resource Manager.

Reporting Server

Service Functionality
GVP Configuration Server GVP Configuration Server must be deployed before deploying RS for proper working.

GVP Configuration Server

N/A

Retrieved from "https://all.docs.genesys.com/GVP/Current/GVPPEGuide/Planning (2025-08-14 09:20:01)"
Comments or questions about this documentation? Contact us for support!