Since the OCP service incurs significant computational and storage overhead during operation, resource planning is required based on the scale of the objects to be managed. Note that in a multi-node OCP deployment, you must add multiple servers during the Add Server step, and the configuration of each server node must meet the following requirements.
CPU and memory
The CPU and memory resources required by the OCP-Server service are shown in the following table. The data below is calculated based on the standard of 10 tenants per managed cluster. Please select appropriate CPU and memory according to your actual situation.
Number of managed hosts |
CPU (Cores) |
Memory (GiB) |
|---|---|---|
| ≤ 10 | 2 | 4 |
| ≤ 50 | 4 | 8 |
| ≤ 200 | 8 | 16 |
| ≤ 500 | 12 | 24 |
| ≤ 1000 | 16 | 32 |
Note
Disk capacity
OCP-Server writes files to disk during operation, which consumes disk space. We recommend reserving at least 100 GiB of disk space for OCP-Server to prevent functionality from being affected due to a full disk.
The disk usage of OCP-Server during operation is shown in the following table.
Category |
Storage Path |
Capacity requirements |
|---|---|---|
| OCP Program | /home/admin/ocp-server/ |
OCP main process files, etc., occupying approximately 800 MiB of space. |
| OCP Files | /home/admin/data/files/ |
OCP's bundled ocp-agent RPM package, etc., occupying approximately 150 MiB of space. |
| OCP Logs | /home/admin/ocp-server/log |
The OCP system parameters define the log file size and the number of files to retain. By default, a single file is 100 MiB, at least 5–10 files are generated per day, and each file is retained for up to 100 days. It is recommended to reserve 100 GiB of space. |
Note
The log retention size for OCP-Server can be configured via OCP system parameters. For details, see Modify system parameters.