Content views and filters in Satellite 6: part 3, content views and composite content views

This episode is about content views and composite content views, as I get lots of questions about how and when to use CCVs. I hope this helps.
Please leave any comments below, please subscribe and checkout the blog post for this video at100things.wzzrd.com/2017/02/15...

[@gregm4501]

These are the most helpful videos on Satellite 6. Once again thanks!!

[@100thingstodowithredhatpro8]

Greg M Thanks! That's a great motivation to create more!

[@krishkarki9795]

Thanks for putting effort on this topic, i am learning a lot from you. I am expecting some more topics on Linux in coming future. Keep up the good work !

[@kevinheron836]

I really like what I am hearing with Satellite 6. I was looking to deploy satellite just for the most basic package management capabilities as I did not have any knowledge of the idea behind a content view and how they could be leveraged.Question for you - if I want to move away from RHEL 5.9 or 5.11 and onto RHEL 6.8 or even 7.2, could I use content views to essentially lay the applications currently running on the 5.9 or 5.11 systems and include RHEL 6.8 or 7.2 libraries to the new system and run it through the SDLC (Stage-Dev-Prod)? Have you seen a use case such as that?

[@100thingstodowithredhatpro8]

Hi Kevin,
Thanks for the question!
If I understand you correctly, you want to add RHEL6 RPMs to a RHEL5 content view in order to update from RHEL5 to RHEL6? If that's the case, the answer is 'no'. In place upgrades from one major RHEL version to another is not supported, except in some cases from RHEL6 to RHEL7.
If you instead mean to create a content view for your application, add the application RPMs to it, and then re-use that application content view in a CCV with a RHEL5 content view, and in another CCV with a RHEL6 or RHEL7 content view, that should work and is actually a really good use case for CCVs.

[@felipepereira1747]

Hello and thanks for these excelent videos! I could not read the KCS you mentioned in the end access.redhat.com/articles/1585273 (logged in). I'd like to hear a practical advice about what to do with EPEL, monitoring, backup -- all basic/common repos. Following your suggestion to keep things simple, I think they should be included in a plain generic cv for rhelX (X being 7,8...), but I see in the video that you have a different cv for EPEL (and probably you group OS+EPEL in the CCVs above). I'm also having some trouble with filters and EPEL. First, EPEL does not keep history (obsoleted packages are deleted from the repo). So it can't be downloaded on-demand, and it should be set to immediate; or maybe I should disable "mirror on sync". And last, filters don't seem to behave so well with EPEL -- looks like there is the "newpackage" type of packages, besides enhancement, important and security -- see access.redhat.com/solutions/1451913 , from 2018, I don't know if Red Hat fixed this, at least not in the 6.7.1 UI.

[@100thingstodowithredhatpro8]

Sorry for the late reply: I didn't get notifications of these up until now :/
Gosh. I didn't know EPEL removed old releases of packages after they're superseded. Wow. That's really good to know!
Indeed, in that case you want to make it "immediate" and probably sync regularly indeed!
If you're still reading this, I'm not sure what exactly goes wrong with your filters for EPEL. Can you ellaborate?