Hardware requirements and supported architectures
View the hardware, architecture, and platform requirements for a deployment of IBM® Cloud Pak for Network Automation Orchestration Manager.
Supported architectures and platforms
You can install IBM Cloud Pak for Network Automation Orchestration Manager on the following combinations of architectures and platforms:
Architecture | Platform |
---|---|
x86_64 | Red Hat® OpenShift® Container Platform 4.16, 4.15, or 4.14 |
Hardware requirements
Profile name | Usage |
---|---|
Starter | A concise configuration designed to handle starter workloads. Starter configurations are typically used for proofs of concept or experimentation with the core product. |
Production | A production-grade configuration that includes security, high availability, sizing, and scale considerations. Production configurations are intended for real world use cases. Typically, production configurations require additional system and storage resources from a starter configuration. |
The tables show the minimum resources for production and starter configurations. You might need extra resources to support your specific workload. Work with your IBM Sales representative to get a more accurate sizing based on your expected workload.
For an active-active configuration, the minimum hardware requirements apply to each cluster in the configuration.
- Production configuration
-
The following table lists the minimum hardware resources that you need to install a single instance of IBM Cloud Pak for Network Automation Orchestration Manager in a production configuration. The resources must be spread across a minimum of three worker nodes.
A blank value in the table indicates that no additional hardware resource is needed for that component.
Table 2. Minimum hardware requirements for a production instance of IBM Cloud Pak for Network Automation Orchestration Manager. Component vCPU Memory (GiB RAM) Disk Space (TB) IBM Cloud Pak for Network Automation Orchestration Manager - base 1. 26 54 1.6 Site Planner 2. 3 3 Total 32 vCPUs 60 GiB 1.6 TB 1. Includes the resources that are required for IBM Cloud Pak foundational services. 2. Site Planner is not installed by default. You can reduce the CPU, memory, and disk space requirements by the corresponding amounts if you do not install this component.
- Starter configuration
-
The following table lists the minimum hardware resources that you need to install a single instance of IBM Cloud Pak for Network Automation Orchestration Manager in a starter configuration. The resources must be spread across a minimum of three worker nodes.
A blank value in the table indicates that no additional hardware resource is needed for that component.
Table 3. Minimum hardware requirements for a starter instance of IBM Cloud Pak for Network Automation Orchestration Manager. Component vCPU Memory (GiB RAM) Disk Space (TB) IBM Cloud Pak for Network Automation Orchestration Manager - base 1. 15 30 1.6 Site Planner 2. 1 1 Total 17 vCPUs 32 GiB 1.6 TB 1. Includes the resources that are required for IBM Cloud Pak foundational services. 2. Site Planner is not installed by default. You can reduce the CPU, memory, and disk space requirements by the corresponding amounts if you do not install this component.
- Storage requirements for installing with a private container registry
- If you use a private container registry to deploy the IBM Cloud Pak® images to your cluster, ensure that you reserve enough storage space for the
images. For example, you might use a private container registry if your OpenShift Container
Platform cluster is air-gapped.
The images require 124 GB of storage space. Ensure that you reserve the storage space in both the local registry and the bastion host.
Cluster requirements for installing on AWS
You can deploy a self-managed Red Hat OpenShift Container Platform cluster on Amazon Web Services (AWS). You can then install IBM Cloud Pak for Network Automation on the cluster.
If you want to
use an AWS cluster in this way, the minimum size for compute node instances is
m5.2xlarge
. You must also specify 3 or more compute nodes.