PEC-REP/Current/GIMPEGuide/PlanningGCA - Revision history

WikiSysop at 16:46, September 2, 2022

2022-09-02T16:46:40Z

WikiSysop at 16:16, September 2, 2022

2022-09-02T16:16:46Z

WikiSysop at 06:32, August 12, 2022

2022-08-12T06:32:02Z

WikiSysop at 19:53, March 30, 2022

2022-03-30T19:53:32Z

Jdruker: Published

2022-02-11T20:49:10Z

Published

Jdruker: Republishing to refresh third-party data

2022-02-07T16:12:57Z

Republishing to refresh third-party data

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

2021-11-09T21:12:43Z

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:28:27Z

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

Jose.druker@genesys.com: Published

2021-07-01T03:01:53Z

Published

New page

{{PEPrerequisites
|DisplayName=Before you begin GCA deployment
|Context=Find out what to do before deploying GIM Config Adapter (GCA).
|LimitationsStatus=No
|LimitationsText=*ARO uses OCS and S3. The S3 bucket is used to share data among the gsp, gca, and gim namespaces.
*Instructions are provided for a single-tenant deployment.

<br />
|HelmStatus=No
|HelmText=GIM Config Adapter (GCA) and GCA monitoring are the only services that run in the GCA Docker container. The Helm charts included with the GCA release provision GCA and any Kubernetes infrastructure necessary for GCA to run.

See {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GIMHelm}} for the Helm chart versions you must download for your release.

For information about how to download the Helm charts, see {{SuiteLevelLink|helmchart}}.
|ThirdPartyStatus=No
|ThirdPartyText=For information about setting up your Genesys Engage cloud private edition platform, see {{SuiteLevelLink|softwarereq}}.

The following table lists the third-party prerequisites for GCA.
|SectionThirdPartyItem={{SectionThirdPartyItem
|ThirdPartyItem=1a407778-58fe-4acd-8ca7-5af8eac31283
}}{{SectionThirdPartyItem
|ThirdPartyItem=2f69518e-33af-4c0f-adcc-a98e5427e5e0
}}{{SectionThirdPartyItem
|ThirdPartyItem=2afd763e-337c-47eb-8428-3bafcc89dbca
}}{{SectionThirdPartyItem
|ThirdPartyItem=0d238336-2626-4954-8be3-2f1e16fdd0ce
}}{{SectionThirdPartyItem
|ThirdPartyItem=3aee73ed-68e0-4c70-8693-2421c68b86cd
}}
|StorageStatus=No
|NetworkStatus=No
|NetworkText={{Notices|Notice=PEComingSoon}}
|BrowserStatus=No
|DependenciesStatus=No
|DependenciesText=The following Genesys Engage microservices must be deployed before you deploy GCA:

*{{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=TenantPEGuide|display text=Voice Tenant Service}}, which enables GCA to access the Configuration Server database
*GIM Stream Processor (GSP)

For detailed information about the correct order of services deployment, see {{SuiteLevelLink|deployorder}}.
|GDPRStatus=No
|GDPRText=Not applicable. GCA does not store information beyond an ephemeral snapshot.
|PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167
}}

@@ Line 5: / Line 5: @@
 |LimitationsStatus=No
 |LimitationsText=Instructions are provided for a single-tenant deployment.
 |HelmStatus=No
-|HelmText=To configure and deploy the GIM Config Adapter (GCA), you must obtain the Helm charts included with the GCA release. These Helm charts provision GCA plus any Kubernetes infrastructure needed for GCA to run.
+|HelmText=GIM Config Adapter (GCA) and GCA monitoring are the only services that run in the GCA Docker container. The Helm charts included with the GCA release provision GCA and any Kubernetes infrastructure necessary for GCA to run.
-GCA and GCA monitoring are the only services that run in the GCA container.
+See {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GIMHelm}} for the Helm chart versions you must download for your release.
-For information on downloading from the Genesys JFrog image repository, see {{SuiteLevelLink|helmchart}}. To find the correct Helm chart version for your release, see {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GIMHelm}}.
+For information about how to download the Helm charts, see {{SuiteLevelLink|helmchart}}.
 |ThirdPartyStatus=No
 |ThirdPartyText=For information about setting up your Genesys Multicloud CX private edition platform, see {{SuiteLevelLink|softwarereq}}.
