Hardware and software requirements

Learn more about the hardware and software requirements to install IBM® Engineering Requirements Quality Assistant (RQA) in your private network by using the OpenShift® Container Platform (OCP).

Software requirements

Make sure that the following applications are deployed in your private network:

DOORS® Next: See Installing the Requirements Management (RM) application. The supported DOORS Next versions are 6.0.6 or later.
Jazz® Authorization Server: See Installing Jazz Team Server.
Note: You need to deploy the Jazz Authorization Server if you use the Jazz Authorization Server authentication that is liberty-based authentication. If you use the non-liberty-based authentication, such as Cloud Identity, Jazz Authorization Server deployment is not required.
IBM Common Licensing Server: See Installing IBM Common Licensing and IBM Common Licensing overview. The supported IBM Common Licensing versions are 8.1.6.x and the fix packs. The IBM Common Licensing Server also needs to be configured so that users can check out the tokens before they analyze the requirements. Complete the following steps to configure the IBM Common Licensing Server:
RQA supports the latest OpenShift Container Platform (OCP): To know about the supported versions, see Life Cycle Dates. For more information about OCP installation, see Installing OpenShift Container Platform documentation.
Note: RQA becomes inoperable after you upgrade to the OCP version 4.8.x. See https://www.ibm.com/support/pages/node/6485201.

Cluster sizing

For OpenShift cluster size recommendations for RQA small and medium deployments, see HA cluster configuration.

Storage requirements for Redis operators

To install the Redis operators, you need the OpenShift storage setup.

Redis operator:
- Disk: 1 GB
- Storage class: The storage class must support:
  - Dynamic provisioning
  - ReadWriteOnce or ReadWriteMany semantics
  - POSIX filesystem compatibility. For example, not NFS.
  The Redis operator is validated for ibmc-block-* and OpenShift Container Storage.
- Filesystem permissions: RQA uses the following security context that defines the filesystem permissions to work with dynamically provisioned storage:
```
fsGroup:
  type: RunAsAny
supplementalGroups:
  type: RunAsAny
```