Chapter 8 - Enterprise Repository Management with Pulp

1. Pulp repositories can be version controlled (through snapshots taken in time). They are also disk space-efficient and do not duplicate packages across mirrors.
2. Linux repositories change on a very regular basis, and a machine patched on Monday may not look like a machine patched on Tuesday. This can, in worst-case scenarios, impact testing results.
3. Pulp 2.x requires a message broker and a MongoDB database to run.
4. /var/lib/mongodb should be 10 GB or more in size. /var/lib/pulp should be sized according to the repositories you want to mirror. They should be created on the XFS filesystem.
5. At the simplest possible level, you could create a repository file in /etc/yum.repos.d and point it at the appropriate path on the Pulp server (as documented in Chapter 8, Enterprise Repository Management with Pulp). It is also possible to configure...