9.2

Edit

Upgrade from v9.0.x to v9.2.x

Overview

This guide describes the steps for in-place SPA upgrade from v9.0.x to v9.2.x.

During the upgrade procedure the installer:

  • Creates a backup of the current config files.
  • Replaces them with new versions.
  • Overrides values in new files with those from the old installation.
caution

Do not change passwords when performing this upgrade. Use the same passwords from your SPA installation. Otherwise, upgrade will fail. Changing passwords is supported after upgrading to SPA v9.2. Do not use dots "." in paths

Prerequisites

  • WorkFusion SPA 9.0.x is installed on RHEL 7.
  • WorkFusion SPA 9.2.x product install packages are downloaded and extracted to <PACKAGE_DIR> on all servers.
  • s3 backend and data migrated from Riak to MinIO.
  • s3_hostname added as additional A or CNAME record for APP server
  • APP server's TLS certificate must be valid for both app_hostname and s3_hostname (either wildcard, or SAN).
  • Prepare Business Processes to upgrade migration notes.

Predefined common variables (set your own values in config.yml before installation):

  • WF_USER: WorkFusion user. Default is wfuser
  • <INSTALL_DIR>: WorkFusion Home Directory. Default is /opt/workfusion
  • <PACKAGE_DIR>: WorkFusion Installer Directory. Default is /opt/workfusion/wf_installer
  • Available <SERVER_ROLE>:
    • apm: APM server
    • app: APP server
    • db: DB server
    • ocr: OCR server
    • vds-master: AutoML Master server
    • vds-slave: AutoML Agent server

Preparation steps

  1. Ensure, that DNS names for servers are configured according to the DNS name configuration section.

    The following DNS names are not required in v9.2 and can be removed:

    crowdcontrol.taglib.db.example.com
cv-help.db.example.com
doc-upload.db.example.com
logos.crowdcomputing.db.example.com
public.crowdcontrol.db.example.com
recorder-images.db.example.com
secdocs.db.example.com
tinymce-resources.db.example.com
vds-models.db.example.com
vds-resources.db.example.com
workfusion-resources.db.example.com
workfusiondevelopment.db.example.com
workspace-resources.db.example.com

  2. Stop all processes on all servers.

    • SSH into <SERVER_ROLE> server.

    • Run as <WF_USER>.

    wfmanager stop all

  3. Copy certificates and configs into the 9.2 <PACKAGE_DIR>

    The old certificates, secrets and config files can be reused from the previous installation. They can be found in /distr/2018-04-28-1524913731/.

    Run as <WF_USER> on all servers:

    cd <PACKAGE_DIR>
cp -r <INSTALL_DIR>/distr/2018-04-28-1524913731/certificates .
cp <INSTALL_DIR>/distr/2018-04-28-1524913731/config_overrides.yml ./config_overrides.yml
cp <INSTALL_DIR>/distr/2018-04-28-1524913731/secrets_overrides.yml ./secrets_overrides.yml

  4. Turn off passwords verification checks. Starting from v9.1, we introduced verification for passwords complexity on precheck phase:

    Note the following password policy rules for secrets.yml:

    • In passwords English alphabetical characters must be used.
    • Passwords must contain 6-20 characters.
    • Passwords must contain at least one capital letter [A-Z].
    • Passwords must contain at least one number [0-9].
    • Passwords must contain at least one of the following special symbols unless limitations are explicitly described in comments: "!", "*", "#", "%", "^", "@".
    • Passwords must not contain the following symbols: "$", "&".

    The password verification may cause failures during the upgrade. The thing is passwords from previous installation will be used during the upgrade and they may not satisfy new passwords requirements.

    cd <PACKAGE_DIR>
echo "passwords_check: false" >> ./config_overrides.yml

  5. Add s3_hostname into config file:

    cd <PACKAGE_DIR>
echo "s3_hostname: app-s3.hostname" >> ./config_overrides.yml

  6. Copy the license file.

    The license file should be copied to APP Server only.

    Run as <WF_USER>.

    cp <INSTALL_DIR>/workfusion/conf/license.properties .

Upgrade order

  1. DB Server
  2. APP Server
  3. Other servers (can be updated in parallel)

Upgrade steps

Go to WorkFusion Installer Directory:

cd <PACKAGE_DIR>

DB, APP, APM, OCR servers

  1. Perform precheck and preinstall operations.

    Run as root.

    ./install.sh precheck <SERVER_ROLE> -e @config_overrides.yml -e @secrets_overrides.yml
./install.sh preinstall <SERVER_ROLE> -e @config_overrides.yml -e @secrets_overrides.yml

  2. Perform Installation and post-install check operations.

    Run as <WF_USER>.

    ./install.sh install <SERVER_ROLE> -e @config_overrides.yml -e @secrets_overrides.yml
./install.sh check <SERVER_ROLE> -e @config_overrides.yml -e @secrets_overrides.yml

AutoML-Master Server

  1. Perform precheck and preinstall operations.

    Run as root.

    ./install.sh precheck vds-master -e @config_overrides.yml -e @secrets_overrides.yml -e ''{\'vds_update_zookeeper_config\':false}''
./install.sh preinstall vds-master -e @config_overrides.yml -e @secrets_overrides.yml -e ''{\'vds_update_zookeeper_config\':false}''

  2. Perform installation and post-install check operations.

    Run as WF_USER.

    ./install.sh install vds-master -e @config_overrides.yml -e @secrets_overrides.yml -e ''{\'vds_update_zookeeper_config\':false}''
./install.sh check vds-master -e @config_overrides.yml -e @secrets_overrides.yml -e ''{\'vds_update_zookeeper_config\':false}''

AutoML-Agent Server

  1. Perform Precheck and Preinstall operations.

    Run as root.

    ./install.sh precheck vds-slave -e @config_overrides.yml -e @secrets_overrides.yml
./install.sh preinstall vds-slave -e @config_overrides.yml -e @secrets_overrides.yml

  2. Perform installation and post-install check operations.

    Run as WF_USER.

    ./install.sh install vds-slave -e @config_overrides.yml -e @secrets_overrides.yml
./install.sh check vds-slave -e @config_overrides.yml -e @secrets_overrides.yml

After upgrade to v9.2, the default workfusion password will be changed to wf_password from secrets.yml.

Post-upgrade steps

You can review difference between old configuration files and new in changes log: /distr/2018-04-28-1527769370/diff_changes_.log

Follow the steps from the Post-installation guide to make sure the environment works properly.

← PreviousNext →