Containers
You can find information about hardware and embedded software requirements for containers to run the HCL DevOps Deploy (Deploy).
The hardware requirements for the containers to run the Deploy server are
as follows:
| Hardware | Containers | Requirement |
|---|---|---|
| Disk space |
|
Minimum of 2 GB. |
| Memory |
|
Java Heap requirements: A minimum of 2 GB is required for evaluation purposes, such as proof of concept (POC) instance or a small demo environment. Increase the Xmx
setting for production purposes as follows:
Native memory: 4 GB for POC, 8 GB for production, for 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-core processor per 500 agents on the relay, use an 8-core server for the best performance. |
| Product specific |
|
Agent Relay minimum system requirements. Without artifact
caching:
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 number of artifacts kept
in HCL
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:
|
The embedded software requirements for containers to run the HCL
Deploy components
are as follows:
| Embedded software | Containers | Deploy components | Runtime provider | |
|---|---|---|---|---|
| Red Hat Universal Minimal Base image (UBI)10 |
|
|
|
|