SEMANTIC QUERY LAYER

RELEASE NOTES – R25

Version 1.0

Document History
Version Date Author / Changed By Change Description

1.0 22-07-2025 Temenos Updated 25.0.1 version details

Comments:
Contents
1. Introduction............................................................................................................................................ 4
2. Prerequisites & General Considerations................................................................................................ 4
3. Pre-Installation Steps............................................................................................................................. 4
3.1 Pod Status before the Upgrade Process............................................................................................4
3.2 Scaling down the Pods before the Upgrade Process.........................................................................4
4. Installation Steps.................................................................................................................................... 5
4.1 Build the Docker Images.................................................................................................................... 5
4.1.1 SQL image build......................................................................................................................... 5
4.1.2 ods-api image build.................................................................................................................... 5
4.2 Docker images after the build............................................................................................................ 6
4.3 Tag the Images.................................................................................................................................. 6
4.4 Login into container registry............................................................................................................... 7
4.5 Push the Images................................................................................................................................ 7
4.6 Helm Upgrade Process...................................................................................................................... 8
4.6.1 Note Down Existing Values........................................................................................................ 8
4.6.2 Setting up values yaml............................................................................................................... 9
4.6.3 Copy Helm charts to Build VM................................................................................................. 10
4.6.4 Helm upgrade........................................................................................................................... 10
5. Post-Installation Steps......................................................................................................................... 11
5.1 Scaling Up of Pods after the Upgrade Process................................................................................11
5.2 Verification of Pods post Upgrade Process......................................................................................11
6. Verification Steps................................................................................................................................. 12
6.1 Verification of pods........................................................................................................................... 12
7. Release Notes..................................................................................................................................... 13
7.0 SemanticQueryLayer-25.0.1............................................................................................................ 13
7.0.1 New Features and User stories released in 25.0.1:.................................................................13
7.0.2 Maintenance Defects Released in 25.0.1:................................................................................13
7.0.3 Internal Defect Released in 25.0.1:.......................................................................................... 13
7.0.4 Patch Details............................................................................................................................ 13
7.0.5 Build Details............................................................................................................................. 13
8. Appendix.............................................................................................................................................. 17
1. Introduction
This document explains on the standard upgrade process of SQL from one version to other version in
the same Release. Release Notes section in the document provides the information about each version
that got delivered in the Release.

2. Prerequisites & General Considerations

Base version of SQL belongs to the respective release should have been installed in the target
environment.
Docker is required to build the images.
Helm is required to perform the installation.
Access to the environment / subscription is required for the installation.
SQL Pack should be received from the Temenos Distribution Team.

3. Pre-Installation Steps
3.0 Pod Status before the Upgrade Process
Get the SQL namespace
Execute the below command to check the status of the pods before the Upgrade Process.
kubectl get pods -n <SQL Namespace>
Here SQL Namespace is sql

3.1 Scaling down the Pods before the Upgrade Process

Execute the below command to get the deployment names under sql namespace
kubectl get deployments -n sql

Scale down all the pods by using the below command.

kubectl scale deployments --replicas=0 <deployment name> -n <Namespace Name>
Here, sql is the namespace and sqlportal, ods are the deployment names.
4. Installation Steps
4.0 Build the Docker Images
Set the BASE_REPO and BASE_TAG environment variables
BASE_REPO=[Link]/temenos-baseimages-validated
BASE_TAG=dev

4.0.1 SQL image build

Open the Command Prompt from the following location
<SemanticQueryLayer-25.0.x>\sql-k8s\docker\sql_images\sql_portal\build_scripts
Execute the below command
For windows - [Link]
For Linux - [Link]

4.0.2 ods-api image build

Open the Command Prompt from the following location
<SemanticQueryLayer-25.0.x>\sql-k8s\docker\sql_images\ods-api\build_scripts
Execute the below command
For windows - [Link]
 For Linux - [Link]

4.1 Docker images after the build

New images are built which can be checked using docker images command.

4.2 Tag the Images

By default, the built images refer to the "latest" tag. Run the below command to tag the image to its respective
release or version.
docker tag <image repository name>:<tag> <registry name>/<image repository name>:<tag>

 Run the below command to tag an SQL portal image.

docker tag temenos/data/sql_portal:latest <registry name>/temenos/data/sql_portal:x.x.x

Example: docker tag temenos/data/sql_portal:latest

[Link]/temenos/data/sql_portal:24.0.2

 Run the below command to tag an ODS API image.

docker tag temenos/data/ods-api:latest <registry name>/temenos/data/ ods-api:x.x.x

Example: docker tag temenos/data/ods-api:latest [Link]/temenos/data/ods-api:24.0.2

docker images after tagging,

4.3 Login into container registry
Login to the container registry for pushing the images.

Command: az login

Command: az account set --subscription <SubscriptionId>

Command: az acr login --name <containername>/

4.4 Push the Images

Run the below command to push the images

docker push <image_repository_name>:<tag>

