Update DESK Managed

To run a successful update, you need at least 3 GB of available space on the partition where DESK Managed is installed.

Update of DESK Managed consists of two steps:

Downloading the update package.
Performing the actual update.

Sequential updates

Updates of DESK Managed can only be done sequentially with regard to versions. If your Managed cluster currently runs for example, version 1.146 and you want to upgrade it to version 1.150, you'll have to upgrade first to version 1.148 and then to version 1.150.

If you update several versions in a row , it is necessary to wait at least 24 hours between updates.

Package download

Typically, the update package download occurs automatically. If you wish to download the update packaged manually, the automatic download can be disabled on demand only via the Mission Control.

For servers not connected to Mission Control (offline servers), upon update release, you will receive an official email with a link to download the update package.

Automatic update (recommended)

For automatic updates, all you need to do is specify a convenient time when your users won't be using DESK Managed and the system can upgrade itself (for example, during a previously scheduled maintenance window).

Update in progress

Your monitoring and cluster management pages won't be accessible during the upgrade process if your cluster consists of only two nodes or the upgrade requires a restart of all nodes simultaneously (rare occurrence).

To define a start time for automatic updates:

From the navigation menu, select Settings > Automatic update.

Set the Install DESK cluster updates automatically switch to the On position.

Cluster license

This switch is disabled if the license for the cluster has the Enforce automatic cluster updates feature enabled. In such cases, even the cluster administrator can't change this setting.

Specify a weekly maintenance window start time. DESK Managed updates will start at the time you specify.
This setting doesn't affect the download of updates.

Manually triggered update

For manually triggered updates, you have to trigger the actual update with the user interface or via the REST API. Once triggered, the update process is performed in the same way as in the automatic updates. Typically, you would use the manually triggered update if you wish to initiate the update outside scheduled maintenance window.

Offline cluster update

Offline cluster is a cluster with a specific license that permits this cluster to operate in closed environments. These clusters are administered by Cluster Management Console (CMC). Once the update is announced, you will receive an email with a link to download the update package.

To update an offline cluster:

Download the update package from the official source to the node.

Use the Cluster Management Console (CMC) to upload the patch to the cluster.
The Cluster Management Console will propagate the update package to all the nodes and execute the update in the same way as in the automatic updates.

Manual update

For manual update, you must manually download the update package, manually propagate the update package to all your cluster nodes, and manually initiate the update script.

Upgrading Managed nodes to version 1.172

This update procedure exception is specific only to updating Managed nodes to version 1.172. You must shut down DESK services on all nodes during the update. This means that your cluster won't monitor any data during the update. The downtime depends on your cluster size and the monitoring data in your cluster environment. You should plan for approximately two hours of update time. This estimate assumes that the update script is executed in parallel on all nodes.

Stop DESK services on all nodes.
Log into each node as a root user and execute the desk.sh command with the stop parameter.
By default, the script is located at /opt/desk-managed/launcher.

[root@localhost]# ./desk.sh stop

After you have stopped DESK services on all nodes, download the update package from the official source to each node and give the update package executable permissions. You can copy the update package into any convenient path on the node system. Use the Linux chmod command to set permissions:

[root@localhost]# chmod +x update_package.sh

On all nodes, execute the update script with the --no-start parameter. When the no-start parameter is set, DESK services won't be automatically started after the update is complete.

Minimize downtime

To minimize downtime, we recommend that you execute the update script in parallel on all nodes.

[root@localhost]# ./update-package.sh --no-start
Starting DESK 1.172.60.20190506-112012 installer ...               OK
Testing connection to DESK Mission Control ...                     OK
...
DESK session replay store is located in directory /var/opt/desk-managed/server/replayData
You can now log into your DESK Server at https://10.10.10.10

[root@localhost]#

After the updates have completed on all nodes, start the DESK services on each node individually.
Log into the each node as a root user and execute the desk.sh command with the start parameter.
By default, the script is located at /opt/desk-managed/launcher.

[root@localhost]# ./desk.sh start

Update nodes in sequence

Since the node that's being updated isn't operating, it's crucial that you manually update in sequence.
Wait until the node update completes before starting an update on the next node.

To manually update the cluster, perform this procedure for each node in sequence one node at a time:

Download the update package from the official source to the node.
You can copy the update package into any convenient path on the node system.

Give the update package executable permissions. Use Linux chmod command.

[root@localhost]# chmod +x update_package.sh

As a root user, execute the update script with the --upgrade parameter.
Once the update completes successfully, move to the next node and repeat the procedure.

[root@localhost]# ./update_package.sh --upgrade

Node upgrade example

[root@localhost]# ./update-package.sh --upgrade
Starting DESK 1.168.60.20190506-112012 installer ...              OK
Testing connection to DESK Mission Control ...                     OK
Verifying system compatibility ...                                      OK
Verifying disk space ...                                                OK
Verifying DESK directories ...                                     OK
Verifying system privileges ...                                         OK
Verifying system connectivity ...                                       OK
Stopping DESK ...                                                  OK
Preparing system user for DESK ...                                 OK
Initializing upgrade ...                                                OK
Checking user permissions ...                                           OK
Checking file ownership ...                                             OK
Downloading DESK OneAgent. This may take a few minutes ...         OK
Upgrading. This may take a few minutes ...                              OK
Preparing connectivity settings ...                                     OK
Setting up cluster configuration. This may take a few minutes ...       OK
Starting DESK. This may take up to half an hour ...                OK

Upgrade completed successfully after 8 minutes 50 seconds.

DESK binaries are located in directory /opt/desk-managed
DESK data is located in directory /var/opt/desk-managed
DESK metrics repository is located in directory /var/opt/desk-managed/cassandra
DESK Elasticsearch store is located in directory /var/opt/desk-managed/elasticsearch
DESK server store is located in directory /var/opt/desk-managed/server
DESK session replay store is located in directory /var/opt/desk-managed/server/replayData
You can now log into your DESK Server at https://10.10.10.10

[root@localhost]#

DESK Managed version check

To check which DESK Managed version you currently use:

Log into the Cluster Management Console or one of your monitoring environments.

Open the User menu in the top right corner. The version number appears at the bottom right corner of the User menu.

Alternatively,

Navigate to the home page of your Cluster Management Console, where you can view your DESK Managed deployment status.

Click a DESK Managed node to open the overview page of this node. The installed version appears right under the title of the page.