*** This bug has been marked as a duplicate of bug 1203267 ***

Hi Sean,
This is not the same at all... nothing to see !

Here, we don't want to have several CCVs on a host, this is the opposite, we want an special CCV which offers a lot of possibilities of contents for the special case (like applications servers).
We apply a strict policy security and we try to give a frame to our users and guide them to the better choice.
We limited the offer in term of rpms and rpm to help them to give a max of Red Hat support. We want to limit all the repositories without entreprise support. 
For such repositories we limited until the rpms, but we are limited by the system,we touch the limit.

Explainations : 

remember these principes :
1- We use CVs inside a CCV.
2 - A CV contains generally one repo.
3 - We have differents CVs on the same repo but with differents filters.
4 - We have a system to avoid to reduce numbers of keys and CCVs.

For instance : 
We need some package in EPEL, but EPEL not supported, so we gives only 2 rpms -> a CV with repo EPEL + filter A
but some teams need 4 others rpm in EPEL and we want another EPEL but with only this rpms -> a CV wut repo EPEL + Filter B

We have to give these specials CV in a special CCV which allow to activate special depo in case of needs.
Today, when we do that, the repo has the same name, but we have several case managed by each different CV but one CCV is applied to the hosts. 
The reposet comes with the less by the key of register and the people activate in case of needs on the host (manually or by a manager of configuration like puppet/ansible etc).


Today you can have filter but when we have the repo in several CV and applied in a CCV (composite Content View), this is a limit because the name of the repository stay the same, but we could have several CV+filter on the same repo, today, in the CCV, that gives an agregation, this is not good for us, we want what we want only not an agregation because the name of repo is the same.
We don't want a agregation of filter, but the repo filtered as we want like in the CV (repo + filter) even if there is several configuration CV

note : Sorry for my english

Regards
Aymeric Marchal