PrivateEdition/Current/PEGuide/StorageReq - Revision history

WikiSysop at 04:02, March 31, 2023

2023-03-31T04:02:06Z

WikiSysop at 14:30, September 30, 2022

2022-09-30T14:30:46Z

Show changes

Uma.jayakumar.IX: Published

2021-12-22T18:58:34Z

Published

Show changes

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

2021-11-09T21:12:32Z

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:00Z

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

Tanya.ivanova@genesys.com: Published

2021-08-05T22:27:57Z

Published

Uma.jayakumar@genesys.com: Published

2021-07-07T11:36:19Z

Published

Uma.jayakumar@genesys.com: Published

2021-07-05T09:03:58Z

Published

Uma.jayakumar@genesys.com: Published

2021-06-30T18:51:02Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Storage requirements
|Context=Provides information about different storage types required for Genesys Engage services.
|ComingSoon=No
|Section={{Section
|sectionHeading=File and disk storage
|alignment=Vertical
|structuredtext=Deciding storage includes a lot of factors such as the number of agents, call volumes, call recordings and archiving them, data security, accessibility and so on. It also includes technical factors such as the Input Output Per Second (IOPS) or throughput, storage type, latency, and so on.

In Genesys Engage cloud private edition, you will create storage for specific services, for example, GCXI, Voice. The services that require storage elements such as file and disk storage for processing its data uses the [https://kubernetes.io/docs/concepts/storage/persistent-volumes/ Kubernetes Persistence Volume subsystem] (PV).
The storage subsystem and Kubernetes StorageClass types requirements for different services are given in the following table. You can create or select the storage subsystem for your service based on the information presented in the table. For the exact sizing of each storage subsystem or PVs, refer the related service-level documentation.

{{NoteFormat|By default, the Kubernetes platform creates default file and disk storage classes. However, Genesys recommends not to use them and create custom a file and disk storage for your service.|1}}
{{NoteFormat|You can determine the storage requirements for your contact center yourself by either exploring the storage requirements of each service, using the Sizing Calculator or by leveraging the Genesys Professional Services team's support.|2}}
{{{!}} class="wikitable"
{{!}}+
{{!}}'''Storage Type'''
{{!}}'''Description'''
{{!}}'''Associated Services'''
{{!}}-
{{!}}Disk-node ephemeral
{{!}}This is the node disk which is used for temporary storage.
{{!}}GCXI, GVP-MCP, Voice services, Pulse, IXN, WebRTC, GplusWFM, Tenant
{{!}}-
{{!}}Disk
{{!}}Uses dynamically provisioned disks (which reside in a single AZ) to create an RWO volume that can be attached to a single pod. Genesys recommends SSD storage for production deployments.
{{!}}GVP-RM, GVP-MCP, RUP, GplusWFM, Voice services, Designer
{{!}}-
{{!}}Files-local
{{!}}Create an RWX volume that can be attached to many pods across all the node pool AZs; this is similar to NFS. Local type means the 'Locally Redundant Storage' which replicates copies of data in a single AZ in a single region. Hence, there is a risk of your Persistent Volume Claims (PVCs) becoming unavailable if a single region completely fails. It needs guarantees of 1 IOPs per GB stored with a minimum of 100 IOPs while allowing bursting and higher throughput than standard HDD storage. SSD storage is recommended for production deployments.
{{!}}Designer, BDS, GIM, GSP, Voice services
{{!}}-
{{!}}Files-redundant
{{!}}Create an RWX volume that can be attached to many pods across all the node pool AZs. Redundant type means the 'Zonal Redundant Storage' which replicates copies of data across multiple AZs in a region. No IOPs guarantees needed; this is similar to NFS.
{{!}}CXC, GCXI, Designer, Tenant, lwauth, AriaWFM, Nexus, GVP //Should we remove lwauth and AriaWFM?
{{!}}-
{{!}}blob storage
{{!}}Create Blob storage which is optimized for storing massive amounts of unstructured data across AZ and regions. Blob storage is similar to S3 or Azure Blob, Google Cloud Storage.
{{!}}Voicemail, Recordings (GVP), Data Feed data
{{!}}}
|Status=No
}}
}}

@@ Line 12: / Line 12: @@
 *[[{{FULLPAGENAME}}#storageAKS|File and disk storage for Azure Kubernetes Service (AKS)]]
 *[[{{FULLPAGENAME}}#storageGKE|File and disk storage for Google Kubernetes Engine (GKE)]]
-*[[{{FULLPAGENAME}}#storageOCP|File and disk storage for OpenShift]]
 You can create or select the storage subsystem for your service on a specific Kubernetes platform based on the information presented in the corresponding table. For the exact sizing of each storage subsystem or PVs, refer to the related {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=GEServices|display text=service-level documentation}}.
@@ Line 164: / Line 164: @@
 |Status=No
 }}
+<br />
 |Status=No
 }}
 }}

@@ Line 22: / Line 22: @@
 {{!}}Disk
 {{!}}Uses dynamically provisioned disks (which reside in a single AZ) to create an RWO volume that can be attached to a single pod. Genesys recommends SSD storage for production deployments.
