Update Inforiver Container Instances (for 3.x users)

This guide explains how to update Inforiver container instances in an Azure on-premises environment.

Follow these steps carefully to ensure a smooth update and access to the latest features. You can refer to the screenshots provided for additional guidance.

1. Edit the CNI Configuration

Open your Azure CLI window and run the following command:

az container export -g <resource group name> -n <container instance name > --file output_file

To download the output file, click on Manage files -> Download and enter the path of the output file. Click Download.

Click on the output file to download it to your local system.

Now, configure the below-listed containers in this file for Inforiver container deployment.

Containers Instance List - 1

The following are the set of containers required for the Inforiver deployment of Azure Container Instance-1.

Note: Transition from Default Azure Domain to Custom Domain

When transitioning to a custom domain (e.g., https://webapp.inforiver.com) from the default Azure domain (e.g., https://webapp.azurewebsites.net), it is necessary to update the URL in the configuration settings of both the Azure App Service and the associated Container Instances. Specifically, ensure the environment variable ADMIN_PORTAL_URL is updated to reflect the new custom domain in both services.

i) Inforiver Cron

- name: inforiver-cron-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      image: turing.azurecr.io/turing-cron:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 0.5

ii) Inforiver Audit

- name: inforiver-audit-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      image: turing.azurecr.io/turing-audit:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 0.5

iii) Inforiver Orchestrator

- name: inforiver-orchestrator-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      image: turing.azurecr.io/turing-orchestrator:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 1.0

iv) Inforiver Worker

- name: inforiver-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      image: turing.azurecr.io/turing-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 2.0

v) Inforiver Writeback Worker

- name: inforiver-writeback-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      image: turing.azurecr.io/turing-writeback-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 3.0

vi) InfoBridge Writeback Worker

- name: inforiver-infobridge-writeback-worker
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      - name: PRODUCT_BUILD
        value: inforiver
      - name: LISTENER_MODE
        value: dataflow
      image: turing.azurecr.io/turing-writeback-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 2.0
      volumeMounts:
      - mountPath: /mnt/azure
        name: infofile

vii) InfoBridge Transformation Worker

- name: inforiver-infobridge-transformation-worker
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      - name: PRODUCT_BUILD
        value: inforiver
      - name: SERVICE_NAME
        value: infobridgeTransformationWorker
      - name: GRPC_URL
        value: localhost:9006
      image: turing.azurecr.io/turing-datasource-integration-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 1
          memoryInGB: 2.0
      volumeMounts:
      - mountPath: /mnt/azure
        name: infofile

viii) InfoBridge Visual Worker

- name: inforiver-infobridge-visual-worker
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      - name: PRODUCT_BUILD
        value: inforiver
      - name: SERVICE_NAME
        value: infobridgeVisualWorker
      - name: VISUAL_WORKER_LISTENER_MODE
        value: dataFlowSourceIntegration
      - name: DEFAULT_MODE
        value: Non-Aks
      image: turing.azurecr.io/turing-visual-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 2.0
      volumeMounts:
      - mountPath: /mnt/azure
        name: infofile

ix) InfoBridge Engine Worker

- name: inforiver-infobridge-engine-worker
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      - name: DUCKDB_MOUNT_PATH
        value: /mnt/azure
      image: turing.azurecr.io/turing-infobridge-engine:<tag>
      ports:
      - port: 9006
        protocol: tcp
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 2.0
      volumeMounts:
      - mountPath: /mnt/azure
        name: infofile

Containers Instance List - 2

The following are the set of containers required for the Inforiver deployment of Azure Container Instance-2.

i) Inforiver Writeback Worker-1

- name: inforiver-writeback-worker-container-1
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      image: turing.azurecr.io/turing-writeback-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 3.0

ii) Inforiver Auto Writeback Worker

- name: inforiver-auto-writeback-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      - name: IS_AUTO_WRITEBACK_CONTAINER
        value: Y
      image: turing.azurecr.io/turing-writeback-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 2.0

iii) Inforiver Visual Worker

- name: inforiver-visual-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      image: turing.azurecr.io/turing-visual-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 2.0

iv) Inforiver ETL Worker

- name: inforiver-etl-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      image: turing.azurecr.io/turing-etl-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 1.0

v) Inforiver Comment Worker

- name: inforiver-comment-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
- name: SERVICE_NAME
        value: "commentWorker"
      image: turing.azurecr.io/turing-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 1.0

After adding the list of container configurations in both container instances, verify these steps in both container instance configurations.
Provide the username and password for pulling the image from the registry. You would have received this information during the initial deployment. If not, please get in touch with our support team.
Remove the IP configuration section from the configuration file from both ACIs.

Provide the storage account details in the volume section for the first container instance only.

volumes:
  - azureFile:
      shareName: <filesharename>
      storageAccountName: <storage account name>
      storageAccountKey: <storage account primary key>
    name: <volumename>

Note: Storage account keys can be obtained from the respective storage account's Access keys section.

Update the API version as specified below.

apiVersion: '2023-02-01-preview'

2. Create ACI

We need to separate the ACI into two container instances.

First, add the initial set of Inforiver containers into one configuration file and create the first ACI with a name, say inforivercontainerinstance.
Then, add the second set of Inforiver containers in another configuration file and create the second ACI, say inforivercontainerinstancenew.

After adding all the containers in the configuration files, execute the following commands in the Azure CLI to create two separate container instances.

az container create -g <resource group name> -n <container instance name> --file output_file

az container create -g <resource group name> -n <container instance name> --file output_file1

The CNI will start provisioning with the latest configuration.

Please wait until the status is complete.

By following the above steps, you will be able to successfully update the Inforiver container instances in your Azure environment.

If you encounter any issues or need further assistance, please contact our technical support team here.

PreviousIntegrate EDITable with Inforiver (for 2.x users)NextUpdate EDITable Container Instance (for 3.x users)

Last updated 3 months ago