Release - 6.1.0 (latest)

Hot-fix 6.1.0 (08-05-2024)

1. Image URL is not getting generated when QR code is searched - KN-1071

Release Tags

Component	Service to be Build	Tag	Deploy Job	Deployment Tag	Comment
Schema upload	NA	NA	Deploy/Kubernetes/UploadSchema	release-6.1.0_RC2
Knowledge-platform	Build/Core/Content	release-6.1.0_RC2	Deploy/Kubernetes/Content	release-5.6.0-knowlg_RC1	Deploy Tag is given for reference only. Please do not use directly for deployment.

Configuration/Environment variable changes:

Variables Added in Content-Service:

Variable Name	Description	Default Value
cloud_storage_dial_container	Storage container name to store dial codes	dial
dialcode_image.keyspace	Keyspace name to store dial code images details in Cassandra	dialcodes

6.1.0 (29-04-2024)

Discussion thread: https://github.com/orgs/Sunbird-Knowlg/discussions/190

Release timeline:

	Start date	End date
Planning phase	12-Feb, 2024	23-Feb, 2024
Sprint 1	26-Feb, 2024	15-Mar, 2024
Sprint 2	18-Mar, 2024	5-Apr, 2024
PPV	8-Apr, 2024	19-Apr, 2024
Prod	22-Apr, 2024

6.1.0 total scope: Link

Document Release Version

Project	Release Version	Date
Sunbird Knowlg	R6.1.0

Important note to the adopters:

As part of this release, we have made the below changes, which are important to know everyone.

We have upgraded Elasticsearch upgrade 6.8.22 to 7.17.13 — KN-976

Elasticsearch Upgrade Release Notes: 6.8.22 to 7.17.13

Upgrade Overview:

This release involves upgrading Elasticsearch from version 6.8.22 to version 7.17.13. The upgrade brings significant enhancements, bug fixes, and potential breaking changes that administrators and developers need to be aware of.

Upgrade Steps:

1. Preparation:

   • Ensure compatibility with Java 11, as Elasticsearch 7.17.13 requires this version.

2. Backup:

   • Before proceeding with the upgrade, ensure all data is backed up to prevent any loss during the migration process.

   • Please Click here for Backup & Restore In Local & Azure documentation

3. Upgrade Process:

   • Follow the Elasticsearch upgrade documentation for detailed instructions on upgrading from version 6.8.22 to 7.17.13.

   • Please Click Here for upgrading ES from 6.8.22 to 7.17.13 documentation.

Once you have upgraded to Elasticsearch 7.17.13, please consider using the below release tags for API services and Flink Jobs deployment.

Following are the Planned Tickets of R 6.1.0

New Features:

None

Enhancements / Technical tasks:

S.no	JIRA ID	Description
1	KN-976	Elasticsearch upgrade 6.8.22 to 7.17.13
2	KN-982	Sunbird Video Player - Angular version upgrade 15 to 17
3	KN-983	Sunbird PDF Player - Angular version upgrade 15 to 17
4	KN-979	Angular version update for Player SDK from 13 to 17
5	KN-1068	Sunbird Collection editor documentation changes
6	KN-879	DIAL code APIs Move from Knowlg MW to Content Service

Release Tags:

Upgrade Knowlg From 6.0.0 to 6.1.0

API Services:

Component	Service to be Build	Tag	Deploy Job	Deployment Tag	Comment
Schema upload	NA	NA	Deploy/Kubernetes/UploadSchema	release-6.1.0_RC1
Knowledge-platform	Build/Core/Content	release-6.1.0_RC1	Deploy/Kubernetes/Content	release-5.6.0-knowlg_RC1	Deploy Tag is given for reference only. Please do not use directly for deployment.
	Build/Core/Taxonomy	release-6.1.0_RC1	Deploy/Kubernetes/Taxonomy	release-5.6.0-knowlg_RC1	Deploy Tag is given for reference only. Please do not use directly for deployment.
	Build/Core/search	release-6.1.0_RC1	Deploy/Kubernetes/Search		Deploy Tag is given for reference only. Please do not use directly for deployment.
