BUG-898031 SRS Readme clarification on embedded ES #852
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
From: Peterson, John <John.Peterson@pega.com> Sent: Friday, November 15, 2024 4:10 PM To: Kowalska, Kinga <Kinga.Kowalska@pega.com> Cc: Casavant, Dave <Dave.Casavant@pega.com>; Chikkam, Venkata Satya Gopal <VenkataSatyaGopal.Chikkam@in.pega.com>; Talbot, Adam <Adam.Talbot@pega.com>; Kumar, Saurabh <Saurabh.Kumar2@in.pega.com> Subject: CMC Documentation clarification for SRS & Databases. Hi Kinga, Yes, I agree with your proposed changes. Thanks! John From: Kowalska, Kinga <Kinga.Kowalska@pega.com> Sent: Thursday, November 14, 2024 8:15 AM To: Peterson, John <John.Peterson@pega.com> Cc: Casavant, Dave <Dave.Casavant@pega.com>; Chikkam, Venkata Satya Gopal <VenkataSatyaGopal.Chikkam@in.pega.com>; Talbot, Adam <Adam.Talbot@pega.com>; Kumar, Saurabh <Saurabh.Kumar2@in.pega.com> Subject: RE: ExtMsg: Pega Containerized Deployment on OpenShift Hi John, For Elasticsearch: In Search and Reporting Service Helm chart I would replace the following introduction paragraph: The Pega Search and Reporting Service or SRS backing service can replace the embedded search feature of Pega Infinity Platform. To use it in your deployment, you provision and deploy it independently as an external service which provides search and reporting capabilities with a Pega Infinity environment. With: The Pega Search and Reporting Service or SRS backing service provides the search and reporting capabilities of Pega Infinity Platform. To use it in your deployment, you provision and deploy it independently as an external service in a Pega Infinity environment. If we want to stress the message, I can add a note specifically saying “Embedded Elasticsearch service is not supported for containerized deployments.”, but this will become redundant once we cycle out of Pega Platform versions that support embedded search. For databases: In JDBC Configuration I can add the following sentence with a link: Use the jdbc section of the values file to specify how to connect to the Pega database. Pega must be installed to this database before deploying on Kubernetes. For more information on supported databases and jdbc driver versions, see the Platform Support Guide. Does this work for you? Best regards, Kinga Kowalska | Principal Technical Writer | Pegasystems Inc. Email: kinga.kowalska@pega.com | pega.com From: Peterson, John <John.Peterson@pega.com> Sent: Friday, November 1, 2024 3:28 PM To: Kowalska, Kinga <Kinga.Kowalska@pega.com> Cc: Casavant, Dave <Dave.Casavant@pega.com>; Chikkam, Venkata Satya Gopal <VenkataSatyaGopal.Chikkam@in.pega.com>; Talbot, Adam <Adam.Talbot@pega.com>; Kumar, Saurabh <Saurabh.Kumar2@in.pega.com> Subject: RE: ExtMsg: Pega Containerized Deployment on OpenShift Hi Kinga, We’ve never supported running embedded search on K8S deployments, so I think the language needs to be updated, is this something you can assist with? From a database support perspective, can you also update the K8S documentation to refer the Platform Support Guide? Thanks, John From: Peterson, John Sent: Friday, November 1, 2024 10:03 AM To: Panigrahy, Chinmaya <Chinmay.Panigrahy@in.pega.com>; Oleti Venkata, Nagendra <Nagendra.OletiVenkata@in.pega.com>; Thota, Srinivas Maheedhar <Srinivas.Maheedhar@in.pega.com>; Chikkam, Venkata Satya Gopal <VenkataSatyaGopal.Chikkam@in.pega.com> Subject: RE: ExtMsg: Pega Containerized Deployment on OpenShift Hi Chinmaya, Usage of existing on-premise DB : We have existing oracle database on-premise, Can we use this existing database and schemas with the containerized deployment on OpenShift ? Yes. https://github.com/pegasystems/pega-helm-charts/tree/master/charts/pega#url-and-driver-class Usage of embedded Kafka on OpenShift : As we are doing POC on 23.1.2 version of Pega , can we use embedded kafka & elastic search on OpenShift ? Embedded Kafka : Yes, but it is not recommended. https://github.com/pegasystems/pega-helm-charts/blob/1936bcfcbd0257fc047dc4390a4764a2dad6a626/charts/pega/EmbeddedStream.md#embedded-stream-with-latest-helm-chart-version Embedded Search : No. https://github.com/pegasystems/pega-helm-charts/tree/1936bcfcbd0257fc047dc4390a4764a2dad6a626/charts/backingservices/charts/srs#search-and-reporting-service-helm-chart Thanks, John
petejo
approved these changes
Nov 18, 2024
pega-talba
approved these changes
Nov 18, 2024
bhowd1
approved these changes
Nov 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From: Peterson, John John.Peterson@pega.com
Sent: Friday, November 15, 2024 4:10 PM
To: Kowalska, Kinga Kinga.Kowalska@pega.com
Cc: Casavant, Dave Dave.Casavant@pega.com; Chikkam, Venkata Satya Gopal VenkataSatyaGopal.Chikkam@in.pega.com; Talbot, Adam Adam.Talbot@pega.com; Kumar, Saurabh Saurabh.Kumar2@in.pega.com
Subject: CMC Documentation clarification for SRS & Databases.
Hi Kinga,
Yes, I agree with your proposed changes.
Thanks!
John
From: Kowalska, Kinga Kinga.Kowalska@pega.com
Sent: Thursday, November 14, 2024 8:15 AM
To: Peterson, John John.Peterson@pega.com
Cc: Casavant, Dave Dave.Casavant@pega.com; Chikkam, Venkata Satya Gopal VenkataSatyaGopal.Chikkam@in.pega.com; Talbot, Adam Adam.Talbot@pega.com; Kumar, Saurabh Saurabh.Kumar2@in.pega.com
Subject: RE: ExtMsg: Pega Containerized Deployment on OpenShift
Hi John,
For Elasticsearch:
In Search and Reporting Service Helm chart I would replace the following introduction paragraph:
The Pega Search and Reporting Service or SRS backing service can replace the embedded search feature of Pega Infinity Platform. To use it in your deployment, you provision and deploy it independently as an external service which provides search and reporting capabilities with a Pega Infinity environment.
With:
The Pega Search and Reporting Service or SRS backing service provides the search and reporting capabilities of Pega Infinity Platform. To use it in your deployment, you provision and deploy it independently as an external service in a Pega Infinity environment.
If we want to stress the message, I can add a note specifically saying “Embedded Elasticsearch service is not supported for containerized deployments.”, but this will become redundant once we cycle out of Pega Platform versions that support embedded search.
For databases:
In JDBC Configuration I can add the following sentence with a link:
Use the jdbc section of the values file to specify how to connect to the Pega database. Pega must be installed to this database before deploying on Kubernetes. For more information on supported databases and jdbc driver versions, see the Platform Support Guide.
Does this work for you?
Best regards,
Kinga Kowalska | Principal Technical Writer | Pegasystems Inc.
Email: kinga.kowalska@pega.com | pega.com
From: Peterson, John John.Peterson@pega.com
Sent: Friday, November 1, 2024 3:28 PM
To: Kowalska, Kinga Kinga.Kowalska@pega.com
Cc: Casavant, Dave Dave.Casavant@pega.com; Chikkam, Venkata Satya Gopal VenkataSatyaGopal.Chikkam@in.pega.com; Talbot, Adam Adam.Talbot@pega.com; Kumar, Saurabh Saurabh.Kumar2@in.pega.com
Subject: RE: ExtMsg: Pega Containerized Deployment on OpenShift
Hi Kinga,
We’ve never supported running embedded search on K8S deployments, so I think the language needs to be updated, is this something you can assist with?
From a database support perspective, can you also update the K8S documentation to refer the Platform Support Guide?
Thanks,
John
From: Peterson, John
Sent: Friday, November 1, 2024 10:03 AM
To: Panigrahy, Chinmaya Chinmay.Panigrahy@in.pega.com; Oleti Venkata, Nagendra Nagendra.OletiVenkata@in.pega.com; Thota, Srinivas Maheedhar Srinivas.Maheedhar@in.pega.com; Chikkam, Venkata Satya Gopal VenkataSatyaGopal.Chikkam@in.pega.com
Subject: RE: ExtMsg: Pega Containerized Deployment on OpenShift
Hi Chinmaya,
Usage of existing on-premise DB : We have existing oracle database on-premise, Can we use this existing database and schemas with the containerized deployment on OpenShift ?
Yes. https://github.com/pegasystems/pega-helm-charts/tree/master/charts/pega#url-and-driver-class
Usage of embedded Kafka on OpenShift : As we are doing POC on 23.1.2 version of Pega , can we use embedded kafka & elastic search on OpenShift ?
Embedded Kafka : Yes, but it is not recommended. https://github.com/pegasystems/pega-helm-charts/blob/1936bcfcbd0257fc047dc4390a4764a2dad6a626/charts/pega/EmbeddedStream.md#embedded-stream-with-latest-helm-chart-version
Embedded Search : No. https://github.com/pegasystems/pega-helm-charts/tree/1936bcfcbd0257fc047dc4390a4764a2dad6a626/charts/backingservices/charts/srs#search-and-reporting-service-helm-chart
Thanks,
John