Installing IBM Visual Insights stand-alone

You use the command line to install IBM Visual Insights stand-alone.

IBM Visual Insights stand-alone installation prerequisites

You must complete the following installation prerequisites steps before you install IBM Visual Insights.
  1. Complete all steps in the Prerequisites for installing IBM Visual Insights topic.
  2. Your system must have a proper subscription and repository that provides you with updated packages. For information, see the Red Hat Subscription Manager documentation.
  3. Turn on Extra Packages for Enterprise Linux (EPEL). For information, see the EPEL website.
  4. If there was a previous version of PowerAI Vision installed but you do NOT wish to migrate the data, delete or move /opt/powerai-vision/volume. This will ensure that data for the previous install, such as data sets and trained models, will not appear in the newer version of the product.
Attention: You cannot install IBM Visual Insights stand-alone on the same system that has the following software installed:
  • IBM Data Science Experience (DSX)
  • IBM Cloud Private
  • IBM Watson Studio Local Edition
  • Any other Kubernetes based applications

Install IBM Visual Insights from IBM Passport Advantage

To install IBM Visual Insights stand-alone, complete the following steps:
  1. Download the product tar file from the IBM Passport Advantage website.
  2. (Optional) Verify the downloaded tar file by following the instructions in this topic: Verify the downloaded tar file.
  3. Unzip and untar the product tar file, and run the installation command for the platform you are installing on.
    RHEL
    sudo yum install ./<file_name>.rpm
    Ubuntu
    sudo dpkg -i ./<file_name>.deb
    The install files are extracted to visual-insights-arch-1.2.0.0-ppa, where arch is x86 or ppc, depending on your platform.
  4. Load the IBM Visual Insights images from the directory that contains the extracted tar file. The user running the script must have Docker privileges:
    sudo /opt/ibm/vision/bin/load_images.sh -f ./file_name.tar
    Note: The installation process can take some time to complete.
  5. (RHEL only) Open ports for the firewall to access IBM Visual Insights by running this script: 
    sudo /opt/ibm/vision/sbin/firewall.sh
  6. After the installation is complete, you can start IBM Visual Insights by running this script: 
    sudo /opt/ibm/vision/bin/vision-start.sh
    A user named admin is created with a password of passw0rd. For instructions to change these values, see Managing users.
    Note: The startup script will modify ownership and permissions on /opt/ibm/vision/volume so that the containers can run under a non-root ID and access the data.

    You must read and accept the license agreement that is displayed before you can use IBM Visual Insights.

    It can take several minutes to start IBM Visual Insights. To check the status of the startup process, run this script: 
    sudo /opt/ibm/vision/bin/helm.sh status vision
    In the output from the helm.sh status vision script, you can verify which IBM Visual Insights components are available by locating the Deployment section and identifying that the AVAILABLE column has a value of 1 for each component. The following is an example of the output from the helm.sh status vision script that shows all components are available:
    user@system:~$ /opt/ibm/vision/bin/helm.sh status vision