@@ Line 17: / Line 19: @@
 |SectionThirdPartyItem={{SectionThirdPartyItem
 |ThirdPartyItem=2f69518e-33af-4c0f-adcc-a98e5427e5e0
-|Notes=GCA publishes configuration data to the <code>gca-cfg</code> topic, which GSP consumes. The topic must exist in your Kafka configuration.
+|Notes=GCA publishes configuration data to the <tt>gca-cfg</tt> topic, which GSP consumes. The topic must exist in your Kafka configuration.
 <!--<br/>{{Editgrn_open}}<font color=red>'''Writer's note: Borys/Alexey,''' in GSP the topic name is customizable (in the values.yaml), but I don't see where customers could customize it in the GCA values.yaml. ??</font>{{Editgrn_close}}-->
 }}{{SectionThirdPartyItem
@@ Line 29: / Line 31: @@
 }}
 |StorageStatus=No
-|StorageText=GCA uses S3-compatible storage to store the GCA snapshot during processing. You must provision this S3-compatible storage in your environment. By default, GCA is configured to use Azure Blob storage, but you can also use S3-compatible storage provided by other cloud platforms.
+|StorageText=GCA uses object storage to store the GCA snapshot during processing. Like GSP, GCA supports using S3-compatible storage provided by OpenShift and Google Cloud Platform (GCP),<!-- By default, GCA expects to use Azure Blob Storage, but you can also use S3-compatible bucket storage provided by other cloud platforms. <font color=red>'''Writer's note:''' Confirm the default setup. All the storage parameters in the values.yaml are empty.</font> If you use S3-compatible storage for GSP,--> and Genesys expects you to use the same storage account for GSP and GCA. If you want to use separate storage for GCA, follow the {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=ConfigureGSP|anchor=Storage|display text=Configure S3-compatible storage}} instructions for GSP to create similar S3-compatible storage for GCA.
 |NetworkStatus=No
 |NetworkText=No special network requirements.

@@ Line 5: / Line 5: @@
 |LimitationsStatus=No
 |LimitationsText=Instructions are provided for a single-tenant deployment.
 |HelmStatus=No
-|HelmText=GIM Config Adapter (GCA) and GCA monitoring are the only services that run in the GCA Docker container. The Helm charts included with the GCA release provision GCA and any Kubernetes infrastructure necessary for GCA to run.
+|HelmText=To configure and deploy the GIM Config Adapter (GCA), you must obtain the Helm charts included with the GCA release. These Helm charts provision GCA plus any Kubernetes infrastructure needed for GCA to run.
-See {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GIMHelm}} for the Helm chart versions you must download for your release.
+GCA and GCA monitoring are the only services that run in the GCA container.
-For information about how to download the Helm charts, see {{SuiteLevelLink|helmchart}}.
+For information on downloading from the Genesys JFrog image repository, see {{SuiteLevelLink|helmchart}}. To find the correct Helm chart version for your release, see {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GIMHelm}}.
 |ThirdPartyStatus=No
 |ThirdPartyText=For information about setting up your Genesys Multicloud CX private edition platform, see {{SuiteLevelLink|softwarereq}}.
@@ Line 19: / Line 17: @@
 |SectionThirdPartyItem={{SectionThirdPartyItem
 |ThirdPartyItem=2f69518e-33af-4c0f-adcc-a98e5427e5e0
-|Notes=GCA publishes configuration data to the <tt>gca-cfg</tt> topic, which GSP consumes. The topic must exist in your Kafka configuration.
+|Notes=GCA publishes configuration data to the <code>gca-cfg</code> topic, which GSP consumes. The topic must exist in your Kafka configuration.
 <!--<br/>{{Editgrn_open}}<font color=red>'''Writer's note: Borys/Alexey,''' in GSP the topic name is customizable (in the values.yaml), but I don't see where customers could customize it in the GCA values.yaml. ??</font>{{Editgrn_close}}-->
 }}{{SectionThirdPartyItem
@@ Line 31: / Line 29: @@
 }}
 |StorageStatus=No
