Bug 1889005

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.7/html-single/installing_satellite_server_from_a_connected_network/index#satellite-storage-requirements_satellite

Section Number and Name: 
1.2. Storage Requirements


Describe the issue: 
The session suggests a maximum size of 20 GB for the /var/cache/pulp filesystem. We have increasing numbers of support cases where customers fill up /var/cache/pulp with either yum repo metadata (the "*-other.xml.gz" metadata file for rhel-7-server-rpms is now 3.7+ GB in size) or, significantly worse, with container image blobs. One case in particular with a customer making heavy use of Satellite for docker contents, has /var/cache/pulp use upwards of 90 GB during syncs.

The documentation suggests /var/cache/pulp lives in the same filesystem as /var/lib/pulp so moving files is just a quick inode operation. Maybe this needs to be a requirement going forward?

Otherwise, we need to make it very clear that /var/cache/pulp size needs to increase according to docker repo usage.

At the very least, thinking of an 8-worker pulp generating the "other.xml.gz" metadata for rhel-7-server-rpms at the same time, the current space used for /var/cache/pulp needs to be 8 x 4 GB = 32 GB.

Suggestions for improvement: 
It really depends on the approach. Turning to mandatory /var/cache/pulp residing with /var/lib/pulp would be one thing, whereas increasing the minimum size to 32 GB would be very different and less of a change.