PrivateEdition/Current/PEGuide/ServicePriorities - Revision history

WikiSysop at 06:45, June 28, 2022

2022-06-28T06:45:49Z

WikiSysop at 06:45, June 27, 2022

2022-06-27T06:45:42Z

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

2021-11-09T21:28:25Z

Text replacement - "Genesys Cloud" to "Genesys Cloud CX"

Ed.jamer@genesys.com: Text replacement - "Genesys Multicloud CXment" to "Genesys Engagement"

2021-11-09T21:15:36Z

Text replacement - "Genesys Multicloud CXment" to "Genesys Engagement"

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

2021-11-09T21:12:36Z

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

Uma.jayakumar@genesys.com: Published

2021-07-13T09:56:14Z

Published

Uma.jayakumar@genesys.com: Published

2021-07-13T09:48:44Z

Published

Uma.jayakumar@genesys.com: Published

2021-07-07T13:58:51Z

Published

Uma.jayakumar@genesys.com: Published

2021-06-30T18:51:03Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Service priorities for Genesys Engage services
|Context=Learn about service priorities of Genesys Engage Services.
|ComingSoon=No
|Section={{Section
|alignment=Vertical
|structuredtext=Genesys has assigned a service priority class for each Genesys Engage service based on the Kubernetes Pod Priority guidelines. The guideline states to use a value of one million for high priority pods and values of two billion and above for Kubernetes itself for cluster critical Pods like kube-proxy and core-dns. Genesys has designed the service priority values for each priority class such as ''Critical'', ''Medium'', and ''Low'', and categorized the services under different service priority classes based on their business function. For example, Voice services are given 'Critical' priority because they cannot handle long delays. You can override this value in your Helm charts before deployment.

Before overriding, remember that the Pods will be evicted from the node based on the service priority you set. Hence, it is essential to assign service priority based on your business requirements.

====Sample Service Priority configuration====
If you want to override the service priority for a service,

*Define an optional '''priorityClassName''' variable in the '''values.yaml''' file of the corresponding service.
*Assign the service priority value such as '''genesysengage-critical-priority, genesysengage-medium-priority,''' or '''genesysengage-low-priority'''. Your values.yaml configuration looks like the following:

<code>priorityClassName: genesysengage-medium-priority</code>

*Now, in your Deployment/ReplicaSet chart, include the '''priorityClassName''' by adding the following code as part of the pod spec:

 

<source>
spec:
template:
spec:
containers:
. . .
{{- if .Values.priorityClassName }}
priorityClassName: {{.Values.priorityClassName }}
{{- end }}
</source>

The following table illustrates the Genesys chosen priority class and its priority value.
{{{!}} class="wikitable"
{{!}}+
!Priority
!Priority Value
!Usage Notes
{{!}}-
{{!}}Critical
{{!}}10,000,000
{{!}}Use this priority for Genesys Engage services that must '''not''' be evicted due to resource limitations and can evict all other lower priority services, when needed.
{{!}}-
{{!}}High
{{!}}1,000,000
{{!}}Use this priority for Genesys Engage services that might be evicted by critical services but will evict lower priority services, when needed.
{{!}}-
{{!}}Medium
{{!}}100,000
{{!}}Use this priority for Genesys Engage services that might be evicted by critical or high priority services but will only evict lower or default priority services, when needed.
{{!}}-
{{!}}<none>
{{!}}0
{{!}}Use this priority for Genesys Engage services that can be evicted for more than 24 hours, if needed.
{{!}}}

The following table illustrates the recommended priority for each Genesys Engage service at a granular level.
{{{!}} class="wikitable" border="1" cellspacing="0" cellpadding="0"
{{!}} width="133" valign="top"{{!}}'''Services Groups'''
{{!}} width="299" valign="top"{{!}}'''Services'''
{{!}} width="110" valign="top"{{!}}'''Service Priority'''
{{!}}-
{{!}} width="133" valign="top"{{!}}'''Designer'''
{{!}} width="299" valign="top"{{!}}Designer

Designer Application Service
{{!}} width="110" valign="top"{{!}}medium

critical
{{!}}-
{{!}} width="133" valign="top"{{!}}'''Genesys Web Services (GWS/GAPI)'''
{{!}} width="299" valign="top"{{!}}9.x GWS Chat Service

9.x GWS Configuration Service

9.x GWS Environment Service

9.x GWS Feedback Service

9.x GWS Interaction Service

9.x GWS OCS Service

9.x GWS Provisioning Service

9.x GWS Setting Service

9.x GWS SPL Service

9.x GWS Statistics Service

9.x GWS UCS Service

9.x GWS Voice Service

9.x GWS Workspace Service

Workspace Web Edition (9.x)

Agent Setup
{{!}} width="110" valign="top"{{!}}high

critical

critical

medium

high

high

high

critical

high

high

high

critical

critical

critical

critical
{{!}}-
{{!}} width="133" valign="top"{{!}}'''Genesys Engagement Service (Callback and Mobile)'''
{{!}} width="299" valign="top"{{!}}Genesys Engagement Service
{{!}} width="110" valign="top"{{!}}high
{{!}}-
{{!}} width="133" valign="top"{{!}}'''Genesys Cloud Hybrid Integration'''
{{!}} width="299" valign="top"{{!}}Conversation Provider

User Event Generator

Data Sync

Screen Recording Gateway

Lightweight Authentication Service
{{!}} width="110" valign="top"{{!}}high

high

high

high

high
{{!}}-
{{!}} width="133" valign="top"{{!}}'''Historical Reporting Back-end'''
{{!}} width="299" valign="top"{{!}}GIM

GCA

GSP
{{!}} width="110" valign="top"{{!}}high

medium

high
{{!}}-
{{!}} width="133" valign="top"{{!}}'''Historical Reporting Front-end'''
{{!}} width="299" valign="top"{{!}}GCXI
{{!}} width="110" valign="top"{{!}}medium
{{!}}-
{{!}} width="133" valign="top"{{!}}'''Realtime Reporting'''
{{!}} width="299" valign="top"{{!}}Quick Update

Pulse web backend

Object Browser

Tenant Load Distribution Server (LDS)

Tenant Collector
{{!}} width="110" valign="top"{{!}}high

high

high

high

high
{{!}}-
{{!}} width="133" valign="top"{{!}}'''Digital/Nexus'''
{{!}} width="299" valign="top"{{!}}Nexus

Interaction Server (IXN)

UCS-X
{{!}} width="110" valign="top"{{!}}high

high

high
{{!}}-
{{!}} width="133" valign="top"{{!}}'''IWD'''
{{!}} width="299" valign="top"{{!}}IWD

IWD DataMart

Email Service
{{!}} width="110" valign="top"{{!}}high

medium

high
{{!}}-
{{!}} width="133" valign="top"{{!}}'''CX-Contact'''
{{!}} width="299" valign="top"{{!}}CX Contact API Aggregator

CX Contact Campaign Manager

CX Contact Compliance Manager

CX Contact Job Scheduler

CX Contact List Builder

CX Contact List Manager

CX Contact UI
{{!}} width="110" valign="top"{{!}}High

high

high

high

high

high

high
{{!}}-
{{!}} width="133" valign="top"{{!}}'''GVP'''
{{!}} width="299" valign="top"{{!}}Voice Platform MCP

Voice Platform MRCP Proxy

Voice Platform Reporting Server

Voice Platform RM

Voice Platform Config Server

Voice Platform Tenant Provisioner
{{!}} width="110" valign="top"{{!}}critical

critical

high

critical

critical

critical
{{!}}-
{{!}} width="133" valign="top"{{!}}'''WebRTC'''
{{!}} width="299" valign="top"{{!}}WebRTC CoTurn Service

WebRTC Gateway Service
{{!}} width="110" valign="top"{{!}}critical

critical
{{!}}-
{{!}} width="133" valign="top"{{!}}'''Voice Microservice'''
{{!}} width="299" valign="top"{{!}}Voicemail Service

Dialplan Service

Config Service

Orchestration Service

Frontend Service

SIP Cluster Service

Registrar Service

Agent State Service

Call State Service

SIP Proxy

Tenant Service

- TServer

- Configuration Server

- Universal Routing

- Stat Server

- OCS
{{!}} width="110" valign="top"{{!}}high

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

high

medium
{{!}}-
{{!}} width="133" valign="top"{{!}}'''PECA Portal (Hub)'''
{{!}} width="299" valign="top"{{!}}Static Web page per tenant. This page will be deployed in Azure’s CDN in regions where the tenant is deployed. 
{{!}} width="110" valign="top"{{!}}critical
{{!}}-
{{!}} width="133" valign="top"{{!}}'''WFM 3rd party Connector'''
{{!}} width="299" valign="top"{{!}}Aria Adapters
{{!}} width="110" valign="top"{{!}}high
{{!}}-
{{!}} width="133" valign="top"{{!}}'''Telemetry'''
{{!}} width="299" valign="top"{{!}}Telemetry Service
{{!}} width="110" valign="top"{{!}}high
{{!}}-
{{!}} width="133" valign="top"{{!}}'''BDS'''
{{!}} width="299" valign="top"{{!}}Generates usage billing data
{{!}} width="110" valign="top"{{!}}medium
{{!}}-
{{!}} width="133" valign="top"{{!}}'''Genesys Authentication Services'''
{{!}} width="299" valign="top"{{!}}Authentication Service (API)

Environment Service

Authentication UI
{{!}} width="110" valign="top"{{!}}critical

critical

critical
{{!}}}

'''Note to reviewers:''' Review the example. This is copied from [https://intranet.genesys.com/display/AZURE/Helm+Chart+Values Helm Chart Values] 
|Status=No
}}
}}

