9.1

Edit

General information

Prerequisites

  • The steps are valid only for Linux Servers: DB, APP, APM, OCR (Linux), AutoML (Cluster)

  • Linux servers are up and running and all system requirements are met as described in 9.2.x System Requirements

  • SSH access is allowed to the servers with root privileges

  • If created manually, a non-privileged user (WF_USER) must have the same name, UID, and GID.

  • DNS names for all servers (Linux and Windows) are configured according to the DNS names configuration guide.

  • Application Ports are open between servers.

  • Installation packages are uploaded to servers.

  • /opt/workfusion—INSTALL_DIR: default Workfusion installation directory. Change it to your own if necessary.

  • /opt/workfusion/wf_installer—<PACKAGE_DIR>: directory where installation package was extracted.

  • The steps described here cover 90% of all effort required for installing WorkFusion SPA.

  • In code snippets on this page some common variables are reasonably hard-codded so that it's easier to copy-paste every step if you agree on these defaults:

    • /opt/workfusion/workfusion-full-package-9.1.0.0.tar.gz: full path of installation package which was uploaded to all Linux servers
    • /opt/workfusion/wf_installer: directory where the package is extracted (may be referred to as <package_dir>)
    • /opt/workfusion: directory where the product will be installed (may be referred to as <install_dir>)
    • wfgroup and wfuser: group and user which will own the product at run-time (may be referred to as <wf_group> and <wf_user>)

  • You can safely use your own values, replacing the default ones appropriately.

Extract package

Perform the steps below on all Linux servers.

  1. Log in to the target server as root.

    Example

    ssh -i /path/to/private-key.pem user@hostname.example.com
sudo su - root

  2. Choose or create a directory on the file-system where you want to extract installation package. Grant read access for this directory to all users:

    mkdir /opt/workfusion/wf_installer
chmod 0755 /opt/workfusion/wf_installer

  3. Extract the installation package:

    tar -xzvf /opt/workfusion/workfusion-full-package-9.1.0.0.tar.gz --strip 1 -C /opt/workfusion/wf_installer

Perform initial configuration

Perform the steps below on DB server.

  1. Log in to DB Server via SSH.

  2. Edit the following files with any available editor (vi is used in the example below):

    cd /opt/workfusion/wf_installer
vi config.yml
vi secrets.yml

    The configuration files are thoroughly commented to explain each of the parameters.

    You can also refer to Workfusion Config Files section for more details on each configuratin option.

  3. Generate TLS and Vault Certificates for all servers:

    1. Generate TLS and Vault Certificates by the generate-certificates.sh script. It is mandatory to run ./generate-certificates.sh script as it also generates Vault authentication certificates among others, which are required for Product:

      ./generate-certificates.sh -n -d -p "my_ca_pass"
      • After running this command, two folders are populated with certificates: ./certificates and ./certs_db.
      • The command above has generated self-signed certificates for all Linux servers. Refer to Using TLS certificates for more details on other options.
      • If in the config.yml file, https_enabled: true, the certificates from the ./certificates folder will be used for configuring HTTPS for all components.
      • If in the config.yml file, https_enabled: false, the certificates from the ./certificates folder will be ignored (except for Vault certificates).

    2. If you want to apply publicly trusted TLS certificates, you should put them into the ./certificates folder instead of the ones generated with ./generate-certificates.sh.

  4. We need to distribute the ./certificates folder (not ./certs_db), the config.yml and secrets.yml files across all other Linux servers.

  5. Create the archive of these files:

    tar czvf wf_configs.tar.gz certificates config.yml secrets.yml

    After running this command, the wf_configs.tar.gz file was created.

  6. The easiest way to deliver wf_configs.tar.gz to all other Linux servers is via python SimpleHTTPServer. Firstly, start the HTTP server on any port which is accessible on DB server for all other Linux servers (it can be any port, even the one which will be used by some service on DB server, as it's temporary operation just for downloading wf_configs.tar.gz to other servers). In the example below, 9999 port is used:

    python -m SimpleHTTPServer 9999

    This command makes the directory content where the command was executed downloadable via HTTP.

Run the next steps on all other Linux servers:

  1. Log in into target server as root and download wf_configs.tar.gz from DB server:

    cd /opt/workfusion/wf_installer


## install wget if not installed
yum -y install wget
wget http://db_hostname:9999/wf_configs.tar.gz -O wf_configs.tar.gz

  2. Unpack configs and certificates:

    tar xzvf wf_configs.tar.gz -C /opt/workfusion/wf_installer/

Install WorkFusion license

Perform the step below on APP server.

Copy the license.properties file (obtained from WorkFusion) to the location where you've extracted the installer: /opt/workfusion/wf_installer. Its full path should be as follows:

/opt/workfusion/wf_installer/license.properties

Run precheck

  • Should be performed on all Linux servers;
  • This step validates the provided configuration, checks system requirements and prerequisites.
  • This step does not change anything in the system.
  • It is impossible to proceed further with installation without passing this step.
./install.sh precheck <server_role>

Available Server roles:

  • apm: APM server
  • app: APP server
  • db: DB server
  • ocr: OCR server
  • vds-master: AutoML Master server*
  • vds-slave: AutoML Agent server*
  • vds-nfs: NFS server for AutoML servers*

* The VDS acronym refers to a legacy Workfusion product called Virtual Data Scientist. AutoML (Automatic Machine Learning) is the name of the latest component that does was VDS did previously. All references to VDS are references to AutoML.

Run preinstall automatically

  • Should be performed on all Linux servers;
  • To execute all preinstall steps automatically, two options should be set in config.yml:
    • automate_preinstall_steps: true
    • automate_system_packages_install: true

Tasks to be performed on this step:

  • Setting SELinux state to permissive with targeted policy.
  • Creating a user or ensuring the user exists, as defined in wf_user (default wfuser).
  • Creating directory as defined in install_dir.
  • Installation of packages from official RHEL repo. automate_system_packages_install should be set to true in config.yml. If not, see Required packages and install them manually.
  • Installation of bundled RPM dependencies that cannot be or have not yet been converted to the non-root variant.
  • Enabling and starting supervisord via systemd.

Run as root:

./install.sh preinstall <server_role>
  • If you use automate_system_packages_install: true, ensure that curl and openssl packages have versions at least not older than described in Required packages. You can check it as follows:
    • rpm -q curl
    • rpm -q openssl
  • After execution of this step on all Linux servers, proceed to the installation steps.
  • If for some reason you are not allowed to perform preinstall steps automatically, refer to the Run preinstall manually section, and then go to Installation steps.
← PreviousNext →