Installing IBM Visual Insights with IBM Cloud Private

If you have more than one IBM® Power Systems server available, you can use IBM Cloud® Private 3.1.0 or later to install a single instance of IBM Visual Insights that has access to all the Power Systems GPUs across the entire cluster.

If you have only a single Power Systems server and do not have an existing IBM Cloud Private environment, you should use the IBM Visual Insights stand-alone process. For more information, see the Installing IBM Visual Insights stand-alone topic.

To install IBM Visual Insights with IBM Cloud Private, complete the following steps:
Notes:
  • If IBM Cloud Private is already installed and configured in your environment, you can go to step 4.
  • The links to IBM Cloud Private go to the 3.1.0 Knowledge Center. To go to a different version, click the link, then click Change version.
  1. Install IBM Cloud Private. For more information, see the Installing IBM Cloud Private topic.
  2. Install the IBM Cloud CLI. For more information, see the Install IBM Cloud CLI topic.
  3. Authenticate to your master node in your IBM Cloud Private environment. For more information, see the Configuring authentication for the Docker CLI topic.
    To log in to the IBM Cloud Private cluster, run the following command: 
    cloudctl login -a https://<cluster-domain-name>:8443/ --skip-ssl-validation
  4. Set up your system to install your IBM Cloud Private deployment into a non-default namespace. It is recommended that you do not install into the default namespace for security reasons.
    Important: Install each distinct deployment of IBM Cloud Private into a unique namespace.
    1. Create an appropriate ClusterRoleBinding to enable IBM Visual Insights to query Kubernetes. To create this, copy the below text into a crb.yaml file, where CustomNamespace is your custom namespace name:
      apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: CustomNamespace-crb
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
  -
    kind: ServiceAccount
    name: default
    namespace: CustomNamespace
    2. Run the following command: 
      kubectl create -f crb.yaml
  5. Download the appropriate tar file from IBM Passport Advantage.
  6. (Optional) Verify the downloaded tar file by following the instructions in this topic: Verify the downloaded tar file.
  7. Untar the visual-insights-<architecture>-<version_number>-ppa.tar tar file. It contains install packages for the standalone product, as well as the tar file with the containers that must be loaded for the IBM Cloud Private installation.
  8. To make IBM Visual Insights available in the IBM Cloud Private catalog, run the following command:
    cloudctl catalog load-archive --archive file_name.tar --registry <icp full host name>:8500/<namespace>
    Where:
    --registry <value>
    Lets you specify the docker registry that the images will be pushed to.
    Example:
    mycluster-icp:8500/<namespace>
    --clustername <cluster_CA_domain>
    Lets you specify the certificate authority (CA) domain. If you did not specify a CA domain, the default value is mycluster.icp.
  9. Review the Chart README for IBM Visual Insights carefully. It documents prerequisites, requirements, and limitations of IBM Visual Insights in IBM Cloud Private.
  10. Verify that you have a minimum of 40 GB of persistent storage. If your IBM Cloud Private installation has dynamic provisioned storage, you can use it for your 40 GB of persistent storage. To manually create persistent volumes in IBM Cloud Private, see the Creating a Persistent Volume topic. After you create the persistent volume, you must make the volume sharable across all nodes in the cluster.
    Note: Do not use HostPath for the persistent storage unless you have only one node in your cluster. See Creating a Persistent Volume and Creating a hostPath PersistentVolume in the IBM Cloud Private documentation for details.
  11. Important: You must run the following commands to set up the persistent volume. This is required because the containers run under the non-root id 1979:
    AIV_USER=1979
VOL_DIR=<persistent_volume_path>
mkdir -p ${VOL_DIR}/data ${VOL_DIR}/run/logstash ${VOL_DIR}/run/elasticsearch ${VOL_DIR}/run/mongodb ${VOL_DIR}/run/pgsql
chown ${AIV_USER}:${AIV_USER} ${VOL_DIR} ${VOL_DIR}/run
chown -R ${AIV_USER}:${AIV_USER} ${VOL_DIR}/data
chown 1000:1000 ${VOL_DIR}/run/logstash ${VOL_DIR}/run/elasticsearch
chown 999 ${VOL_DIR}/run/mongodb
chown 999 ${VOL_DIR}/run/pgsql
  12. To install IBM Visual Insights from the IBM Cloud Private catalog, from the navigation menu select Catalog > Helm Charts.
  13. In the search box, enter vision and click visual-insights. Review the information.
  14. Click Configure and enter information for the Release name and the Namespace fields. The default user name is admin and the default password is passw0rd. For instructions to change these values, see Managing users. For information about namespaces, see Namespaces in the IBM Cloud Private Knowledge Center.
  15. Click Install.

    It can take several minutes for the application to be deployed and the user interface to be made available. When the application startup has completed, it can be accessed using the URL https://proxyhost/visual-insights-RELEASE/, where proxyhost is the host name of your IBM Cloud Private proxy server, and RELEASE is the name you specified in the Release name field when you deployed the Helm chart.

  16. For information about accessing IBM Visual Insights, see Logging into IBM Visual Insights.
Important: NFS volumes should have the no_root_squash flag set in /etc/exports: 
/var/nfs *(rw,no_root_squash,no_subtree_check)