Table of contents

Install Watson Studio Local by web browser UI

You can install Watson Studio Local by web browser UI by running the installation without any configuration file present.

Requirement: Before you install Watson Studio Local, ensure that your servers meet all of the system requirements.
Restriction: The Amazon Web Services (AWS) installation supports a command line or configuration file installation only. A load balancer can only be specified in a configuration file installation.

To install Watson Studio Local by web browser UI, complete the following steps:

  1. Download the Watson Studio Local installation package to the first master node of your dedicated Watson Studio Local cluster. Ensure that the master node has a public IP address that is reachable by your web browser server.
  2. Move the installation package to the installer files partition you created (you cannot install from any path that is mounted as /), and make the installation package executable by entering chmod +x <installpkg>.
  3. Optional: To automatically install add-ons such as SPSS Modeler or H2O Flow, create a new addon-packages sub-directory in the same directory as the installer files. Download the installation package TAR files into the addon-packages sub-directory. Later, the installer will prompt for confirmation to install those add-ons. Restriction: This method does not work for the Watson Explorer oneWEX add-on.
  4. In /etc/selinux/config, ensure SELINUX=enforcing or SELINUX=permissive for Watson Studio Local to install. POWER requirement: Ensure that all of the nodes use container-selinux version 2.21 or later before you install Watson Studio Local.
  5. Run the installation package with the --extract-pre-install-scripts parameter to extract the pre-installation scripts for Watson Studio Local. RHEL cluster only: You can automatically install an RHEL docker on each node (requires a minimum of 200 GB raw disk) by completing the following steps on each node in the cluster:
    1. Enable a Red Hat repo for package installation on each node.
    2. Enable the extras repo on each node so docker can be installed, for example, --subscription-manager repos --enable rhel-7-server-extras-rpms.
    3. Ensure that there is a raw disk available (200G or more) on each node that has no partitions and no file systems. You can use wipefs --all --force /dev/xxx to prepare it.
    4. Run the docker_redhat_install.sh script you extracted on all nodes in the cluster to install docker using the RHEL repo.
  6. If you chose not to use the docker_redhat_install.sh script and selected SELINUX=enforcing, then after installing docker complete the following steps:
    1. In the /etc/sysconfig/docker file, remove --selinux-enabled from the OPTIONS line.
    2. Enter the following command: setsebool -P docker_transition_unconfined 1
    3. Restart docker.
  7. Run the extracted pre-installation check script on each node in the cluster:
    • For a cluster with five nodes or less, run pre_install_check.sh --type=3nodes on all of the nodes.
    • For a cluster that exceeds five nodes, run pre_install_check.sh --type=9nodes_master on all master nodes, pre_install_check.sh --type=9nodes_compute on all compute nodes, and pre_install_check.sh --type=9nodes_deploy on all deployment nodes.
    The script prompts for information about your installation such as path to the installation files, location of data (for master nodes), and the subnet being used by weave (the default is 9.242.0.0/16). You will get a pass or a fail for mandatory requirements, or a warning for issues such as cron jobs asking to make sure there are no scripts being run that might change the network configuration.
  8. For a six or more node installation by web browser UI, run the installation package without any parameters. For a three, four, or five node installation by web browser UI, run the installation package with the --three-nodes parameter. Wait several minutes for the pre-installation steps to complete.
  9. Agree to the terms and conditions.
  10. In the Assign & ping nodes page, the Private key filename field is optional. You can specify a private SSH key file (instead of a sudo user name and password) to install by using the private key as the credentials (ensure that this key can be used to make a successful SSH connection to each node in your cluster). Alternatively, you can leave the field blank and specify sudo user names and passwords instead.

    Figure: Panel for assigning a minimum of six nodes

    Assign and ping nine nodes screencap

    Figure: Panel for assigning a minimum of three nodes

    Assign and ping three nodes screencap

  11. Specify a cluster overlay network, or type in the suggested value of 9.242.0.0/16. Ensure that the value differs from any networks that exist within your local network. Otherwise, Watson Studio Local encounters conflicts when it tries to access outside resources.
  12. Specify one unused IP address as the proxy IP address. The IP address must be static, portable, and in the same subnet as the cluster.
  13. Specify the IP addresses of the nodes to install the components on. The program determines whether they meet the system requirements. If you are not using a private key file, then specify sudo user names and passwords for each node. Specify the path to store installer files and the path for service data storage (these two paths need to be the partitions pre-created and mounted with the xfs format).
  14. Optional: Add extra nodes to scale your cluster. In a runtime environment, Watson Studio Local supports adding compute and deployment nodes only.
  15. Start the installation. The program installs the Kubernetes cluster across the nodes you specified, configures the network and storage, sets up the docker registries, deploys the services such as Cloudant and Spark, and deploys Watson Studio Local and its user interfaces. This installation runs step-by-step, and might take a long time. If the page displays improperly due to a network issue, refresh the page. If an installation step fails, you can view the log and contact IBM support. To avoid unexpected issues, make sure to resolve the issue in the log before you retry or skip the step.
    Tip: If you see an error during deployment of Watson Studio Local or dashboard helm charts, then do not retry or skip; instead, watch the logs by running the following command: kubectl get po --all-namespaces | grep ibmdp-assistant-deployment | awk '{system("kubectl logs -n "$1" "$2)}'.

    Figure: Log file for a failed installation step with the retry or skip option

    Installation failure screencap

    Figure: Panel for a successful installation

    Installation success screencap

  16. Set the password for your primary Watson Studio Local administrator (user name is admin).
  17. Click the Submit and Launch button to open the Watson Studio Local client automatically. As the primary Watson Studio Local administrator, you can toggle to both the Watson Studio Local client and administration dashboard client from the same web address.

    Context switcher for client to the admin dashboard

See set up to configure your Watson Studio Local system.

Install for PowerBroker

Watson Studio Local Version 1.2.0.2 or later supports a number of PowerBroker configurations. PowerBroker manages Privileged Access Management in computing units, and is used to log user actions and privilege management through a central server.

To run the installer with pbrun, enter the following command:

pbrun bash -c "export TERM=\"xterm-256color\";
cd /ibm; ./installer_name --pbrun"

where /ibm represents the installation directory.

If you entered a non-root user, the add node pop up displays radio buttons that ask for Become Method. Choose pbrun and continue as normal.

To uninstall using pbrun, enter the following command:

pbrun bash -c "/wdp/utils/uninstall.sh --username=your_user_here --password --pbrun"