@@ Line 338: / Line 338: @@
 <nowiki>*</nowiki>''In private edition, the following functions are rearchitected into Tenant Service:''
-*''Tenant functions (T-Servers)''
+*''Tenant call control functions (T-Servers)''
 *''Configuration functions''
 *''Routing functions''

@@ Line 261: / Line 261: @@
 <span lang="EN-US">critical</span>
 {{!}}-
-{{!}} width="133" valign="top"{{!}}'''<span lang="EN-US">Voice Microservice</span>'''
+{{!}} width="133" valign="top"{{!}}'''<span lang="EN-US">Voice Microservices</span>'''
 {{!}} width="299" valign="top"{{!}}<span lang="EN-US">Voicemail  Service</span>
-<span lang="EN-US">Dialplan  Service</span>
+<span lang="EN-US">Dialplan Service</span>
-<span lang="EN-US">Config  Service</span>
+<span lang="EN-US">Config Service</span>
 <span lang="EN-US">Orchestration  Service</span>
@@ Line 274: / Line 274: @@
 <span lang="EN-US">SIP  Cluster Service</span>
-<span lang="EN-US">Registrar  Service</span>
+<span lang="EN-US">Registrar Service</span>
 <span lang="EN-US">Agent  State Service</span>
@@ Line 282: / Line 282: @@
 <span lang="EN-US">SIP  Proxy</span>
