Requirements
The following tables specify the minimum server and proxy requirements.
1. Server Requirements
Software and Hardware | Details | Recommendation |
---|---|---|
openSUSE Leap 15.5 |
Clean installation, up-to-date |
openSUSE Leap 15.5 |
CPU |
- |
Minimum 4 dedicated 64-bit CPU cores (x86-64) |
RAM |
Test or Base Installation |
Minimum 16 GB |
Production Server |
Minimum 32 GB |
|
Disk Space |
|
Minimum 40 GB |
|
Minimum 50 GB |
|
|
Minimum storage required: 100 GB (this will be verified by the implemented check) * 50 GB for each SUSE product and Package Hub * 360 GB for each Red Hat product |
|
|
Minimum 10 GB. Add 100 MB per SUSE product, 1 GB per Red Hat or other product. Double the space if the server is an ISS Master. |
|
Swap space |
3 GB |
2. Proxy Requirements
Software and Hardware | Details | Recommendation |
---|---|---|
openSUSE Leap 15.5 |
Clean installation, up-to-date |
openSUSE Leap 15.5 |
CPU |
Minimum 2 dedicated 64-bit CPU cores |
|
RAM |
Test Server |
Minimum 2 GB |
Production Server |
Minimum 8 GB |
|
Disk Space |
|
Minimum 40 GB |
|
Minimum 100 GB |
|
|
Minimum 100 GB |
SUSE Manager Proxy caches packages in the /var/cache/
directory.
If there is not enough space available in /var/cache/
, the proxy will remove old, unused packages and replace them with newer packages.
As a result of this behavior:
-
The larger
/var/cache/
directory is on the proxy, the less traffic there will be between it and the SUSE Manager Server. -
By making the
/var/cache/
directory on the proxy the same size as/var/spacewalk/
on the SUSE Manager Server, you avoid a large amount of traffic after the first synchronization. -
The
/var/cache/
directory can be small on the SUSE Manager Server compared to the proxy. For a guide to size estimation, see the [server-hardware-requirements] section.