Run the below command to push the sql portal image.

docker push <registry name>/temenos/data/sql_portal:x.x.x.x

 `

Run the below command to push an ODS API image.

docker push <registry name>/temenos/data/ods-api:x.x.x.x

4.5 Helm Upgrade Process

4.5.1 Note Down Existing Values
Launch the cloud shell.
Note down the existing helm chart values before starting upgrade. Execute the below comment to get
the helm chart values,
helm get values <RELEASE NAME> -n <SQL Namespace> -a
Here RELEASE NAME is sql and SQL Namespace is sql.
4.5.2 Setting up values yaml
Go to the directory path “<SemanticQueryLayer-25.0.x>\sql-k8s\helm\sql_chart\” and edit the helm
charts to include the details.

Add the image registry details such as the registry name from where the image has to be pulled and its
credentials.
 Add the image tag to match the tag with which the images have been pushed to container registry.

Configure the other helm chart values by referring the existing values noted.

[Link]:
Edit “[Link]” file for On-Prem docker installations.
Configure the other helm chart values by referring the existing values noted.
[Link]:
This file configuration is required only for SQL installations done Azure environment.
Configure the azure related details (ingress) by referring the existing values noted.
[Link]:
This file configuration is required only for SQL installations done in OpenShift environment.
Configure the OpenShift related details (routes) by referring the existing values noted.
[Link]:
This file configuration is required only for SQL installations done in AWS environment.
Configure the details by referring the existing values noted.

4.5.3 Copy Helm charts to Build VM

Once the yaml file configurations are done, zip the helm folder and copy it into the build VM

4.5.4 Helm upgrade

Unzip the [Link] file inside the Build VM
 Execute the below command from path \helm\sql_chart\ to perform helm upgrade
helm upgrade <chart name> --namespace <SQL Namespace> <chart location>
On-Perm:
Execute the below command for On-Prem environment,
helm upgrade sql . --namespace sql -f [Link]

Note: Don’t use helm uninstall and install command

Azure:
Execute the below command for Azure environment,
helm upgrade sql . --namespace sql -f [Link]
OpenShift:
Execute the below command for OpenShift environment,
helm upgrade sql . --namespace sql -f [Link]
AWS:
Execute the below command for AWS environment,
helm upgrade sql . --namespace sql -f [Link]

5. Post-Installation Steps
5.0 Scaling Up of Pods after the Upgrade Process
Scale up all the pods by using the below command.
kubectl scale deployments --replicas=1 <deployment name> -n <SQL Namespace>
Here, sql is the namespace and sqlportal, ods are the deployment names.

5.1 Verification of Pods post Upgrade Process

New pods will be created automatically after helm upgrade. It can be checked using
kubectl get pods -n sql
6. Verification Steps
6.0 Verification of pods
Launch the below URLs to confirm the successful deployment of pods,
 SQL Portal
URL - [Link] name>/swagger-ui/[Link]#
where, <sql_ip/dns name> - sql portal pod Ip or dns name

 ODS
URL - [Link] name>/ods-api-container/api/v1.0.0/meta/apis
where, <ods_ip/dns name> - ods pod Ip or dns name
7. Release Notes
7.0 SemanticQueryLayer-25.0.1
7.0.1 New Features and User stories released in 25.0.1:

7.0.2 Maintenance Defects Released in 25.0.1:

 DF-24718 - TSR-1048708 SQL properties files are not being included in the DSF
package
 DF-24719 - TSR-1052431 Helm charts not having resources configurations of SQL
(Semantic Query Layer) and ODS API pods.
 DF-24510 - TSR-1016213 TDH APIs Error response when processing multiple
requests.

7.0.3 Internal Defect Released in 25.0.1:

NA

7.0.4 Patch Details

 Fix done in [Link]

 Fix done in helm charts

7.0.5 Build Details

 Docker Image Build – sql_portal

Run “[Link]” or “[Link]” from the following path <SemanticQueryLayer-25.0.x>\sql-k8s\

docker\sql_images\sql_portal\build_scripts
 Docker Image Build – ods-api

Run “[Link]” or “[Link]” from the following path <SemanticQueryLayer-25.0.x>\sql-k8s\

docker\sql_images\ods-api\build_scripts
 Helm Updates

 Helm upgrade is required

 Special Instructions

 Helm charts changes done for the configuration of resources details.

Below properties are added and values are defaulted. Change it if required.
requests:
cpu: 0.5
memory: 4G
limits:
cpu: 1
 memory: 6G

 As a part of this, the resource requests and limits are applied to the sql portal, ods and
ads pods

 Special Instructions

In case of upgraded environment, follow the below steps to correct the properties files in GCMS for
creating the package with properties files.

Get the properties files content from GCMS and repost with id=<name>

 [Link]

POST to GCMS with id="[Link]"

 [Link]

POST to GCMS with id="[Link]"

 [Link]
POST to GCMS with id="[Link]"

Properties files are listed in WB

8. Appendix