Release Notes - Version 2.0 Vessel Registry

Release Summary

New Features and Improvements

Bug Fixes

Application Changes

Pre-Release Preparation

• Release Date: May 11

• Code freeze (April 20): All increment 2 PBIs are completed.

  • Bug fixes will continue

  • No new features will be introduced after code freeze

• Training required:

  • Acceptance environment setup after code freeze

  • Lucy and Troy will work with users prior to launch to train users on new features

• Decommissioning SCVLS:

  • Users are informed about the decommissioning SCVLS application

  • Web and DBA team are informed about revoking user write permissions (Future task)

  • Will give a grace period prior to decommissioning the SCVLS application

• Replicate production data in acceptance for testing. After testing will remove all the data.

• Sequence numbers should be verified/incremented for the new databases after the on-premise data migration

  • Client Detail Service Database

  • Vessel Registry service database

  • Vessel Detail service database

  • Vessel History service database

Release Process

Estimated downtime:

• Service Deployment: 2 hrs

• VRM Deployment: 2 hrs

Communication required:

• Coordination with Team Triton on the user migration from the legacy SCVLS to the cloud VR application

• Users are informed of downtime ahead of deployment

• Users are instructed to refrain from using the Legacy SCVLS system

• MOLE team @Xia W will be informed once the services are deployed to production

Service Deployment (April 25):

• Client Detail Service

  1. Deploy Bicep templates to provision azure resources required for this service

  2. Database / Roles

  3. Service

• Vessel Registry Service

  1. Deploy Bicep templates to provision azure resources required for this service

  2. Database / Roles

  3. Service

• Vessel Detail Service

  1. Deploy Bicep templates to provision azure resources required for this service

  2. Database / Roles

  3. Service

• Vessel History Service

  1. Deploy Bicep templates to provision azure resources required for this service

  2. Database / Roles

  3. Service

• Vessel Registry Gateway

• Job Scheduling Service

  1. Deploy Bicep templates to provision azure resources required for this service

  2. Database / Roles

  3. Service

• Vessel Registry Database Updater Gateway (Kanga Server)

  • Run pipeline with release configuration

  • Move generated service files to vrdu-gw

• Vessel Registry Database Updater Service

  • Create an SCVLS VRDU user in A01_USER table (Reference the development SCVLS table for the required data)

  • Run pipeline with release configuration

  • Move generated service files to vrdu-api-prod

• Workload Management Service

  1. Execute data migration script

  2. Deploy to staging slot

  3. Deploy application resource / Swap production with staging slot to make the staging the production slot

Vessel Registry Management Deployment (May 11):

1. Update list of value service

2. Deploy application to staging slot

3. Swap staging and production slots

4. Trigger the Job Scheduling Service recurring jobs for

   1. Batch Suspensions (Scheduled for midnight every day)

   2. Vessel History Service Caching (Scheduled for 5 am every day)

5. Verify functionality

Back-out Method

Service Deployment

• WMS - Swap deployment slots to revert the application to older version

• All other services can remain deployed, but status switched stopped, as they are unused and will not affect already deployed services

Vessel Registry Management Deployment

• Swap staging slots to revert to application back to version 1

• If WMS is deployed and an issue is identified that is directly related to the service, we rollback the service to the previous version.