Description of problem:

Currently Satellite6 synchronize entire container image repositories and use copies for each content view and lifecycle environment combination:

[root@inf60 ~]# du -sh /var/lib/pulp/nodes/published/https/repos/*rhel-base
589M	/var/lib/pulp/nodes/published/https/repos/acme-container_images-rhel-base
468M	/var/lib/pulp/nodes/published/https/repos/acme-library-ccv-infra-openshift3-container_images-rhel-base
468M	/var/lib/pulp/nodes/published/https/repos/acme-library-cv-app-ose3-container_images-rhel-base
468M	/var/lib/pulp/nodes/published/https/repos/acme-library-cv-con-webshop-container_images-rhel-base
468M	/var/lib/pulp/nodes/published/https/repos/acme-web-dev-cv-app-ose3-container_images-rhel-base
468M	/var/lib/pulp/nodes/published/https/repos/acme-web-dev-cv-con-webshop-container_images-rhel-base
468M	/var/lib/pulp/nodes/published/https/repos/acme-web-qa-cv-app-ose3-container_images-rhel-base

Since container image repositories are quite big from a storage consumption perspective this leads to an unnecessary huge storage consumption if many container image repos and content views are used.

Version-Release number of selected component (if applicable):

6.1

How reproducible:

Sync a container image repository. Add it to one or more content views and promote them. Verify disk usage inside pulp.

Steps to Reproduce:
1.
2.
3.

Actual results:

Repositories are copied.

Expected results:

Repositories are linked only.

Additional info: