IREX
EN

Update instance

Since IREX computational resources, databases, and services are deployed on the system servers, the update routine does not require any special actions on the client side. However, updates should be properly managed at the Customer's organization.

Updates to the Secure Cloud platform might temporarily terminate system service performance; updates to the Smart City shell typically do not. Anyway, an update is an event of special attention.

We recommend  keeping to the measures below to minimize possible disruptions to the system performance:

  • A DevOps engineer notifies his or her counterpart on the client side about the upcoming update release, its purpose, contents, and foreseeable implications.
  • Both parties agree on the date and time to upload the update to the servers.
  • Customer's users are notified about the update upload date and time, duration, and possible disruptions.
  • After the update upload is complete, check the system performance.
  • Should any malfunction be revealed, immediately contact Support.

Secure cloud update

The Secure Cloud update process is similar to the deployment process. Meanwhile, the Ubuntu OS may be updated too.

Updates can only be applied strictly in sequential order; skipping an update is impossible.

Prepare the Secure Cloud update

  1. Copy TLS keys.
  2. Check and correct, if needed, IP addresses in balancer to keep them different.
  3. Copy new version of  the Secure Cloud sub-platform repository to MAAS server.

Update routine step-by-step

  1. Check and get cluster config and inventory ready:

    2. Define cluster name, include all necessary *.yml files to config (monitoring/logging/DNS, etc.)
    Define user and keys for deployment
    Define required repositories for the machine source list.

  2. After the cluster config is ready,  deploy the Secure Cloud using the deployment script that includes all necessary component updates:

    3. Kubernetes
    Ceph
    Cassandra
    Postgres
    Kafka
    Etc.

Test the Private Cloud Update

Repeat the functionality tests to make sure the update was applied correctly.

Update the Smart City sub-platform

The Smart City upgrade process is similar to the deployment process in its essential features.

  1. Copy the Smart City platform repository or needed components to MAAS server.
  2. Get Kafka configs ready.
  3. Enter cluster name.
  4. Add config to Ansible directory.
  5. Check and make variables ready; fill in the backend address.
  6. Check needed node labels (backed/video analytics and others).
  7. Deploy the Smart City shell using the deployment configuration tool.

Test the Smart City update

Repeat the functionality tests to make sure the update was applied correctly.