Training with local data
To learn about cloud native analytics, you can install a local data set. Learn how to install and load your local data, train the system, and see the results.
Before you begin
- The ea-events-tooling container is installed
by the operator. It is not started as a pod, and contains scripts to install data on the system,
which can be run with the
kubectl run
command. - Find the values of image and
image_tag for the ea-events-tooling container, from the
output of the following
command:
Where <release_name> is the custom resource release name of your cloud deployment. For example, in the following output, image iskubectl get noi <release_name> -o yaml | grep ea-events-tooling
ea-events-tooling
, and image_tag is2.0.14-20200120143838GMT
.kubectl get noi <release_name> -o yaml | grep ea-events-tooling --env=CONTAINER_IMAGE=image-registry.openshift-image-registry.svc:5000/default/ea-events-tooling:2.0.14-20200120143838GMT \ --image=image-registry.openshift-image-registry.svc:5000/default/ea-events-tooling:2.0.14-20200120143838GMT \
Hybrid deployment: For a hybrid deployment, run the following command:
Where <release_name> is the custom resource release name of your hybrid deployment.kubectl get noihybrid <release_name> -o yaml | grep ea-events-tooling
IBM® Netcool® for AIOps deployment: For an online or offline deployment (airgap) of Netcool Operations Insight® with IBM Cloud Pak for AIOps, find the values of image and image_tag from the noi-operator CSV file. Run the following command:
Where <noi-operator> is the noi-operator CSV file name.oc get csv <noi-operator> -o yaml | grep olm.relatedImage.NOI_ea-events-tooling: | awk -F ': ' '{print $2}'
- Determine the HTTP username and password from the secret that has
systemauth in the name, by running the following
command:
kubectl get secret release_name-systemauth-secret -o yaml
- If you created your own docker registry
secret, then patch your
service
account.
Where noi-registry-secret is the name of the secret for accessing the Docker repository.kubectl patch serviceaccount default -p '{"imagePullSecrets": [{"name": "noi-registry-secret"}]}'
Note: As an alternative to patching the default service account with image pull secrets, you can add the following option to each kubectl command that you issue:--overrides='{ "apiVersion": "v1", "spec": { "imagePullSecrets": [{"name": "evtmanager-registry-secret"}] } }'
About this task
You can use scripts in the ea-events-tooling container to install local data on the system. To complete this task, run the filetoingestionservice.sh, getTimeRange.sh, runTraining.sh, createPolicy.sh, and filetonoi.sh scripts. The scripts load local data to the ingestion service, train the system for seasonality and temporal events, create live seasonal policies and suggest temporal policies, and load the data into cloud native analytics.
June 2020 #4638