Hi there,
I have a question about how Pulp content looks when the same content-view is promoted to multiple lifecycle environments.
I have the following LEs: Eng>RC>UAT>Dev>Test>PAT>Prod (quite a few)
I create a new version of my cv-core, publish it and promote it into each of those LEs.
The content is unchanged in each promotion, but it looks to me that Pulp is generating a new copy of cv-core in each LE.
First up, am I right about this? It certainly look that way from the server workload when I compare promotions into just Eng versus promotions into all LEs.
Secondly (depending on the answer to Q1), is it not possible to link the version of cv-core in say UAT back to the initial version promoted to Eng? Copy on Write type of thing? Saving having to create an entire new copy of a cv which is identical.
I’m asking because my content is synched out from a central Pulp in Katello out to 26 global smart-proxies and the 7 LEs mentioned above. The workload on each of the smart-proxies is massive during each release cycle. We wondered if there is anything we can do to tune this to help the smart-proxies out.
Thanks
Duncan