Use these instructions to install IBM
Netcool Operations Insight®, with the
Container Application Software for Enterprises (CASE) and the Red Hat® OpenShift® Operator Lifecycle
Manager (OLM) user interface (UI). This installation method is similar to installing with the OLM
UI, but CASE creates the Netcool®
Operations Insight catalog source
and installs the Netcool
Operations Insight Operator for
you.
Procedure
Get the Netcool
Operations Insight
CASE.
-
Download and install IBM® Cloud Pak CLI (cloudctl) version 3.8.0 from the cloud-pak-cli
GitHub repository . Version 3.8.0 is the maximum supported version for installing Event
Manager.
cloudctl
verifies the integrity of the
Netcool
Operations Insight CASE's digital
signature by default. If you want to verify the
cloudctl
binary, follow the
instructions in
Check Certificate/Key Validity . Extract the
cloudctl
binary, give it executable permissions, and ensure that it is in your
PATH.
- Download the Netcool
Operations Insight CASE bundle
(
ibm-netcool-prod
) to your Red Hat OpenShift cluster.
cloudctl case save --case ibm-netcool-prod --outputdir destination_dir --repo https://raw.githubusercontent.com/IBM/cloud-pak/master/repo/case
Where destination_dir is a directory of your choosing, for example
/tmp/cases.
- Extract the Netcool
Operations Insight CASE
bundle.
tar -xvf destination_dir/ibm-netcool-prod*.tgz
where
destination_dir is the directory that you downloaded the CASE bundle into in the
previous step.
Install the Netcool
Operations Insight Catalog and
Operator.
- Install the catalog by using CASE.
cloudctl case launch \
--case ibm-netcool-prod \
--namespace namespace \
--inventory noiOperatorSetup \
--action install-catalog
Where namespace is the custom namespace to be used for your
deployment, that you created when you prepared your cluster.
- Verify the Netcool
Operations Insight catalog
source.
From the Red Hat OpenShift OLM UI, go to , and then select the
OperatorHub configuration resource under the Global
Configuration tab. Verify that the ibm-noi-catalog catalog source is
present.
- Install the Netcool
Operations Insight operator by using
CASE.
cloudctl case launch \
--case ibm-netcool-prod \
--namespace namespace \
--inventory noiOperatorSetup \
--action install-operator \
--args "--secret noi-registry-secret"
Where
-
namespace is the custom namespace to be used for your deployment.
- noi-registry-secret is the secret for accessing the IBM Entitled Registry that you created when you prepared your cluster.
- Verify the status of IBM Cloud Pak for Watson™ AIOps Event
Manager.
From the Red Hat OpenShift OLM UI, go to , and verify that the status of IBM Cloud Pak for Watson AIOps Event
Manager is Succeeded.
Create a Netcool
Operations Insight
instance.
-
From the Red Hat OpenShift
OLM UI, go to , and select IBM Cloud Pak for Watson AIOps Event
Manager. Under ,
select
Create Instance.
-
From the Red Hat OpenShift
OLM UI, use the YAML view or the Form view to configure the properties for the Netcool Operations Insight deployment.
For more information about configurable properties for a cloud only deployment, see Cloud operator properties.
Note: Ensure that the name of the Netcool Operations Insight instance
does not exceed 10 characters.
-
Select Create.
-
Under the All Instances tab, a Netcool Operations Insight instance
appears.
Note:
- Changing an existing deployment from a Trial deployment type to a Production deployment type is
not supported.
- Changing an instance's deployment parameters in the Form view is not supported post
deployment.
- If you update custom secrets in the OLM console, the crypto key is corrupted and the command to
encrypt passwords does not work. Update custom secrets only with the CLI. For more information about
storing a certificate as a secret, see https://www.ibm.com/docs/en/SS9LQB_1.1.10/LoadingData/t_asm_obs_configuringsecurity.html
What to do next
- To enable or disable a feature or observer after installation edit the Netcool Operations Insight instance by
running the command:
oc edit noi <noi-instance-name>
Where
<noi-instance-name> is the name of the deployment that you want to change.
You can then select to enable or disable the feature or observer. When you disable features
postinstallation , the resource is not automatically deleted. To find out whether the feature is
deleted, you must check the asm-operator
log.