Installing on a hybrid architecture

Edit online

Use these instructions to prepare and install a hybrid deployment, which is composed of cloud native components on Red Hat® OpenShift® Container Platform, and an on-premises Operations Management installation.

Click here to download the Netcool Operations Insight Hybrid Installation Guide.

When you install cloud native components on Red Hat OpenShift Container Platform, all of the components are automatically deployed as pods running within the cluster. The deployment of pods across worker nodes is managed by Red Hat OpenShift Container Platform. Pods for a service are deployed on nodes that meet the specification and affinity rules for the service, and are orchestrated by Kubernetes.

The hybrid deployment configuration uses the power of Netcool® Operations Insight®s cloud native components, without the need to deploy the full Netcool Operations Insight on Red Hat OpenShift Container Platform solution. You can deploy only the cloud native components from the Netcool Operations Insight package on Red Hat OpenShift Container Platform, and connect them to an on-premises Operations Management installation. The cloud native components provide cloud native event analytics, cloud native event integrations, runbook automations, and optionally topology management. The on-premises Operations Management installation provides the ObjectServer and WebGUI(s).

Figure 1 displays the multitiered architecture of a hybrid Netcool Operations Insight deployment.
Figure 1. Multitiered architecture of a hybrid Netcool Operations Insight deployment.
Multitiered architecture of a hybrid deployment of Netcool Operations Insight
The hybrid solution can be deployed in high availability disaster recovery (HADR) mode, or in a non-HADR mode.

  • HADR mode: A HADR hybrid deployment is composed of cloud native components on Red Hat OpenShift Container Platform and an on-premises Operations Management installation that has multiple WebGUI instances to provide redundancy. For more information, see Setting up a high availability disaster recovery hybrid deployment.

    The advanced.antiAffinity parameter is set to false by default. To prevent primary and backup server pods from being installed on the same worker node, set this option to true. When enabled, anti-affinity is configured for preferredDuringSchedulingIgnoredDuringExecution. For more information, see Hybrid operator properties and Cloud operator properties.

  • Non-HADR mode: A non-HADR hybrid deployment is composed of cloud native components on Red Hat OpenShift Container Platform and an on-premises Operations Management installation that has only one WebGUI.
Note: Integration with on-premises IBM® Agile Service Manager is not supported for hybrid deployments.