Is it possible to make a composite content view with RHEL 6, RHEL 7 and Custom local RPMs content views?

Latest response

I am trying to find a simple solution for this situation. I have few rhel 6 and 7 machines where I deploy new custom local RPMs every morning. Now, can I have just one composite component view which will have both rhel 6,7 and custom content view so that those test machines will have all all three content views. And I guess I can manually disable the repos I do not want on the test machines for desired outcome?

Responses

Hello, why not have two CCVs, one for RHEL6 and one for RHEL7 and both can include you custom CV.

Stephen, That's exactly what I did. I created two ccvs, i.e, ccv_custom6_test & ccv_custom7_test. Also, do you know if publishing and promoting those content views automatically updates content views under those composite views or do I have to "content-view update" the component ids in order to publish the new version of ccv? Thanks in advance.

It is definitely possible but generally not recommended. A Content View is effectively 'a group of repositories on the same lifecycle'. RHEL6 & RHEL7 aren't on the same lifecycle, so it doesn't make sense to put them in the same CV/CCV.

Additionally, the more repositories in a content view, the longer it takes to publish, so there is some value is keeping them separate.

Composite Content Views are also point in time snapshots, so if you change the underlying content view, you still need to republish the composites.

Rich, So, do I need to update component IDs of underlying content views of a composite view in order to publish and promote it? Or when I publish and promote content views, it automatically updates the underlying content views of a composite view?

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.