Satellite 6 SOE / Recommended Practices / Products / EPEL

Hi,

I've come across a couple of different guides for Satellite 6 best practices:

https://access.redhat.com/articles/1169613
Red Hat Satellite 6: Core Standard Operating Environments (SOE) Recommended Practices

https://access.redhat.com/articles/1585273
10 Steps to Build an SOE: How Red Hat Satellite 6 Supports Setting up a Standard Operating Environment

Firstly, are there any changes in 6.1 which would alter any of the best practice recommendations above?

The recommendations around products is: "create as few Products as possible", "The minimum required number of Products is determined by the GPG key" and "we recommend that you bundle all Products and variants of each software within one Product as long as they use the same GPG key".

I know that EPEL is out of the scope of Red Hat support. However, this question could apply to other products that users have.

EPEL ships with different GPG keys for each RHEL release. So, for something like this, should I create 1 "EPEL" product and add each repo to this, or should I create 3 EPEL products, each with their own key? When creating a product, I'm asked to provide a GPG key. As this will vary between releases, I'm thinking I would need 3 different products.

Finally, is anyone using EPEL in practice? I've sync'd EPEL 5, EPEL 6 and EPEL 7 but I'm seeing odd behaviour with the errata. I have a RHEL7 client subscribed to Satellite, but it seems to think that some EPEL5 errata are applicable to it:

Eg:

FEDORA-EPEL-2015-5677
chrony-1.31.1-1.el5 security update

Yet my client has the RHEL 7 chrony package installed, so I don't see why it's relevant.

[root@rhel7 ~]# rpm -qa | grep chro
chrony-1.29.1-1.el7.x86_64

This is probably something I can't raise under a support case, so is putting EPEL under Satellite a good idea?

Richard.