Prerequisites for installing the server software on IBM® Red Hat OpenShift
You must complete certain tasks before you install Rational® Test Automation Server on the Red Hat OpenShift platform.
The following sections describe each prerequisite in detail:
Entitlement key
You must copy the Entitlement key from the Container software library to pull the images that are used by the server software. For more information, refer to Creating an API key.
Red Hat OpenShift platform
You must set up the Red Hat OpenShift platform, and then install the following components in your IT infrastructure:
-
Red Hat OpenShift Container Platform (OCP). For more information, refer to the Installing section in the Red Hat OpenShift documentation.
-
Dynamic Volume Provisioning that supports ReadWriteOnce (RWO) and ReadWriteMany (RWX) access modes. For more information, refer to the Dynamic provisioning section in the Red Hat OpenShift documentation.
-
Optional: Jaeger operator to trace test logs and Jaeger-based reports when you run tests. For more information, refer to Installing the Operators.
-
Optional: You can configure the Red Hat OpenShift software-defined networking (SDN) to provide a unified cluster network that enables the communication between pods across the Red Hat OpenShift Container Platform cluster. The default installation process includes the NetworkPolicy resources and these resources are acted upon only if you configure the SDN appropriately. For more information, refer to the Red Hat OpenShift SDN default CNI network provider section in the Red Hat OpenShift documentation.
oc login -u kubeadmin -p {password} https://api.{openshift-cluster-dns-name}:6443
Mandatory software
You must install the following software on Red Hat OpenShift:
-
Helm. For more information, refer to the Installing a Helm chart on Red Hat OpenShift Container Platform cluster section in the Red Hat OpenShift documentation.
-
Red Hat OpenShift CLI. For more information, refer to the Getting started with the CLI section in the Red Hat OpenShift documentation.
Persistent storage
Rational® Test Automation Server requires persistent storage in addition to the minimum resources required by the cluster. Depending on the workload, you might require additional persistent storage.
The default configuration creates the PersistentVolumeClaim that dynamically provision the PersistentVolume. The following table lists the PersistentVolumeClaim, its size, and access mode during the configuration:
PersistentVolumeClaim | Size | Access Mode | Content |
---|---|---|---|
data-{my-rtas}-postgresql-0 | 26 GB |
ReadWriteOnce CLI Abbreviation: RWO |
User data used by services |
data-{my-rtas}-rabbitmq-0 | 8 GB | RWO | Notifications between services |
data-{my-rtas}-results-0 | 8 GB | RWO | Reports |
data-{my-rtas}-tam-0 | 32 GB | RWO | Cloned git repositories |
data-{my-rtas}-userlibs-0 | 1 GB |
ReadWriteMany CLI Abbreviation: RWX |
User-provided third-party libraries and extensions |
Service virtualization usage metrics
You must perform the following tasks so that Rational® Test Automation Server shows the correct usage of service virtualization metrics:
-
Create the cluster-monitoring-config ConfigMap object to configure the Red Hat OpenShift Container Platform (OCP) monitoring stack, if the ConfigMap does not exist.
For more information about creating a cluster monitoring config map, based on the version of OCP that you use, refer to Creating a cluster monitoring config map.
-
Enable the user workload monitoring services in the Red Hat OpenShift cluster to show the service virtualization usage metrics in Rational® Test Automation Server.
For more information about the enabling monitoring of your services, based on the version of OCP that you use, refer to Enabling monitoring of your services