-|StorageText=GCA uses object storage to store the GCA snapshot during processing. Like GSP, GCA supports using S3-compatible storage provided by OpenShift and Google Cloud Platform (GCP),<!-- By default, GCA expects to use Azure Blob Storage, but you can also use S3-compatible bucket storage provided by other cloud platforms. <font color=red>'''Writer's note:''' Confirm the default setup. All the storage parameters in the values.yaml are empty.</font> If you use S3-compatible storage for GSP,--> and Genesys expects you to use the same storage account for GSP and GCA. If you want to use separate storage for GCA, follow the {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=ConfigureGSP|anchor=Storage|display text=Configure S3-compatible storage}} instructions for GSP to create similar S3-compatible storage for GCA.
+|StorageText=GCA uses S3-compatible storage to store the GCA snapshot during processing. You must provision this S3-compatible storage in your environment. By default, GCA is configured to use Azure Blob storage, but you can also use S3-compatible storage provided by other cloud platforms.
 |NetworkStatus=No
 |NetworkText=No special network requirements.

@@ Line 31: / Line 31: @@
 }}
 |StorageStatus=No
-|StorageText=GCA uses object storage to store the GCA snapshot during processing. Like GSP, GCA supports using S3-compatible storage provided by OpenShift and Google Cloud Platform (GCP),<!-- By default, GCA expects to use Azure Blob Storage, but you can also use S3-compatible bucket storage provided by other cloud platforms. <font color=red>'''Writer's note:''' Confirm the default setup. All the storage parameters in the values.yaml are empty.</font> If you use S3-compatible storage for GSP,--> and Genesys expects you to use the same storage account for GSP and GCA. If you want to use separate storage for GCA, follow the {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=ConfigureGSP|anchor=S3|display text=Create object storage}} instructions for GSP to create similar S3-compatible storage for GCA.
+|StorageText=GCA uses object storage to store the GCA snapshot during processing. Like GSP, GCA supports using S3-compatible storage provided by OpenShift and Google Cloud Platform (GCP),<!-- By default, GCA expects to use Azure Blob Storage, but you can also use S3-compatible bucket storage provided by other cloud platforms. <font color=red>'''Writer's note:''' Confirm the default setup. All the storage parameters in the values.yaml are empty.</font> If you use S3-compatible storage for GSP,--> and Genesys expects you to use the same storage account for GSP and GCA. If you want to use separate storage for GCA, follow the {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=ConfigureGSP|anchor=Storage|display text=Configure S3-compatible storage}} instructions for GSP to create similar S3-compatible storage for GCA.
 |NetworkStatus=No
 |NetworkText=No special network requirements.
@@ Line 38: / Line 38: @@
 |DependenciesText=*{{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=TenantPEGuide|display text=Voice Tenant Service}}, which enables GCA to access the Configuration Server database. You must deploy the Voice Tenant Service before you deploy GCA.
 **Ensure that an appropriate user account is available for GCA to use to access the Configuration Database. The GCA user account requires at least read permissions.
-**You must also have your Tenant ID information available. <!--{{Editgrn_open}}<font color=red>'''Writer's note:''' Where can they find this info?</font>{{Editgrn_close}}-->
+**You must also have your Tenant ID information available.<!--{{Editgrn_open}}<font color=red>'''Writer's note:''' Where can they find this info?</font>{{Editgrn_close}}-->
 *There are no strict dependencies between the Genesys Info Mart services, but the logic of your particular pipeline might require Genesys Info Mart services to be deployed in a particular order. Depending on the order of deployment, there might be temporary data inconsistencies until all the Genesys Info Mart services are operational. For example, GSP looks for the GCA snapshot when it starts; if GCA has not yet been deployed, GSP will encounter unknown configuration objects and resources until the snapshot becomes available.

@@ Line 2: / Line 2: @@
 |DisplayName=Before you begin GCA deployment
 |Context=Find out what to do before deploying GIM Config Adapter (GCA).
 |LimitationsStatus=No
 |LimitationsText=*ARO uses OCS and S3. The S3 bucket is used to share data among the gsp, gca, and gim namespaces.

@@ Line 33: / Line 33: @@
 |BrowserStatus=No
 |DependenciesStatus=No
-|DependenciesText=The following Genesys Engage microservices must be deployed before you deploy GCA:
+|DependenciesText=The following Genesys Multicloud CX microservices must be deployed before you deploy GCA:
 *{{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=TenantPEGuide|display text=Voice Tenant Service}}, which enables GCA to access the Configuration Server database