dial-service	Build/Core/Dial	release-6.1.0_RC1	Deploy/Kubernetes/Dial	release-5.6.0-knowlg_RC1	Deploy Tag is given for reference only. Please do not use directly for deployment.
Knowledge-platform-jobs	Build/KnowledgePlatform/FlinkJobs	release-6.1.0_RC1	Deploy/KnowledgePlatform/FlinkJobs	release-5.7.0_RC4	Jobs to be deployed: Search-indexer transaction-event-processor asset-enrichment Content-publish post-publish-processor qrcode-image-generator video-stream-generator

Sunbird player SDK:

Angular version - 13

Install: npm i @project-sunbird/sunbird-player-sdk-v9@6.0.2

https://www.npmjs.com/package/@project-sunbird/sunbird-player-sdk-v9/v/6.0.2

Angular version - 14

Install: npm i @project-sunbird/sunbird-player-sdk-v9@6.0.3

https://www.npmjs.com/package/@project-sunbird/sunbird-player-sdk-v9/v/6.0.3

Angular version - 15

Install: npm i @project-sunbird/sunbird-player-sdk-v9@6.0.4

https://www.npmjs.com/package/@project-sunbird/sunbird-player-sdk-v9/v/6.0.4

Angular version - 16

Install: npm i @project-sunbird/sunbird-player-sdk-v9@6.0.5

https://www.npmjs.com/package/@project-sunbird/sunbird-player-sdk-v9/v/6.0.5

Angular version - 17

Install: npm i @project-sunbird/sunbird-player-sdk-v9@6.0.7

https://www.npmjs.com/package/@project-sunbird/sunbird-player-sdk-v9/v/6.0.7

Sunbird PDF Player:

Angular version - 16

Install: npm i @project-sunbird/sunbird-pdf-player-v9@6.1.0

https://www.npmjs.com/package/@project-sunbird/sunbird-pdf-player-v9/v/6.1.0

Angular version - 17

Install: npm i @project-sunbird/sunbird-pdf-player-v9@6.1.1

https://www.npmjs.com/package/@project-sunbird/sunbird-pdf-player-v9/v/6.1.1

Sunbird Video Player:

Angular Version - 16

Install: npm i @project-sunbird/sunbird-video-player-v9@6.1.0

https://www.npmjs.com/package/@project-sunbird/sunbird-video-player-v9/v/6.1.0

Angular Version - 17

Install: npm i @project-sunbird/sunbird-video-player-v9@6.1.1

https://www.npmjs.com/package/@project-sunbird/sunbird-video-player-v9/v/6.1.1

Configuration/Environment variable changes:

In this release, we've transferred the following two APIs from Knowledge-MW-service to Content-Service. Because we moved these APIs to the Content-Service, the endpoints have been updated to ensure consistency with other content APIs.

S.No	Old API Endpoint	New API Endpoint
1	/v1/dialcode/reserve/:identifier	/content/v3/dialcode/reserve/:identifier (OR) /content/v4/dialcode/reserve/:identifier
2	/v1/dialcode/process/status	/content/v3/process/status/:processid (OR) /content/v4/process/status/:processid

Consequently, to reflect these changes, we'll need to update the upstream_url configuration in kong-api layer to reference Content-Service instead of Knowledge-MW-service.

Previous:

- name: reserveDialcode
  uris: "{{ dialcode_service_prefix }}/v1/reserve"
  upstream_url: "{{ knowledge_mw_service_url }}/v1/dialcode/reserve"
  
- name: qrCodeBatchProcessStatus
  uris: "{{ dialcode_service_prefix }}/v1/process/status"
  upstream_url: "{{ knowledge_mw_service_url }}/v1/dialcode/process/status"

Update to:

- name: reserveDialcode
  uris: "{{ dialcode_service_prefix }}/v1/reserve"
  upstream_url: "{{ content_service_url }}/content/v3/dialcode/reserve"
  
- name: qrCodeBatchProcessStatus
  uris: "{{ dialcode_service_prefix }}/v1/process/status"
  upstream_url: "{{ content_service_url }}/content/v3/process/status

Variables Added in Content-Service:

Variable Name	Description	Default Value
kafka.dial.request.topic	Input Kafka Topic Name	{{ env_name }}.qrimage.request
dialcode.keyspace	Keyspace name to store dial code process details in Cassandra	dialcodes