Skip to content

Hotfix for OperationKeyManagement version 2.1.2_impl

Latest
Latest

Choose a tag to compare

View all tags
@PrathibaJee PrathibaJee released this 28 Feb 06:20
· 2 commits to develop since this release
V2.1.2-hotfix.1_impl
4771012
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Software Release Notes

Application: OperationKeyManagement
Version: V2.1.2
tag: V2.1.2-hotfix.1_impl
Release Date: 28.02.2025

Overview

This hotfix addresses critical improvements and ensures enabling security in the SDN ApplicationLayer. It introduces necessary deployment procedures to maintain operational consistency while updating the system.

Pre-Deployment Requirements

Note : For test environment , the environment does not contain any dummy values configured in the TinyApplicationController's client stacks.

  1. Operational Mode Check:
    • If OKM (Operation Key Management) is running in REACTIVE mode, switch OKM’s Operational Mode to OFF.
    • This action triggers a cyclic process (lasting approximately 15 minutes) to update the default operation key across all consuming applications.

Deployment Procedure

  1. Backup Configuration:

    • Take a backup of OKM’s database/config.json file before proceeding with the patch deployment.

  2. Patch Deployment:

    • Deploy V2.1.2-hotfix.1_impl.

  3. Restore Configuration:

    • Replace the previously backed-up OKM’s database/config.json file into the OKM volumes.

Reason for Backup and Restore

  • The existing version of OKM contains configuration data for all deployed business applications.
  • Since the hotfix does not support a dedicated port for running an instance, data transfer using the bequeath-your-data-and-die API is not possible.
  • To prevent loss of existing business application data, a backup and restore procedure is required.

Testing Guidelines for Reactive Mode in the Test Environment

When testing Reactive Mode, adhere to the following guidelines:

  1. Do NOT modify the LTP client stack (TCP, HTTP, operation-client) configurations of ApplicationLayerTopology (ALT) and OperationKeyManagement (OKM) in:

    • The config.json file.
    • The REST interface (Swagger).

  2. Do NOT use dummy values when testing Individual and Basic services of ALT and OKM.

    • Example: Avoid changing the operation-client API (/v2/regard-updated-link) of OKM to a dummy value like /v1/list-applications.

  3. Do NOT modify TCP server settings to:

    • A dummy value.
    • A different application's TCP configuration.

For further assistance, contact the development team.

Assets 2
Loading