Rate This Document
Findability
Accuracy
Completeness
Readability

Upgrading OmniData

OmniData can be upgraded only after being approved by customers.

  1. Select the service nodes to be upgraded (for example, ceph1, ceph2, and ceph3), click Configure Service, select Command Execution, and click Add a Task.
  2. Edit the task content and click Save.

    Parameter

    Description

    Task Name

    Stopping the OmniData service

    Run Directory

    /

    Run Command

    sh /home/omm/omnidata-install/omnidata/bin/launcher stop

  1. Select the service nodes to be upgraded (for example, ceph1, ceph2, and ceph3). Configure the service flow, select File Transfer, and click Add a Task.

    Parameter

    Description

    Task Name

    Transferring the upgrade software package

    Task Description

    Transferring the upgrade software package for OmniData upgrade

    Local Path

    Select a local path for storing the OmniData software package based on your requirements.

    Remote Path

    /home/omm/omnidata-software

  2. Add a command execution service flow, edit the task content, and click Save.

    Parameter

    Description

    Task Name

    Software upgrade

    Task Description

    Upgrading OmniData

    Run Directory

    /home/omm/omnidata-install/omnidata-setup

    Run Command

    sh omnidata_upgrade.sh /home/omm/omnidata-software/BoostKit-omnidata_1.4.0.tar.gz

    Parameters in the omnidata_upgrade.sh script in 4 are described as follows:

    The first parameter indicates the absolute path of the upgrade package.

  3. Check the service status.

    The upgrade.sh parameter is the absolute path of the new package. The script checks whether the OmniData service is running. If the OmniData service is running, the upgrade will not be performed. Ensure that the OmniData service is stopped before the upgrade.

    Run the following command using SmartKit:

    /home/omm/omnidata-install/omnidata/bin/launcher status