FSM V1.4 Upgrade Plan for
Odisha is currently running on FSM v1.2 for 33 ULBs. Upgrading the platform to v1.3 requires the deployment of certain microservices related to FSM. There is no change in the core services.
FSM v.13 will be first deployed on SUJOG UAT and sanity testing is executed. Once PwC and eGov find this version to be good and signed off, a production upgrade is initiated.
Activities for production upgrade
Have alignment with the PwC team on the upgrade plan and release dates
Have a developer from the PwC team aligned to work with the eGov team for making the deployment on production and updating the MDMS
Inform the State team of the upgrade timeline and initiate the deployment off ULB working hours.
Send an email to PwC with the image details on the list of services and configurations that needs to be deployed on the server for the upgrade
Take a backup of all the existing images
Get the new images deployed on production
Get the MDMS changes, persister, indexer and other configuration changes done on production.
Test the FSM application using the production URL for the testing tenant.
As part of backward compatibility testing make sure the transactions created before the upgrade are working seamlessly.
PwC team to do sanity of the Sujog modules( if they want to)
Once sanity is passed the release can be considered successful and communication can be made with all stakeholders