System requirements
Review the minimum system requirements for setting up and running the middleware Content Runtime within a virtual machine.
- Hardware requirements
- Supported operating systems and platforms
- Network requirements
- Port information for Content Runtime virtual machine
Hardware requirements
You must meet the following hardware minimum requirements:
- 4 CPU cores
- 8 GB memory
- 20 GB disk for Operating System
- 100 GB disk for Software Repository
- 40 GB disk for Docker production configuration (optional). For more information, see Production Docker.
- Content Runtime supports only x86 architecture.
Supported operating systems and platforms
The following operating systems and platforms are supported.
- Ubuntu 18.04 LTS
- VMware Tools must be enabled in the image for VMWare template.
- Ubuntu Repos with correct configuration must be enabled in the images.
- Sudo User and password must exist and be allowed for use.
- Firewall (through iptables) must be disabled.
- SELinux must be disabled.
- The system umask value must be set to 0022.
- Red Hat Enterprise Linux (RHEL) 7 (requires Docker-EE
)
- Needs RHEL 7.x image to be created, at least.
- VMware Tools must be enabled in the image.
- RHEL Satellite Repos with correct configuration must be enabled in the images.
- Red Hat Enterprise Linux 7 Server (RPMs)
- Red Hat Enterprise Linux 7 Server - RH Common (RPMs)
- Red Hat Enterprise Linux 7 Server - Optional (RPMs)
- Red Hat Enterprise Linux 7 Server - Supplementary (RPMs)
- Red Hat Enterprise Linux 7 Server - Extras (RPMs)
- Sudo user and password must exist and be allowed for use.
- Firewall (through iptables/firewalld) is disabled.
- SELinux must be disabled.
- The system umask value must be set to 0022.
- CentOS 7
- VMware Tools must be enabled in the image.
- Sudo user and password must exist and be allowed for use.
- Firewall (through iptables/firewalld) is disabled.
- SELinux must be disabled.
- The system umask value must be set to 0022.
Network requirements
- Static IPv4 address is assigned to each VM. No DHCP is used.
- A static IPv4 address is allocated and reserved prior to its usage.
- The IPv4 address is an IP in a private network that has egress-only access to Internet.
- In addition to IPv4 address, the Gateway, Prefix Length, DNS Suffixes, and DNS Servers need to be obtained prior to the deployment.
- Managed services instance is deployed in the same private network, so deploying from Managed services Instance to VMware environment is truly through private networking.
- The virtual machine must have a connection to the internet for the duration of the configuration process.
Port information for Content Runtime virtual machine
The following table lists the suggested settings for network and firewall:
Network Environment | Private IP Only | Port Details |
---|---|---|
Private | Yes | Allow the following access for all sources on private interface: - SSH - ICMP - HTTP - HTTPS - TCP 8888 (non-secure software repository) - TCP 9999 (secure software repository) - TCP 5443 (pattern manager port) |
Chef Versions
The following Chef Server and Client versions have been validated to be used for IBM provided cookbooks within CAM.
- Chef Server : 12.18.14
- Chef Client : 14.1.1
Docker and Docker Compose Versions
- Docker latest version, at the time of this document is : 20.10
- Docker Compose version, 1.11.2
VMWare ESXi Configuration
On an ESX/ESXi host, enable Network Time Protocol (NTP) Client, configure NTP Server, and ensure that the NTP Service is running.