Appendix B. Storing content on an NFS share
When local disk space on your Satellite Server is insufficient for content storage, you can mount an NFS share at /var/lib/pulp to store synchronized content remotely.
Use high-bandwidth, low-latency storage for the /var/lib/pulp file system. Red Hat Satellite has many I/O-intensive operations. Therefore, high-latency, low-bandwidth storage might have issues with performance degradation.
Procedure
-
Create the NFS share. This example uses a share at
nfs.example.com:/Satellite/pulp. Ensure this share provides the appropriate permissions to Satellite Server and itsapacheuser. Stop Satellite services on your Satellite Server:
# satellite-maintain service stopInstall the
nfs-utilspackage on your Satellite Server:# satellite-maintain packages install nfs-utilsCopy the existing contents of
/var/lib/pulpto the NFS share.Mount the NFS share at a temporary location:
# mkdir /mnt/temp # mount -o rw nfs.example.com:/Satellite/pulp /mnt/tempCopy the existing contents of
/var/lib/pulpto the temporary location:# cp -r /var/lib/pulp/* /mnt/temp/.-
Set the permissions for all files on the share to use the
pulpuser. Unmount the temporary storage location:
# umount /mnt/temp
Remove the existing contents of
/var/lib/pulp:# rm -rf /var/lib/pulp/*Edit the
/etc/fstabfile and add the following line:nfs.example.com:/Satellite/pulp /var/lib/pulp nfs rw,hard,intr,context="system_u:object_r:pulpcore_var_lib_t:s0"This makes the mount persistent across system reboots. Ensure to include the SELinux context.
Enable the mount:
# mount -aVerify the NFS share provides the content:
Confirm the NFS share mounts to
/var/lib/pulp:# df Filesystem 1K-blocks Used Available Use% Mounted on ... nfs.example.com:/Satellite/pulp 309506048 58632800 235128224 20% /var/lib/pulp ...Confirm the content exists at the mount on
/var/lib/pulp:# ls /var/lib/pulp
Start Satellite services on your Satellite Server:
# satellite-maintain service start
Verification
- Run content synchronization to ensure the NFS share works as expected. For more information, see Section 4.2, “Synchronizing repositories ad hoc”.