-<span lang="EN-US">Tenant  Service</span>
+<span lang="EN-US">Tenant Service<nowiki>*</nowiki></span>
 {{!}} width="110" valign="top"{{!}}<span lang="EN-US">high</span>
@@ Line 314: / Line 304: @@
 <span lang="EN-US">critical</span>
 {{!}}-
 {{!}} width="133" valign="top"{{!}}'''<span lang="EN-US">PECA Portal (Hub)</span>'''
@@ Line 356: / Line 336: @@
 |Status=No
 }}
 }}

@@ Line 121: / Line 121: @@
 {{!}} width="110" valign="top"{{!}}<span lang="EN-US">high</span>
 {{!}}-
-{{!}} width="133" valign="top"{{!}}'''<span lang="EN-US">Genesys Cloud Hybrid Integration</span>'''
+{{!}} width="133" valign="top"{{!}}'''<span lang="EN-US">Genesys Cloud CX Hybrid Integration</span>'''
 {{!}} width="299" valign="top"{{!}}<span lang="EN-US">Conversation  Provider</span>

@@ Line 117: / Line 117: @@
 <span lang="EN-US">critical</span>
 {{!}}-
-{{!}} width="133" valign="top"{{!}}'''<span lang="EN-US">Genesys Multicloud CXment Service (Callback and Mobile)</span>'''
+{{!}} width="133" valign="top"{{!}}'''<span lang="EN-US">Genesys Engagement Service (Callback and Mobile)</span>'''
 {{!}} width="299" valign="top"{{!}}<span lang="EN-US">Genesys  Engagement Service</span>
 {{!}} width="110" valign="top"{{!}}<span lang="EN-US">high</span>