-{{!}}Designer, GCXI, GVP-MCP, GVP-RM, gPlus-WFM, IXN, Pulse, Tenant, Voice Services, and WebRTC
+{{!}}GCXI*, GVP, gPlus-WFM, IXN*, Pulse*, Tenant*, Voice Services*, and WebRTC*
 {{!}}-
 {{!}}Files-local
 {{!}}Create an RWX volume that can be attached to many pods across all the node pool AZs; this is similar to NFS. Local type means the 'Locally Redundant Storage' which replicates copies of data in a single AZ in a single region. Hence, there is a risk of your Persistent Volume Claims (PVCs) becoming unavailable if a single region completely fails. It needs guaranteed 1 IOPs per GB stored with a minimum of 100 IOPs while allowing bursting and higher throughput than standard HDD storage. Genesys recommends SSD storage for production deployments. '''Note:''' The minimum volume size needed is 100GB.
-{{!}}BDS, Designer, GIM, gPlus-WFM, GSP, and Voice Services
+{{!}}BDS
 {{!}}-
 {{!}}Files-redundant
 {{!}}Create an RWX volume that can be attached to many pods across all the node pool AZs. Redundant type means the 'Zonal Redundant Storage' which replicates copies of data across multiple AZs in a region. No IOPs guarantees needed. Similar to NFS.
-{{!}}BDS, CXC, Designer, GCXI, gPlus-WFM, GVP, GWS, Pulse, Tenant, UCSX, and IWD
+{{!}}CXC, Designer, GCXI, gPlus-WFM, GVP, GWS, IWD, Pulse*, Tenant*, UCSX, and WebRTC*
 {{!}}-
-{{!}}blob storage
+{{!}}Object storage
-{{!}}Create Blob storage which is optimized for storing massive amounts of unstructured data across AZ and regions. Similar to S3 or Azure Blob, Google Cloud Storage.
+{{!}}Create object storage which is optimized for storing massive amounts of unstructured data across AZ and regions. Similar to S3 or Azure Blob, Google Cloud Storage.
-{{!}}GIM data feeds, Recordings, Voicemail, and Telemetry
+{{!}}GIM data feed/GSP, Nexus (image, files, upload), Recordings(GVP), Voicemail, and Telemetry
 {{!}}}
 |Status=No
 }}
 }}

@@ Line 2: / Line 2: @@
 |Standalone=No
 |DisplayName=Storage requirements
-|Context=Provides information about different storage types required for Genesys Engage services.
+|Context=Provides information about different storage types required for Genesys Multicloud CX services.
 |ComingSoon=No
 |Section={{Section
@@ Line 38: / Line 38: @@
 {{!}}}
-<nowiki>*</nowiki>''Genesys Engage services that use the disk space mainly for logging purposes. You can optionally configure them not to use the disk space. Refer the related service-level guides for more information.''
+<nowiki>*</nowiki>''Genesys Multicloud CX services that use the disk space mainly for logging purposes. You can optionally configure them not to use the disk space. Refer the related service-level guides for more information.''
 |Status=No
 }}
 }}

@@ Line 9: / Line 9: @@
 |structuredtext=Deciding storage includes a lot of factors such as the number of agents, call volumes, call recordings and archiving them, data security, accessibility and so on. It also includes technical factors such as the Input Output Per Second (IOPS) or throughput, storage type, latency, and so on.
-In Genesys Engage cloud private edition, you will create storage for specific services, for example, GCXI, Voice. The services that require storage elements such as file and disk storage for processing its data uses the [https://kubernetes.io/docs/concepts/storage/persistent-volumes/ Kubernetes Persistence Volume subsystem] (PV).
+In Genesys Multicloud CX private edition, you will create storage for specific services, for example, GCXI, Voice. The services that require storage elements such as file and disk storage for processing its data uses the [https://kubernetes.io/docs/concepts/storage/persistent-volumes/ Kubernetes Persistence Volume subsystem] (PV).
 The storage subsystem and Kubernetes StorageClass types requirements for different services are given in the following table. You can create or select the storage subsystem for your service based on the information presented in the table. For the exact sizing of each storage subsystem or PVs, refer the related service-level documentation.

@@ Line 19: / Line 19: @@
 {{!}}'''Description'''
 {{!}}'''Associated Services'''
 {{!}}-
 {{!}}Disk
@@ Line 34: / Line 30: @@
 {{!}}Files-redundant
 {{!}}Create an RWX volume that can be attached to many pods across all the node pool AZs. Redundant type means the 'Zonal Redundant Storage' which replicates copies of data across multiple AZs in a region. No IOPs guarantees needed; this is similar to NFS.
-{{!}}CXC, GCXI, Designer, Tenant, lwauth, AriaWFM, Nexus, GVP //Should we remove lwauth and AriaWFM?
+{{!}}BDS, CXC, Designer, GCXI, gPlus-WFM, GVP, GWS, Pulse, Tenant, UCSX, IWD
 {{!}}-
 {{!}}blob storage