By pulling, downloading and/or using the program you agree to be bound by the end-user license at the following link: http://www14.software.ibm.com/cgi-bin/weblap/lap.pl?li_formnum=L-CKIE-BPARN8&title=IBM%20Visual%20Insights%201.2.0.1%20Trial
It is required to register with IBM before pulling, downloading and/or using the program. Link to register.
IBM Visual Insights makes computer vision with deep learning more accessible to business users. The software includes an intuitive toolset that empowers subject matter experts to label, train, and deploy deep learning vision models, without coding or deep learning expertise.
Designed for business users, the platform provides auto labelling and data augmenting capabilities to accelerate labelling of volumes of images & videos and even work with limited datasets. Bundled with several deep learning frameworks, models for training classifiers, object detectors, image segmentation and Action recognition are core features of the software. Once the models are trained, IBM Visual Insights lets you export the models to iOS devices, NVIDIA TX2/Nano and even to the cloud of your choice.
Before running the containers for IBM Visual Insights Evaluation Edition, please ensure that your system meets the following HW and SW requirements.
Ensure Helm 2 / Tiller is available in your cluster.
Ensure an Ingress is configured for your cluster.
Create a namespace for the application. This is optional, but recommended. Subsequent commands will use CustomNamespace
namespace as an example. Replace this with your own custom namespace.
kubectl create namespace CustomNamespace
kind: ServiceAccount
name: default
namespace: CustomNamespace
Apply the ClusterRoleBinding:
kubectl create -f crb.yaml
Verify that you have a minimum of 40 GB of persistent storage. If your kubernetes cluster has dynamic provisioned storage, you can use it for your persistent storage. To manually create persistent volumes, see the Kubernetes Storage Topics to learn how to work with persistent volumes. After you create the persistent volume, you must make the volume sharable across all nodes in the cluster.
IMPORTANT: Containers within IBM Visual Insights run as non-root users for security reasons. You must set appropriate permissions in order for the application to start up correctly.
AIV_USER=1979
VOL_DIR=/insert/persistent/volume/path/here
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
Create an appropriate imagePullSecret
to allow IBM Visual Insights to dynamically pull container images from NGC as needed. Be sure to associate the secret with the namespace you created earlier. Refer to the Kubernetes documentation for details about how to pull an image from a private registry.
#Note: This is a simple example. Your cluster may be different. Please note the '$oauthtoken' below. This is to provide NGC with the literal '$oauthtoken' username beginning with a dollar sign ($) expected to log in.
kubectl create secret docker-registry --namespace CustomNamespace ngc --docker-server=nvcr.io --docker-username='$oauthtoken' --docker-password=YOUR-NGC-TOKEN --docker-email=o@auth.com
kubectl patch serviceaccount --namespace CustomNamespace default -p '{"imagePullSecrets": [{"name": "ngc"}]}'
# where: YOUR-NGC-TOKEN is your API token to access the NGC private registry
Fetch the helm chart per the helm pull
command provided by NGC above.
Deploy the chart with variables set based on your processor architecture (POWER9 or x86):
For x86 architecture with NVIDIA GPUs (amd64 or x86_64):
helm install --name trial --namespace CustomNamespace ./ibm-visual-insights-prod-2.0.0.tgz --set image.pullPolicy=IfNotPresent --set image.releaseTag=1.2.0.0 --set image.repoPrefix=nvcr.io/partners/ibm
For IBM Power architecture with NVIDIA GPUs (ppc64el or ppc64le or POWER):
helm install --name trial --namespace CustomNamespace ./ibm-visual-insights-prod-2.0.0.tgz --set image.pullPolicy=IfNotPresent --set image.releaseTag=1.2.0.0 --set image.repoPrefix=nvcr.io/partners/ibmpower
Wait for all pods to become ready, then log in via your cluster ingress. By default, the chart will create an ingress-controller
that follows the visual-insights-HELMRELEASENAME
pattern (e.g. /visual-insights-trial
).
helm status trial
Log in to the application at https://ingress.hostname/visual-insights-trial . IMPORTANT: If you changed the chart deployment name from trial
to another value , log in at https://ingress.hostname/visual-insights-HELMRELEASENAME
The default username/password admin / passw0rd
.
Change the default admin password. Note that you may not create new users in the Trial edition of this software.
kubectl run --rm -i --restart=Never usermgt --namespace CustomNamespace --image=nvcr.io/partners/ibm/vision-usermgt:1.2.0.0 -- modify --user admin --password INSERT-PASSWORD-HERE --release trial
Ask us your questions on our forum.