Tempo Upgrade Process

Tempo Upgrade Process

Overview

This article provides a structured approach to upgrading Tempo, focusing on testing, validation, and customer support throughout the process. The upgrade process is divided into three phases: pre-release, pre-upgrade, and post-upgrade. Each phase is outlined below.

Pre-Release:

In this phase, the Appsec SRE (Application Security Reliability Engineering) team selects a representative sample of customer configurations to perform virtual upgrades. These virtual upgrades are carried out in a temporary testing environment.

Automated test suites are executed against the verify environment after the upgrade is deployed. Findings from these tests fall into three categories:

• Engineering Fix Required: Issues that require an engineering fix to ensure a successful release. These are tracked within the ticketing system and go through the development lifecycle.

• Customer Fix Required: Issues that require customers to update their configurations. Documentation is created to guide users on how to correct these issues upon release.

• Known Issue: Low-risk issues that can be documented as known issues and shared with customers upon release.

Scheduling an Upgrade

Upgrade requests will require a lead time of five (5) business days. When scheduling an upgrade, keep in mind that a work window of 2-3 hours will be required for the upgrade. This means the system cannot be used during the work window. Customers must also ensure their batches and procedures are complete and the system is in a good state to be paused.

The scheduling of the actual release is marked as "TBD" (To Be Determined) in this phase.

Pre-Upgrade

Customers are contacted in advance of their upgrade dates to coordinate a pre-upgrade test. The environment scheduled for the upgrade is cloned into an ephemeral environment, and the upgrade is performed. Automated test suites designed for upgrades are used to test the cloned environment.

If any issues are identified during this pre-upgrade test, a member of the Apprentice CS (Customer Service) team collaborates with the customer to review the issues and provide guidance on how to resolve them.

Once any blocking issues are resolved, the customer's environment is upgraded on their scheduled date.

Post-Upgrade

After the upgrade, any issues that require changes in customer configurations need to be addressed immediately and time should be allocated accordingly to address the changes.

Please refer to the Tempo v7.0 Release Notes for detailed information on release updates.

As part of the upgrade experience, customers must refer to the Procedure Verification tab to ensure there are no outstanding issues post-upgrade. It is a best practice to complete a dry run of the procedure once updated.

In order to minimize production downtime, customers should only make changes to procedures in the dev environment. Once the necessary changes have been made, the procedure should then be migrated to val and finally to prod to implement the changes.

Additional items to address:

• Updated signature reasons
• System date/time format

Customers can refer to a list of known fixes provided as part of the Impact Analysis in the Accelerator Pack, to guide them through the corrective measures.