PrivateEdition/Current/PEGuide/Architecture - Revision history

WikiSysop at 04:01, March 31, 2023

2023-03-31T04:01:49Z

Richard.pfeiffer@genesys.com: Published

2021-12-21T17:34:54Z

Published

Richard.pfeiffer@genesys.com: Published

2021-12-01T22:27:40Z

Published

Show changes

Ed.jamer@genesys.com: Text replacement - "Genesys Engage" to "Genesys Multicloud CX"

2021-11-09T21:13:01Z

Text replacement - "Genesys Engage" to "Genesys Multicloud CX"

Ed.jamer@genesys.com: Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

2021-11-09T20:29:40Z

Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

Richard.pfeiffer@genesys.com: Published

2021-09-23T19:42:49Z

Published

Richard.pfeiffer@genesys.com: Published

2021-09-22T20:04:49Z

Published

Richard.pfeiffer@genesys.com: Published

2021-09-20T16:26:23Z

Published

Richard.pfeiffer@genesys.com: Published

2021-09-20T16:00:32Z

Published

Jose.druker@genesys.com: Published

2021-09-14T19:47:04Z

Published

@@ Line 156: / Line 156: @@
 *GKE Ingress is not supported for the initial private edition GKE offering. Instead, private edition requires deploying ingress-nginx.
 *Private edition does not support routes-based clusters.
 |Status=No
 }}{{Section
@@ Line 173: / Line 164: @@
 You are responsible for setting up security in the cluster.
-For more information about security-related topics, see {{Link-SomewhereInThisVersion|manual=PEGuide|topic=SecurityOverview}} and {{Link-SomewhereInThisVersion|manual=PEGuide|topic=ConfigSecurity}}.
+For more information about security-related topics, see {{Link-SomewhereInThisVersion|manual=PEGuide|topic=SecurityOverview}}.
 |Status=No
 }}{{Section
@@ Line 420: / Line 411: @@
 You can enable the [https://cloud.google.com/stackdriver/docs/solutions/gke/managing-metrics#workload-metrics GKE workload metrics] in order to scrape application metrics based on the PodMonitor resource definition. If a service doesn't provide a PodMonitor resource, then you might need to deploy a [https://cloud.google.com/stackdriver/docs/solutions/gke/prometheus Prometheus server with a Stackdriver collector] in order to expose Genesys custom application metrics as external metrics in Cloud Monitoring, which does incur an additional cost.
-====OpenShift====
-Private edition uses [https://docs.openshift.com/container-platform/4.6/monitoring/enabling-monitoring-for-user-defined-projects.html OpenShift monitoring] to verify all metrics provided by the pods.
+===={{Editgrn open}}AKS{{Editgrn close}}====
 ===Logging===
@@ Line 434: / Line 430: @@
 *Send them to an RWX/NFS-style log volume provided by a shared Cloud Filestore for legacy or high volume logging.<br />'''Note:''' RWX/NFS logging will be deprecated in the near future.
-====OpenShift====
+===={{Editgrn open}}AKS{{Editgrn close}}====
-Private edition uses [https://docs.openshift.com/container-platform/4.6/logging/cluster-logging.html OpenShift logging] to verify all logs provided by the pods.
+You can use the [https://learn.microsoft.com/en-us/azure/azure-monitor/logs/log-analytics-workspace-overview Log Analytics workspace feature] in Azure Monitor for collecting log data of system and workloads in private edition. You can create single or multiple log analytics workspaces based on your organizational needs.
 |Status=No
 }}{{Section

@@ Line 9: / Line 9: @@
 [[File:Pe-multicloud-unit-architecture.png]]
 |Status=No
 }}{{Section
@@ Line 56: / Line 55: @@
 ====Unit groups====
-Unit groups interconnect their constituent units by means of a network peering solution, and all inter-region traffic uses either your network connectivity or the network connectivity of your cloud provider. Each group contains a primary unit in each region. This primary regional unit hosts all of the private edition services, while the secondary regional unit hosts only a subset of private edition services. A unit group must contain at least one unit pair. If you add a new geographical region, then you must add a unit pair to the unit group in that geographical region.
+Unit groups interconnect their constituent units by means of a network peering solution, and all inter-region traffic uses either your network connectivity or the network connectivity of your cloud provider. Each group contains a primary unit in one region in the group. This primary regional unit hosts all of the private edition services, while the secondary regional unit hosts only a subset of private edition services. A unit group must contain at least one unit pair. If you add a new geographical region, then you must add a unit pair to the unit group in that geographical region.
 <br />
@@ Line 159: / Line 158: @@
 ===OpenShift===
-{{Notices|Notice=PEComingSoon}}
+The Genesys implementation of OpenShift requires:
 |Status=No
 }}{{Section
@@ Line 187: / Line 192: @@
 ===Elasticsearch / OpenSearch===
 The Elasticsearch and OpenSearch services are shareable across tenants, but the tenant data is never shared.
 {{{!}} class="wikitable" width="651" min-scale="0.9216589861751152"
@@ Line 220: / Line 227: @@
 ===Redis===
 The Redis service is shareable across tenants, but the tenant data is never shared.
 {{{!}} class="wikitable" width="651" min-scale="0.9216589861751152"
 {{!}} class="x_xl67" width="251" height="61"{{!}}'''Service'''
@@ Line 358: / Line 377: @@
 |alignment=Vertical
 |structuredtext=For more information, see {{Link-SomewhereInThisVersion|manual=PEGuide|topic=StorageReq|display text=Storage Requirements}}.
 |Status=No
 }}{{Section

@@ Line 15: / Line 15: @@
 The basic architecture for private edition involves three levels:
-*A '''unit''' consists of all of the Genesys Engage and third-party services and resources required to create a single instance of Genesys Multicloud CX private edition. This instance is hosted within a single region or data center.
+*A '''unit''' consists of all of the Genesys Multicloud CX and third-party services and resources required to create a single instance of Genesys Multicloud CX private edition. This instance is hosted within a single region or data center.
 *A '''unit group''' brings together a network of units to create a global platform for tenants that covers all geographical regions
@@ Line 84: / Line 84: @@
 ====Subnets====
-Subnets are your responsibility: you must create a subnet for the Kubernetes cluster to accommodate the Genesys Engage services.
+Subnets are your responsibility: you must create a subnet for the Kubernetes cluster to accommodate the Genesys Multicloud CX services.
 ===Network access===
@@ Line 93: / Line 93: @@
 |anchor=services
 |alignment=Vertical
-|structuredtext=Genesys Multicloud CX private edition supports the services listed on the {{Link-SomewhereInThisVersion|manual=PEGuide|topic=GEServices|display text=Genesys Engage services list}}.
+|structuredtext=Genesys Multicloud CX private edition supports the services listed on the {{Link-SomewhereInThisVersion|manual=PEGuide|topic=GEServices|display text=Genesys Multicloud CX services list}}.
 |Status=No
 }}{{Section
 |sectionHeading=Software requirements
 |alignment=Vertical
-|structuredtext=Genesys Multicloud CX private edition requires the software and versions listed on the {{Link-SomewhereInThisVersion|manual=PEGuide|topic=Prerequisites|display text=software requirements page}}. Note that you are responsible for installing and deploying the appropriate third-party software in a way that best suits your requirements and the requirements of the Genesys Engage services.
+|structuredtext=Genesys Multicloud CX private edition requires the software and versions listed on the {{Link-SomewhereInThisVersion|manual=PEGuide|topic=Prerequisites|display text=software requirements page}}. Note that you are responsible for installing and deploying the appropriate third-party software in a way that best suits your requirements and the requirements of the Genesys Multicloud CX services.
 |Status=No
 }}{{Section
 |sectionHeading=Kubernetes clusters
 |alignment=Vertical
-|structuredtext=All Genesys Engage services must run in Kubernetes. Required third-party services can be managed either outside Kubernetes or within Kubernetes. Kubernetes is responsible for managing the running of services, such as monitor restart, and so on.
+|structuredtext=All Genesys Multicloud CX services must run in Kubernetes. Required third-party services can be managed either outside Kubernetes or within Kubernetes. Kubernetes is responsible for managing the running of services, such as monitor restart, and so on.
 Private edition does not currently support multiple instances of the platform in a single Kubernetes cluster. In other words, if you want to set up separate environments for testing, staging, production, and so on, you must deploy the private edition instances for the various environments in separate clusters.
 ===Deployment===
-Genesys currently recommends that you use node pools to deploy Kubernetes for the Genesys Engage services that are hosted within each unit.
+Genesys currently recommends that you use node pools to deploy Kubernetes for the Genesys Multicloud CX services that are hosted within each unit.
 *'''Node pools'''—Genesys recommends that you use the following node pools. Our Helm charts include overrides for the nodeSelector attribute. Use these overrides to assign a service to the appropriate node pool.
-**'''General node pool'''—This node pool is where most of the Genesys Engage services are deployed. This type of pool uses general-purpose compute instances with Premium SSD, which provide a 4:1 ratio of memory GB to vCPU.
+**'''General node pool'''—This node pool is where most of the Genesys Multicloud CX services are deployed. This type of pool uses general-purpose compute instances with Premium SSD, which provide a 4:1 ratio of memory GB to vCPU.
 **Real-time '''node pool'''—This node pool is for stateful voice services that require a drain time of 60 minutes or longer to maintain active voice sessions. It uses general-purpose nodes with Premium SSD.
 **'''Third-party service node pool (optional)'''—This node pool is only needed if you are going to deploy data stores and other third-party services in Kubernetes, such as Redis, Kafka, Postgres or Elasticsearch. These services generally need locally optimized storage and will use the storage-optimized nodes with directly attached NVMe and Premium SSD, which provide an 8:1 ratio of memory GB to vCPU.
@@ Line 129: / Line 129: @@
 Most services scale their Kubernetes pods by using the [https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/ Horizontal Pod Autoscaler]. However, this tool can only use CPU or memory metrics from the Kubernetes Metric Server in the HorizontalPodAutoscaler Object. Private edition also works with the Kubernetes cluster scaler. Note that each service provides its own autoscaling rule, and that the autoscaling rule for a specific service is stored in the Helm charts for that service.
-Genesys uses the third-party [https://keda.sh/ KEDA] open-source autoscaler for Genesys Engage services that require custom metrics from Prometheus. Use the included Helm override attributes to adjust the defaults for each service.
+Genesys uses the third-party [https://keda.sh/ KEDA] open-source autoscaler for Genesys Multicloud CX services that require custom metrics from Prometheus. Use the included Helm override attributes to adjust the defaults for each service.
-You must perform your own scaling operations on the Kubernetes control plane. The operational requirements of this scaling depend on the size of your contact center. For large installations, you might need to deploy multiple clusters and distribute the Genesys Engage services across them.
+You must perform your own scaling operations on the Kubernetes control plane. The operational requirements of this scaling depend on the size of your contact center. For large installations, you might need to deploy multiple clusters and distribute the Genesys Multicloud CX services across them.
 ===ConfigMaps===
@@ Line 137: / Line 137: @@
 ===Operators===
-You can use OpenShift operators to deploy most third-party services into OpenShift. Note that Genesys does not provide operators to deploy Genesys Engage services.
+You can use OpenShift operators to deploy most third-party services into OpenShift. Note that Genesys does not provide operators to deploy Genesys Multicloud CX services.
 |Status=No
 }}{{Section

@@ Line 2: / Line 2: @@
 |Standalone=No
 |DisplayName=Architecture
-|Context=Understand the architecture and components of Genesys Engage cloud private edition; the supported third-party back-end services; and how they all work together in both single- and multi-region deployments.
+|Context=Understand the architecture and components of Genesys Multicloud CX private edition; the supported third-party back-end services; and how they all work together in both single- and multi-region deployments.
 |ComingSoon=No
 |Section={{Section
 |alignment=Vertical
-|structuredtext=As mentioned in the {{Link-SomewhereInThisVersion|manual=PEGuide|topic=Overview|display text=About}} page, Genesys Engage cloud private edition gives you the flexibility to deploy your contact center on a public cloud or a private one—and even on bare metal servers that reside within your corporate data center.
+|structuredtext=As mentioned in the {{Link-SomewhereInThisVersion|manual=PEGuide|topic=Overview|display text=About}} page, Genesys Multicloud CX private edition gives you the flexibility to deploy your contact center on a public cloud or a private one—and even on bare metal servers that reside within your corporate data center.
 |Status=No
 }}{{Section
@@ Line 15: / Line 15: @@
 The basic architecture for private edition involves three levels:
-*A '''unit''' consists of all of the Genesys Engage and third-party services and resources required to create a single instance of Genesys Engage cloud private edition. This instance is hosted within a single region or data center.
+*A '''unit''' consists of all of the Genesys Engage and third-party services and resources required to create a single instance of Genesys Multicloud CX private edition. This instance is hosted within a single region or data center.
 *A '''unit group''' brings together a network of units to create a global platform for tenants that covers all geographical regions
@@ Line 60: / Line 60: @@
 ====Deployment models====
-Genesys Engage cloud private edition allows you to set up a highly available and resilient infrastructure whether you are using a {{Link-SomewhereInThisVersion|manual=PEGuide|topic=HADR|anchor=cloud-architecture|display text=cloud}} deployment or hosting it in a {{Link-SomewhereInThisVersion|manual=PEGuide|topic=HADR|anchor=private-architecture|display text=private data center}}, as shown in the following diagrams.
+Genesys Multicloud CX private edition allows you to set up a highly available and resilient infrastructure whether you are using a {{Link-SomewhereInThisVersion|manual=PEGuide|topic=HADR|anchor=cloud-architecture|display text=cloud}} deployment or hosting it in a {{Link-SomewhereInThisVersion|manual=PEGuide|topic=HADR|anchor=private-architecture|display text=private data center}}, as shown in the following diagrams.
 <br />
@@ Line 93: / Line 93: @@
 |anchor=services
 |alignment=Vertical
-|structuredtext=Genesys Engage cloud private edition supports the services listed on the {{Link-SomewhereInThisVersion|manual=PEGuide|topic=GEServices|display text=Genesys Engage services list}}.
+|structuredtext=Genesys Multicloud CX private edition supports the services listed on the {{Link-SomewhereInThisVersion|manual=PEGuide|topic=GEServices|display text=Genesys Engage services list}}.
 |Status=No
 }}{{Section
 |sectionHeading=Software requirements
 |alignment=Vertical
-|structuredtext=Genesys Engage cloud private edition requires the software and versions listed on the {{Link-SomewhereInThisVersion|manual=PEGuide|topic=Prerequisites|display text=software requirements page}}. Note that you are responsible for installing and deploying the appropriate third-party software in a way that best suits your requirements and the requirements of the Genesys Engage services.
+|structuredtext=Genesys Multicloud CX private edition requires the software and versions listed on the {{Link-SomewhereInThisVersion|manual=PEGuide|topic=Prerequisites|display text=software requirements page}}. Note that you are responsible for installing and deploying the appropriate third-party software in a way that best suits your requirements and the requirements of the Genesys Engage services.
 |Status=No
 }}{{Section
@@ Line 142: / Line 142: @@
 |sectionHeading=Security
 |alignment=Vertical
-|structuredtext=Genesys Engage cloud private edition has been developed using industry-standard tools and best practices to identify and eliminate security vulnerabilities.
+|structuredtext=Genesys Multicloud CX private edition has been developed using industry-standard tools and best practices to identify and eliminate security vulnerabilities.
 You are responsible for setting up security in the cluster.

@@ Line 23: / Line 23: @@
 [[File:Pe-units-pairs-and-groups.png]]The following definitions describe important features of the private edition architecture:
-*'''Region'''—A set of isolated and physically separated Availability Zones deployed within a latency-defined perimeter and connected through a dedicated low-latency network within a specific geographical area. '''Note:''' Regions as defined here are a feature of the [[Draft:PrivateEdition/Current/PEGuide/HADR#cloud-architecture|cloud]] deployment architecture and are not supported in the [[Draft:PrivateEdition/Current/PEGuide/HADR#private-architecture|private data center]] deployment architecture, which does not use Availability Zones.
+*'''Region'''—A set of isolated and physically separated Availability Zones deployed within a latency-defined perimeter and connected through a dedicated low-latency network within a specific geographical area. '''Note:''' Regions as defined here are a feature of the {{Link-SomewhereInThisVersion|manual=PEGuide|topic=HADR|anchor=cloud-architecture|display text=cloud}} deployment architecture and are not supported in the {{Link-SomewhereInThisVersion|manual=PEGuide|topic=HADR|anchor=private-architecture|display text=private data center}} deployment architecture, which does not use Availability Zones.
 *'''Data center'''—A building, a dedicated space within a building, or a group of buildings used to house computer systems and associated components, such as telecommunications and storage systems.
-*'''Availability Zone (AZ)'''—A discrete location within a region that is designed to operate independently from the other Availability Zones in that region. Because of this separation, any given Availability Zone is unlikely to be affected by failures in other Availability Zones. '''Note:''' Availability Zones are a feature of the [[Draft:PrivateEdition/Current/PEGuide/HADR#cloud-architecture|cloud]] deployment architecture and are not supported in the [[Draft:PrivateEdition/Current/PEGuide/HADR#private-architecture|private data center]] deployment architecture.
+*'''Availability Zone (AZ)'''—A discrete location within a region that is designed to operate independently from the other Availability Zones in that region. Because of this separation, any given Availability Zone is unlikely to be affected by failures in other Availability Zones. '''Note:''' Availability Zones are a feature of the {{Link-SomewhereInThisVersion|manual=PEGuide|topic=HADR|anchor=cloud-architecture|display text=cloud}} deployment architecture and are not supported in the {{Link-SomewhereInThisVersion|manual=PEGuide|topic=HADR|anchor=private-architecture|display text=private data center}} deployment architecture.
 *'''Tenant'''—A business entity that has common goals and procedures, and occupies part or all of a contact center. Tenants that share a contact center could be different businesses, or different divisions within the same business.
 *'''Multi-tenancy'''—The partitioning capacity for a platform to host and manage tenants. Each tenant is configured individually and separately.
@@ Line 60: / Line 60: @@
 ====Deployment models====
-Genesys Engage cloud private edition allows you to set up a highly available and resilient infrastructure whether you are using a [[Draft:PrivateEdition/Current/PEGuide/HADR#cloud-architecture|cloud]] deployment or hosting it in a [[Draft:PrivateEdition/Current/PEGuide/HADR#private-architecture|private data center]], as shown in the following diagrams.
+Genesys Engage cloud private edition allows you to set up a highly available and resilient infrastructure whether you are using a {{Link-SomewhereInThisVersion|manual=PEGuide|topic=HADR|anchor=cloud-architecture|display text=cloud}} deployment or hosting it in a {{Link-SomewhereInThisVersion|manual=PEGuide|topic=HADR|anchor=private-architecture|display text=private data center}}, as shown in the following diagrams.
 <br />

@@ Line 137: / Line 137: @@
 For more information about security-related topics, see {{Link-SomewhereInThisVersion|manual=PEGuide|topic=SecurityOverview}} and {{Link-SomewhereInThisVersion|manual=PEGuide|topic=ConfigSecurity}}.
 |Status=No
 }}{{Section
@@ Line 246: / Line 245: @@
 {{!}}- height="43"
 {{!}} class="x_xl68" width="251" height="43"{{!}}GWS
-{{!}} class="x_xl66" width="251"{{!}}cached statistics, interaction and agent data.
+{{!}} class="x_xl66" width="251"{{!}}cached statistics, interaction and agent data
 {{!}} class="x_xl65" width="85"{{!}}Yes
 {{!}}No
@@ Line 274: / Line 273: @@
 {{!}}- height="21"
 {{!}} class="x_xl66" width="251" height="21"{{!}}IXN
-{{!}} class="x_xl66" width="251"{{!}}digital interaction and agent data
+{{!}} class="x_xl66" width="251"{{!}}digital interaction data
 {{!}} class="x_xl65" width="85"{{!}}No
 {{!}}No