LAST DEPLOYED: Mon Feb 17 19:25:40 2020
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1beta1/Ingress
NAME        HOSTS  ADDRESS  PORTS  AGE
vision-ing  *      80       6d21h
==> v1/Pod(related)
NAME                                        READY  STATUS   RESTARTS  AGE
vision-elasticsearch-777f6bcc6c-5xvlg       1/1    Running  0         17h
vision-fpga-device-plugin-bm8qx             1/1    Running  0         17h
vision-keycloak-f57979785-fpw8q             1/1    Running  0         17h
vision-logstash-f8cc6fcc6-rhqtc             1/1    Running  0         17h
vision-mongodb-79b9d7977c-2twtb             1/1    Running  0         17h
vision-postgres-6f4788c594-gxcjp            1/1    Running  0         17h
vision-service-799c94f575-2cr48             1/1    Running  0         4h34m
vision-taskanaly-67745bc59f-qd225           1/1    Running  0         17h
vision-ui-774d989b47-2swvb                  1/1    Running  0         17h
vision-video-microservice-6fc86b5866-s8x44  1/1    Running  0         17h
==> v1/Secret
NAME            TYPE    DATA  AGE
vision-secrets  Opaque  4     6d21h
==> v1/ConfigMap
NAME           DATA  AGE
vision-config  53    6d21h
==> v1/PersistentVolumeClaim
NAME             STATUS  VOLUME       CAPACITY  ACCESS MODES  STORAGECLASS  AGE
vision-data-pvc  Bound   vision-data  40Gi      RWX           6d21h
==> v1/Service
NAME                       TYPE       CLUSTER-IP   EXTERNAL-IP  PORT(S)            AGE
vision-elasticsearch       ClusterIP  10.10.0.169  <none>       9200/TCP,9300/TCP  6d21h
vision-keycloak            ClusterIP  10.10.0.30   <none>       8080/TCP,8443/TCP  6d21h
vision-logstash            ClusterIP  10.10.0.198  <none>       9600/TCP           6d21h
vision-mongodb             ClusterIP  10.10.0.173  <none>       27017/TCP          6d21h
vision-postgres            ClusterIP  10.10.0.201  <none>       5432/TCP           6d21h
vision-service             ClusterIP  10.10.0.85   <none>       9080/TCP           6d21h
vision-taskanaly           ClusterIP  10.10.0.44   <none>       5000/TCP           6d21h
vision-ui                  ClusterIP  10.10.0.41   <none>       8080/TCP           6d21h
vision-video-microservice  ClusterIP  10.10.0.216  <none>       38080/TCP          6d21h
==> v1beta1/DaemonSet
NAME                       DESIRED  CURRENT  READY  UP-TO-DATE  AVAILABLE  NODE SELECTOR  AGE
vision-fpga-device-plugin  1        1        1      1           1          <none>         17h
==> v1/Deployment
NAME                       DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
vision-elasticsearch       1        1        1           1          17h
vision-keycloak            1        1        1           1          17h
vision-logstash            1        1        1           1          17h
vision-mongodb             1        1        1           1          17h
vision-postgres            1        1        1           1          17h
vision-service             1        1        1           1          17h
vision-taskanaly           1        1        1           1          17h
vision-ui                  1        1        1           1          17h
vision-video-microservice  1        1        1           1          17h
NOTES:
Find the Visual Insights UI URL by running the following commands:
export NODE_IP=$(kubectl get ing vision-ing --namespace default -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
echo https://${NODE_IP}/vision/

    After the application startup has completed and the user interface is available, it can be accessed at https://hostname/visual-insights/, where hostname is the system on which you installed IBM Visual Insights.

  7. Install any available fix packs. For instructions see Getting fixes from Fix Central.

Install IBM Visual Insights from AAS

  1. Download the product tar.gz file from Advanced Administration System (AAS). This system is also called Entitled Software Support (ESS).
  2. Untar the tar.gz file by running this command.
    gunzip -c file_name.tar.gz | tar -xvf
    -
  3. Unzip and untar the visual-insights-aas-arch-1.2.0.0.tar.gz file (where arch is x86 or ppc depending on the installation platform) by running this command: 
    gunzip -c file_name.tar.gz | tar -xvf -
    The install files are extracted to visual-insights-aas-arch-1.2.0.0/, where arch is x86 or ppc, depending on your platform.
  4. Decompress the product tar file and run the installation command for the platform you are installing on:
    RHEL
    sudo yum install ./<file_name>.rpm
    Ubuntu
    sudo dpkg -i ./<file_name>.deb
  5. Load the IBM Visual Insights images from the directory that contains the extracted tar file. The user running the script must have Docker privileges:
    sudo /opt/ibm/vision/bin/load_images.sh -f ./file_name.tar
    Note: The installation process can take some time to complete.
  6. (RHEL only) Open ports for the firewall to access IBM Visual Insights by running this script: 
    sudo /opt/ibm/vision/sbin/firewall.sh
  7. After the installation is complete, you can start IBM Visual Insights by running this script: 
    sudo /opt/ibm/vision/bin/vision-start.sh
    A user named admin is created with a password of passw0rd. For instructions to change these values, see Managing users.
    Note: The startup script will modify ownership and permissions on /opt/ibm/vision/volume so that the containers can run under a non-root ID and access the data.

    You must read and accept the license agreement that is displayed before you can use IBM Visual Insights.

    It can take several minutes to start IBM Visual Insights. To check the status of the startup process, run this script: 
    sudo /opt/ibm/vision/bin/helm.sh status vision
    In the output from the helm.sh status vision script, you can verify which IBM Visual Insights components are available by locating the Deployment section and identifying that the AVAILABLE column has a value of 1 for each component. The following is an example of the output from the helm.sh status vision script that shows all components are available:
    user@system:~$ /opt/ibm/vision/bin/helm.sh status vision
LAST DEPLOYED: Mon Feb 17 19:25:40 2020
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1beta1/Ingress
NAME        HOSTS  ADDRESS  PORTS  AGE
vision-ing  *      80       6d21h
==> v1/Pod(related)
NAME                                        READY  STATUS   RESTARTS  AGE
vision-elasticsearch-777f6bcc6c-5xvlg       1/1    Running  0         17h
vision-fpga-device-plugin-bm8qx             1/1    Running  0         17h
vision-keycloak-f57979785-fpw8q             1/1    Running  0         17h
vision-logstash-f8cc6fcc6-rhqtc             1/1    Running  0         17h
vision-mongodb-79b9d7977c-2twtb             1/1    Running  0         17h
vision-postgres-6f4788c594-gxcjp            1/1    Running  0         17h
vision-service-799c94f575-2cr48             1/1    Running  0         4h34m
vision-taskanaly-67745bc59f-qd225           1/1    Running  0         17h
vision-ui-774d989b47-2swvb                  1/1    Running  0         17h
vision-video-microservice-6fc86b5866-s8x44  1/1    Running  0         17h
==> v1/Secret
NAME            TYPE    DATA  AGE
vision-secrets  Opaque  4     6d21h
==> v1/ConfigMap
NAME           DATA  AGE
vision-config  53    6d21h
==> v1/PersistentVolumeClaim
NAME             STATUS  VOLUME       CAPACITY  ACCESS MODES  STORAGECLASS  AGE
vision-data-pvc  Bound   vision-data  40Gi      RWX           6d21h
==> v1/Service
NAME                       TYPE       CLUSTER-IP   EXTERNAL-IP  PORT(S)            AGE
vision-elasticsearch       ClusterIP  10.10.0.169  <none>       9200/TCP,9300/TCP  6d21h
vision-keycloak            ClusterIP  10.10.0.30   <none>       8080/TCP,8443/TCP  6d21h
vision-logstash            ClusterIP  10.10.0.198  <none>       9600/TCP           6d21h
vision-mongodb             ClusterIP  10.10.0.173  <none>       27017/TCP          6d21h
vision-postgres            ClusterIP  10.10.0.201  <none>       5432/TCP           6d21h
vision-service             ClusterIP  10.10.0.85   <none>       9080/TCP           6d21h
vision-taskanaly           ClusterIP  10.10.0.44   <none>       5000/TCP           6d21h
vision-ui                  ClusterIP  10.10.0.41   <none>       8080/TCP           6d21h
vision-video-microservice  ClusterIP  10.10.0.216  <none>       38080/TCP          6d21h
==> v1beta1/DaemonSet
NAME                       DESIRED  CURRENT  READY  UP-TO-DATE  AVAILABLE  NODE SELECTOR  AGE
vision-fpga-device-plugin  1        1        1      1           1          <none>         17h
==> v1/Deployment
NAME                       DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
vision-elasticsearch       1        1        1           1          17h
vision-keycloak            1        1        1           1          17h
vision-logstash            1        1        1           1          17h
vision-mongodb             1        1        1           1          17h
vision-postgres            1        1        1           1          17h
vision-service             1        1        1           1          17h
vision-taskanaly           1        1        1           1          17h
vision-ui                  1        1        1           1          17h
vision-video-microservice  1        1        1           1          17h
NOTES:
Find the Visual Insights UI URL by running the following commands:
export NODE_IP=$(kubectl get ing vision-ing --namespace default -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
echo https://${NODE_IP}/vision/

    After the application startup has completed and the user interface is available, it can be accessed at https://hostname/visual-insights/, where hostname is the system on which you installed IBM Visual Insights.

  8. Install any available fix packs. For instructions see Getting fixes from Fix Central.

Install IBM Visual Insights trial mode

  1. Go to the IBM Visual Insights Trial download site, then download the .tar file and the .rpm files as instructed.
  2. Unzip and untar the product tar file, and run the installation command for the platform you are installing on.
    RHEL
    sudo yum install ./<file_name>.rpm
    Ubuntu
    sudo dpkg -i ./<file_name>.deb
    The install files are extracted to visual-insights-arch-1.2.0.0-ppa, where arch is x86 or ppc, depending on your platform.
  3. (Optional) Verify the downloaded tar file by following the instructions in this topic: Verify the downloaded tar file.
  4. Load the IBM Visual Insights images from the directory that contains the extracted tar file. The user running the script must have Docker privileges:
    sudo /opt/ibm/vision/bin/load_images.sh -f ./file_name.tar
    Note: The installation process can take some time to complete.
  5. (RHEL only) Open ports for the firewall to access IBM Visual Insights by running this script: 
    sudo /opt/ibm/vision/sbin/firewall.sh
  6. After the installation is complete, you can start IBM Visual Insights by running this script: 
    sudo /opt/ibm/vision/bin/vision-start.sh
    A user named admin is created with a password of passw0rd. For instructions to change these values, see Managing users.
    Note: The startup script will modify ownership and permissions on /opt/ibm/vision/volume so that the containers can run under a non-root ID and access the data.

    You must read and accept the license agreement that is displayed before you can use IBM Visual Insights.

    It can take several minutes to start IBM Visual Insights. To check the status of the startup process, run this script: 
    sudo /opt/ibm/vision/bin/helm.sh status vision
    In the output from the helm.sh status vision script, you can verify which IBM Visual Insights components are available by locating the Deployment section and identifying that the AVAILABLE column has a value of 1 for each component. The following is an example of the output from the helm.sh status vision script that shows all components are available:
    user@system:~$ /opt/ibm/vision/bin/helm.sh status vision
LAST DEPLOYED: Mon Feb 17 19:25:40 2020
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1beta1/Ingress
NAME        HOSTS  ADDRESS  PORTS  AGE
vision-ing  *      80       6d21h
==> v1/Pod(related)
NAME                                        READY  STATUS   RESTARTS  AGE
vision-elasticsearch-777f6bcc6c-5xvlg       1/1    Running  0         17h
vision-fpga-device-plugin-bm8qx             1/1    Running  0         17h
vision-keycloak-f57979785-fpw8q             1/1    Running  0         17h
vision-logstash-f8cc6fcc6-rhqtc             1/1    Running  0         17h
vision-mongodb-79b9d7977c-2twtb             1/1    Running  0         17h
vision-postgres-6f4788c594-gxcjp            1/1    Running  0         17h
vision-service-799c94f575-2cr48             1/1    Running  0         4h34m
vision-taskanaly-67745bc59f-qd225           1/1    Running  0         17h
vision-ui-774d989b47-2swvb                  1/1    Running  0         17h
vision-video-microservice-6fc86b5866-s8x44  1/1    Running  0         17h
==> v1/Secret
NAME            TYPE    DATA  AGE
vision-secrets  Opaque  4     6d21h
==> v1/ConfigMap
NAME           DATA  AGE
vision-config  53    6d21h
==> v1/PersistentVolumeClaim
NAME             STATUS  VOLUME       CAPACITY  ACCESS MODES  STORAGECLASS  AGE
vision-data-pvc  Bound   vision-data  40Gi      RWX           6d21h
==> v1/Service
NAME                       TYPE       CLUSTER-IP   EXTERNAL-IP  PORT(S)            AGE
vision-elasticsearch       ClusterIP  10.10.0.169  <none>       9200/TCP,9300/TCP  6d21h
vision-keycloak            ClusterIP  10.10.0.30   <none>       8080/TCP,8443/TCP  6d21h
vision-logstash            ClusterIP  10.10.0.198  <none>       9600/TCP           6d21h
vision-mongodb             ClusterIP  10.10.0.173  <none>       27017/TCP          6d21h
vision-postgres            ClusterIP  10.10.0.201  <none>       5432/TCP           6d21h
vision-service             ClusterIP  10.10.0.85   <none>       9080/TCP           6d21h
vision-taskanaly           ClusterIP  10.10.0.44   <none>       5000/TCP           6d21h
vision-ui                  ClusterIP  10.10.0.41   <none>       8080/TCP           6d21h
vision-video-microservice  ClusterIP  10.10.0.216  <none>       38080/TCP          6d21h
==> v1beta1/DaemonSet
NAME                       DESIRED  CURRENT  READY  UP-TO-DATE  AVAILABLE  NODE SELECTOR  AGE
vision-fpga-device-plugin  1        1        1      1           1          <none>         17h
==> v1/Deployment
NAME                       DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
vision-elasticsearch       1        1        1           1          17h
vision-keycloak            1        1        1           1          17h
vision-logstash            1        1        1           1          17h
vision-mongodb             1        1        1           1          17h
vision-postgres            1        1        1           1          17h
vision-service             1        1        1           1          17h
vision-taskanaly           1        1        1           1          17h
vision-ui                  1        1        1           1          17h
vision-video-microservice  1        1        1           1          17h
NOTES:
Find the Visual Insights UI URL by running the following commands:
export NODE_IP=$(kubectl get ing vision-ing --namespace default -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
echo https://${NODE_IP}/vision/

    After the application startup has completed and the user interface is available, it can be accessed at https://hostname/visual-insights/, where hostname is the system on which you installed IBM Visual Insights.