Skip to content

IBM Automation Decision Services Deployment Architecture

Abstract

This document describes the deployment of IBM Automation Decision Services on the RedHat OpenShift Kubernetes Service on IBM Cloud, known as ROKS, on Virtual Private Cloud (VPC) Gen 2 infrastructure.

PM-topology

As we can see in the topology above, the RedHat OpenShift cluster has been deployed on a MultiZone Region (MZR) data center with three availability zones where Virtual Private Cloud Gen 2 is available.

Note

IBM Automation Decision Services requires ReadWriteMany (RWX) storage.

In order to offer Read Write Many (RWX) storage for the applications running on our RedHat OpenShift cluster, we need to make OpenShift Data Foundation available in our RedHat OpenShift cluster.

OpenShift Data Foundation (ODF) is a storage solution that consists of open source technologies Ceph, Noobaa, and Rook. ODF allows you to provision and manage File, Block, and Object storage for your containerized workloads in Red Hat® OpenShift® on IBM Cloud™ clusters. Unlike other storage solutions where you might need to configure separate drivers and operators for each type of storage, ODF is a unified solution capable of adapting or scaling to your storage needs.

The IBM Automation Decision Service runtime requires a MongoDB. For development systems, an embedded MongoDB is provided, however for Production usage an external MongoDB instance is required. In the deployment topology above we are using MongoDB as-a-service which is provided by the Cloud provider (in this case IBM Cloud).

The Business Automation Navigator requires a Postgres DB. In the deployment topology above we are using Postgres as-a-service which is provided by the Cloud provider (in this case IBM Cloud).

The User Management Service requires LDAP. For development systems, an embedded LDAP is provided, however for Production usage an external LDAP instance is required. In the deployment topology above we are using the VSIs to host the LDAP implementation, however this may not be required in an environment where an LDAP already exists.