Movement of MOSIP v1.2.1.0 in Collab Env

[Varaniya201]

Platform Upgrade to v1.2.1.0 (Repos v1.3.0)

Overview

As part of the post-release activities, the Collab environment platform version must be upgraded to v1.2.1.0 (Repositories v1.3.0). The following activities should be completed to ensure a successful end-to-end upgrade.

Upgrade Activities

S.No	Activity	Description	Owner
1	Database Backup	Take a complete backup of the existing Collab database before initiating the migration process.	DevOps
2	Version Verification	Confirm the versions of Database, ID Schema, mosip-data, and mosip-config before starting the upgrade.	Dev
3	Database Analysis & Testing	Analyze the database changes introduced in the target release and perform validation testing.	Dev
4	Schema Comparison	Compare the CRE and Collab database schemas after upgrading Collab to v1.2.1.0. Ensure that custom changes introduced for Inji and eSignet support are retained and no regressions are introduced.	Dev
5	Artifactory Validation	Verify whether any repository, image, or artifact updates are required in Artifactory.	DevOps & Dev
6	Rollback Plan	Prepare, review and signify rollback plan	DevOps & Dev
7	Repository Upgrade	Upgrade all repositories from the current version to the latest released version (v1.3.0).	DevOps
8	Automation & DSL Deployment	Deploy Automation and DSL components and execute sanity validation tests.	DevOps
9	User Acceptance Testing (UAT)	Perform end-to-end UAT to validate platform functionality after the upgrade.	PO
10	Community/ External Party Announcement	During pre and post migration share the upgrade information to stakeholders and third party integrators (Inji/ eSignet/CRVS/PMS/ARC/ Partner Eco System/ DST)	PO

Risks and Validation Points

S.No	Area	Validation Required
1	Dynamic OTP	Verify that Dynamic OTP is enabled by default in the latest version and confirm expected behavior across all applicable workflows.
2	eSignet & Inji Integration	Validate data-sharing dependencies and integration points with eSignet and Inji to ensure uninterrupted functionality.
3	CAPTCHA Validation	Verify CAPTCHA functionality and ensure successful validation across all applicable user journeys.
4	Automation & DSL	Confirm successful deployment and execution of Automation and DSL sanity tests after the upgrade.
5	Third-Party Integrations	Coordinate with external systems such as CRVS, inji and eSignet and ensure functional testing is completed after migration.
6	Data Backup	Consider IDA DB to be taken as backup for smoother upgrade; make sure to take back up of tables relevant to key manager and IDA
7	Limitation in sending email notification	Currently 500 is the maximum limitation to send email notifications.
8	Exposure of internal services	Currently in Collab, internal services has been exposed for third party integration as part of customisation. Hence this needed to be validated as part of the migration as well

Deliverables

Analysis & Findings

• Present the detailed analysis and findings from the upgrade assessment.
• Highlight any deviations from the proposed upgrade approach, along with the rationale and impact.
• Identify any changes to the estimated timelines resulting from the proposed approach or findings.
• Provide infrastructure sizing recommendations, including the number of nodes and resources required to successfully execute and support the end-to-end upgrade activities.

Migration Plan

• Document the recommended upgrade strategy, execution plan, and validation approach.
• Outline any dependencies, risks, and mitigation measures identified during the analysis.

Prerequisites for Migration

• Identify and share a set of sample UINs to be used for validation before and after the upgrade.
• Perform pre-upgrade and post-upgrade verification using the selected UINs to ensure:
  • Existing data remains accessible and intact.
  • Backward compatibility is maintained.
  • Core platform functionalities continue to operate as expected after migration.

Definition of Done

• Database backup completed successfully.
• Version verification completed.
• Database analysis and validation completed.
• Schema comparison completed with no regressions identified.
• Repository upgrade completed successfully.
• Artifactory validation completed.
• Automation and DSL sanity tests passed.
• UAT completed successfully.
• Third-party integration validation completed.
• Final sign-off obtained from all stakeholders.

[ckm007]

Current set of service images identified.
DB hop verification completed for all required DB's.
DB hop upgrade.csv created.
Config migrator executed.
Created set of new config files and manual adjudication.