Update¶

Hint - logon data

You receive the logon data for the SEAL Systems delivery platform from your Technical Project Manager at SEAL Systems.

Hint - no Internet access

If the server on which you want to install SEAL Operator does not have Internet access, use another server with Internet access for logging on to the SEAL Systems delivery platform and downloading the folder. Then, copy the downloaded zip file to the server on which you want to install SEAL Operator.

Hint - configuration

The configuration in Consul etc. and the customer certificates will not be overwritten when updating.

Update To 1.5.0¶

Before the Update (1.5.0)¶

Version 1.5.0 of SEAL Operator is a breaking change to previous versions. The SEAL NATS message broker has been introduced to improve the message handling. It has to be installed before updating to SEAL Operator 1.5.0. For more information about the SEAL NATS installation, refer to the SEAL NATS documentation.

In addition, when connected to a PLOSSYS 4 system, the node-p4rest service has to be updated to version 6.0.0 or higher.

Update To 1.4.0¶

After the Update (1.4.0)¶

With SEAL Operator 1.4.0 French has been added to the available languages to choose for the user interface. If it isn't showing up in the selection dialog, add 'fr' to the system key AVAILABLE_LANGUAGES.

SEAL OP-CLI needs to be updated to version 1.2.0 for the creation of Web Portal shares via script.

Update To 1.3.0¶

Before the Update (1.3.0)¶

With SEAL Operator 1.3.0, the MongoDB service has been replaced by a newer incompatible version. Therefore, the data stored in MongoDB has to be exported before the update and imported again after the update. For how to do this, refer to the SEAL-specific MongoDB documentation.

After the Update (1.3.0)¶

With SEAL Operator 1.3.0, the MongoDB service has been replaced by a newer incompatible version. Therefore, the MongoDB data exported before updating has to be re-imported. For how to do this, refer to the SEAL-specific MongoDB documentation.

Update To 1.2.0¶

Before the Update (1.2.0)¶

With SEAL Operator 1.2.0, the version of seal-consul-agent was increased from 0.9.3 to 1.7.4, which has an incompatible database structure. Therefore, the data stored in Consul has to be exported before the update and imported again after the update.

Before updating SEAL Operator, export the Consul data. For more information about exporting the data, refer to Administrate the System Configuration.
Remove all files from the /opt/seal/data/seal-consul-agent directory.

After the Update (1.2.0)¶

After the update, start seal-consul-agent, refer to Administrate Services.
Import the data exported before the update, refer to Administrate the System Configuration.

Update SEAL Operator¶

Download the Operator - 1.5.1.648 - rpm folder. It is saved as Operator - 1.5.1.648 - rpm.zip.
Extract Operator - 1.5.1.648 - rpm.zip.
Switch to the Operator - 1.5.1.648 - rpm directory and start the installation of the packages contained there:
```
cd "Operator - 1.5.1.648 - rpm"
```
```
sudo sh install.sh
```
Start SEAL Operator:
```
operator service start
```

Hint - no automatic start

After an installation or update, you need to start the operator service yourself. It won't start automatically.

Update the `node-p4rest` Service¶

The following steps are only required if the PLOSSYS 4 connector is used in your installation.

Execute the following steps on the server on which the PLOSSYS 4 system has been installed:

In a browser, log on to the SEAL Systems delivery platform with your logon data:

https://delivery.sealsystems.de

Hint - logon data

You receive the logon data from your Technical Project Manager at SEAL Systems.
Download the node-p4rest-6.0.0-626.x86_64.rpm file from the SEAL Systems delivery platform. It is saved as node-p4rest-6.0.0-626.x86_64.rpm.

Install node-p4rest-6.0.0-626.x86_64.rpm.

RHEL:

sudo yum install node-p4rest-6.0.0-626.x86_64.rpm

SUSE:

sudo zypper install node-p4rest-6.0.0-626.x86_64.rpm