@@ Line 1: / Line 1: @@
 {{Article
 |Standalone=No
-|DisplayName=Service priorities for Genesys Engage services
+|DisplayName=Service priorities for Genesys Multicloud CX services
-|Context=Learn about service priorities of Genesys Engage Services.
+|Context=Learn about service priorities of Genesys Multicloud CX Services.
 |ComingSoon=No
 |Section={{Section
 |alignment=Vertical
-|structuredtext=Genesys has assigned a service priority class for each Genesys Engage service based on the Kubernetes Pod Priority guidelines. The guideline states to use a value of one million for high priority pods and values of two billion and above for Kubernetes itself for cluster critical Pods like kube-proxy and core-dns. Genesys has designed the service priority values for each priority class such as ''Critical'', ''Medium'', and ''Low'', and categorized the services under different service priority classes based on their business function. For example, Voice services are given 'Critical' priority because they cannot handle long delays. You can override this value in your Helm charts before deployment.
+|structuredtext=Genesys has assigned a service priority class for each Genesys Multicloud CX service based on the Kubernetes Pod Priority guidelines. The guideline states to use a value of one million for high priority pods and values of two billion and above for Kubernetes itself for cluster critical Pods like kube-proxy and core-dns. Genesys has designed the service priority values for each priority class such as ''Critical'', ''Medium'', and ''Low'', and categorized the services under different service priority classes based on their business function. For example, Voice services are given 'Critical' priority because they cannot handle long delays. You can override this value in your Helm charts before deployment.
 Before overriding, remember that the Pods will be evicted from the node based on the service priority you set. Hence, it is essential to assign service priority based on your business requirements.
@@ Line 27: / Line 27: @@
 {{!}}<span lang="EN-US">Critical</span>
 {{!}}<span lang="EN-US">10,000,000</span>
-{{!}}<span lang="EN-US">Use this priority for Genesys Engage services that must '''not''' be evicted due to resource limitations and can evict all other lower priority services, when needed.</span>
+{{!}}<span lang="EN-US">Use this priority for Genesys Multicloud CX services that must '''not''' be evicted due to resource limitations and can evict all other lower priority services, when needed.</span>
 {{!}}-
 {{!}}<span lang="EN-US">High</span>
 {{!}}<span lang="EN-US">1,000,000</span>
-{{!}}<span lang="EN-US">Use this priority for Genesys Engage services that might be evicted by critical services but will evict lower priority services, when needed.</span>
+{{!}}<span lang="EN-US">Use this priority for Genesys Multicloud CX services that might be evicted by critical services but will evict lower priority services, when needed.</span>
 {{!}}-
 {{!}}<span lang="EN-US">Medium</span>
 {{!}}<span lang="EN-US">100,000</span>
-{{!}}<span lang="EN-US">Use this priority for Genesys Engage services that might be evicted by critical or high priority services but will only evict lower or default priority services, when needed.</span>
+{{!}}<span lang="EN-US">Use this priority for Genesys Multicloud CX services that might be evicted by critical or high priority services but will only evict lower or default priority services, when needed.</span>
 {{!}}-
 {{!}}<span lang="EN-US"><none></span>
 {{!}}<span lang="EN-US">0</span>
-{{!}}<span lang="EN-US">Use this priority for Genesys Engage services that can be evicted for more than 24 hours, if needed.</span>
+{{!}}<span lang="EN-US">Use this priority for Genesys Multicloud CX services that can be evicted for more than 24 hours, if needed.</span>
 {{!}}}
-The following table illustrates the recommended priority for each Genesys Engage service at a granular level.
+The following table illustrates the recommended priority for each Genesys Multicloud CX service at a granular level.
 {{{!}} class="wikitable" border="1" cellspacing="0" cellpadding="0"
 {{!}} width="133" valign="top"{{!}}'''<span lang="EN-US">Services Groups</span>'''
@@ Line 117: / Line 117: @@
 <span lang="EN-US">critical</span>
 {{!}}-
-{{!}} width="133" valign="top"{{!}}'''<span lang="EN-US">Genesys Engagement Service (Callback and Mobile)</span>'''
+{{!}} width="133" valign="top"{{!}}'''<span lang="EN-US">Genesys Multicloud CXment Service (Callback and Mobile)</span>'''
 {{!}} width="299" valign="top"{{!}}<span lang="EN-US">Genesys  Engagement Service</span>
 {{!}} width="110" valign="top"{{!}}<span lang="EN-US">high</span>

@@ Line 10: / Line 10: @@
 Before overriding, remember that the Pods will be evicted from the node based on the service priority you set. Hence, it is essential to assign service priority based on your business requirements.
-====Sample Service Priority configuration====
+====Overriding Service Priority====
 If you want to override the service priority for a service,
-*Define an optional '''priorityClassName''' variable in the '''values.yaml''' file of the corresponding service.
+*In the '''values.yaml''' file of the corresponding service, locate the '''priorityClassName''' optional variable.
-*Assign the service priority value such as '''genesysengage-critical-priority, genesysengage-medium-priority,''' or '''genesysengage-low-priority'''. Your values.yaml configuration looks like the following:
+*Override the default service priority value by assigning the required value. You can assign any one of the following values—'''genesysengage-critical-priority, genesysengage-medium-priority,''' or '''genesysengage-low-priority'''. After overriding, your '''values.yaml''' configuration looks like the following:
 <code>priorityClassName: genesysengage-medium-priority</code>
 The following table illustrates the Genesys chosen priority class and its priority value.