Hardware

You can find information about the hardware requirements for different operating systems that support IBM DevOps Deploy (Deploy).

Contents

AIX

The hardware requirements to run the Deploy components on the AIX operating systems are as follows:

Hardware Components Requirement
Disk space
  • Agent
  • Command-line client
  • Relay
  • Server
Minimum of 2 GB.
Memory Agent Minimum of 2 GB.
  • Relay
  • Server
Java Heap requirements:

A minimum of 2 GB is required for evaluation purposes, such as a proof of concept (POC) instance or a small demo environment.

The Xmx setting must be increased for production purposes as follows:
  • <500 agents: ~4 GB
  • 500-5000 agents: ~13 GB
  • 5000-15000 agents: ~24 GB

Native memory:

The minimum required memory is 4 GB for POC, 8 GB for production, for the additional memory required beyond the Java Heap.

Network: adapters, drivers, protocols
  • Agent
  • Command-line client
  • Relay
  • Server
Gigabit (1000) Ethernet with low-latency to the database.
Processor
  • Relay
  • Server
The server requires approximately double the CPU capacity of a relay. So, given the number of agents (800) and 2 cores per 500 agents on the relay, use an 8-core machine available for the server.
Agent 2-Core processor

For z/OS: The Deploy agent for z/OS runs on IBM System zEnterprise EC12 or zEnterprise BC12 machines and later versions that support the required z/OS operating system

Product specific
  • Command-line client
  • Relay
  • Server
Agent Relay minimum system requirements.
Without artifact caching:
  • HDD - 2 GB
  • CPU - 2
  • RAM - 2 GB

With artifact caching, use the formula:

HDD - 2GB + the cache size *2

Storage hardware
  • Command-line client
  • Relay
  • Server
Individual requirements depend on usage, retention policies, and application types. In general, the larger the number of artifacts kept in IBM Deploy's artifact repository (CodeStation), the more storage is required.
Note: CodeStation is installed when the Deploy server is installed.
Follow these guidelines to determine storage requirements for production environments:
  • 200-400 GB of database storage is typically sufficient for most environments.
  • To calculate CodeStation storage requirements, use the following formula:
    average artifact size * number of versions imported per day * average number of days before cleanup
  • Approximately 1 MB per deployment of database storage; varies based on local requirements.
Note: The AIX hardware requirement applies to all supported AIX operating systems.

Linux

The hardware requirements to run the Deploy components on the Linux operating systems are as follows:
Hardware Components Requirement
Disk space
  • Agent
  • Command-line client
  • Relay
  • Server
Minimum of 2 GB.
Memory Agent Minimum of 2 GB.
  • Command-line client
  • Relay
  • Server

Java Heap requirements:

A minimum of 2 GB is required for evaluation purposes, such as a proof of concept (POC) instance or a small demo environment.

Xmx setting must be increased for production purposes as follows:
  • <500 agents: ~4 GB
  • 500-5000 agents: ~13 GB
  • 5000-15000 agents: ~24 GB

Native memory:

The minimum required memory is 4 GB for POC, 8 GB for production, for the additional memory required beyond the Java Heap.

Network: adapters, drivers, protocols
  • Agent
  • Command-line client
  • Relay
  • Server
Gigabit (1000) Ethernet with low-latency to the database.
Processor Agent A 2-core processor.

For z/OS: Deploy agent for z/OS runs on IBM System zEnterprise EC12 or zEnterprise BC12 server platforms and later versions that support the required z/OS operating system.

  • Command-line client
  • Relay
  • Server
The server requires approximately double the CPU capacity of a relay, so, given the number of agents (800) and 2 cores per 500 agents on the relay, use an 8-core machine available for the server.
Product specific
  • Command-line client
  • Relay
  • Server
Agent Relay minimum system requirements.
Without artifact caching:
  • HDD - 2 GB
  • CPU - 2
  • RAM - 2 GB

With artifact caching, use the formula:

HDD - 2 GB + the cache size *2

Storage Hardware
  • Command-line client
  • Relay
  • Server
Individual requirements depend on usage, retention policies, and application types. In general, the larger the number of artifacts kept in IBM Deploy's artifact repository (CodeStation), the more storage is required.
Note: CodeStation is installed when the Deploy server is installed.
Follow these guidelines to determine storage requirements for production environments:
  • 200-400 GB of database storage is typically sufficient for most environments.

  • To calculate CodeStation storage requirements, use the following formula:
    average artifact size * number of versions imported per day * average number of days before cleanup
  • Approximately 1 MB per deployment of database storage; varies based on local requirements.

Note: The Linux hardware requirement applies to all supported Linux operating systems.

Solaris

The hardware requirements to run the Deploy agent on the Solaris operating systems are as follows:

