Description of problem:

Adding as a tracker, this will undoubtebly impact several components. Additional use cases should be identified to help determine the scope of this feature. The initial interest in this request is driven by sharing content with multiple proxies:

It is required to kicking off a sync process to get repo data from katello to the proxies. This is useful in many scenarios, but if the user is using the proxies for horizontal scaling in the same datacenter, the additional sync processes can cause both unnecessary overhead, and create different repo metadata between capsules. If a client expects to bounce around between capsules that are behind a VIP, this can cause 404s.

One solution to this problem is to mount the server's /var/lib/pulp/published and /var/lib/pulp/content read-only on the proxies. This lets the proxy serve exactly what katello has, without having to kick off a sync process. Additionally, it makes the content the same across proxies. This makes it easier to use a VIP in front of them.