Hardware Requirement
Disk space Minimum of 2 GB.
Memory Minimum of 2 GB.
Network: adapters, drivers, protocols Gigabit (1000) Ethernet with low-latency to the database.
Processor A 2-core processor.
Note: The Solaris hardware requirement applies to all supported Solaris operating systems.

Windows

The hardware requirements to run the Deploy components on the Windows operating system are as follows:
Hardware Components Requirement
Disk space
  • Agent
  • Command-line client
  • Relay
  • Server
Minimum of 2 GB.
Memory Deploy agent Minimum of 2 GB.
  • Command-line client
  • Relay
  • Server
Java Heap requirements:

A minimum of 2 GB is required for evaluation purposes, such as a proof of concept (POC) instance or a small demo environment.

The Xmx setting must be increased for production purposes as follows:
  • <500 agents: ~4 GB
  • 500-5000 agents: ~13 GB
  • 5000-15000 agents: ~24 GB

Native memory:

The minimum required memory is 4 GB for POC, 4 GB for production, for the additional memory required beyond the Java Heap.

Network: adapters, drivers, protocols
  • Agent
  • Command-line client
  • Relay
  • Server
Gigabit (1000) Ethernet with low-latency to the database.
Processor Agent A 2-core processor.
  • Command-line client
  • Relay
  • Server
The server requires approximately double the CPU capacity of a relay. So, given the number of agents (800) and a 2-cores per 500 agents on the relay, use an 8-core machine available for the server.
Product specific
  • Agent
  • Command-line client
  • Relay
  • Server
Agent relay minimum system requirements
Without artifact caching:
  • HDD - 2 GB
  • CPU - 2
  • RAM - 2 GB

With artifact caching, use the formula:

HDD - 2 GB + the cache size *2

Storage hardware
  • Command-line client
  • Relay
  • Server
Individual requirements depend on usage, retention policies, and application types. In general, the larger the number of artifacts kept in IBM Deploy's artifact repository (CodeStation), the more storage is required.
Note: CodeStation is installed when the Deploy server is installed.
Follow these guidelines to determine storage requirements for production environments:
  • 200-400 GB of database storage is typically sufficient for most environments.
  • To calculate CodeStation storage requirements, use the following formula:
    average artifact size * number of versions imported per day * average number of days before cleanup
  • Approximately 1 MB per deployment of database storage, which varies based on local requirements.
Note: The Windows hardware requirement applies to all supported Windows operating systems.

z/OS

The hardware requirements to run Deploy agents on the z/OS operating system are as follows:
Hardware Requirement
Disk space Minimum of 2 GB.
Memory Minimum of 2 GB.
Network: adapters, drivers, protocols Gigabit (1000) ethernet with low-latency to the database.
Processor A 2-core processor.

For z/OS: Deploy agent for z/OS runs on IBM System zEnterprise EC12 or zEnterprise BC12 server platforms and later versions that support the required z/OS operating system.

Note: The z/OS hardware requirements apply to all supported z/OS operating systems.

For more details on system requirements, see Software product compatibility report.

Integrated system

The hardware requirements to run the Deploy command-line client components on an integrated system are as follows:
Hardware Requirement
Disk space Minimum of 2 GB.
Memory Java Heap requirements:

A minimum of 2 GB is required for evaluation purposes, such as a proof of concept (POC) instance or a small demo environment.

The Xmx setting must be increased for production purposes as follows:
  • <500 agents: ~4 GB
  • 500-5000 agents: ~13 GB
  • 5000-15000 agents: ~24 GB

Native memory:

The minimum required memory is 4 GB for POC, 4 GB for production, for the additional memory required beyond the Java Heap.

Network: adapters, drivers, protocols Gigabit (1000) Ethernet with low-latency to the database.
Processor The server requires approximately double the CPU capacity of a relay. So, given the number of agents (800) and a 2-cores per 500 agents on the relay, use an 8-core machine available for the server.
Product specific Agent relay minimum system requirements
Without artifact caching:
  • HDD - 2 GB
  • CPU - 2
  • RAM - 2 GB

With artifact caching, use the formula:

HDD - 2 GB + the cache size *2

Storage hardware Individual requirements depend on usage, retention policies, and application types. In general, the larger the number of artifacts kept in IBM Deploy's artifact repository (CodeStation), the more storage is required.
Note: CodeStation is installed when the Deploy server is installed.
Follow these guidelines to determine storage requirements for production environments:
  • 200-400 GB of database storage is typically sufficient for most environments.
  • To calculate CodeStation storage requirements, use the following formula:
    average artifact size * number of versions imported per day * average number of days before cleanup
  • Approximately 1 MB per deployment of database storage, which varies based on local requirements.