Well, we take a somewhat different approach. We sync directly from RedHat and hence (re)naming those repos in Satellite isn't really an option. We base our setup on 'products' and 'os' a 'product' being really an 'os' and other things (applications, db etc). But a 'product' can also be part of our core operating system. We do this to play better with the RBAC model.
So we will have P_<product> R_<product>_Yum R_<product>_Puppet The RBAC model only allows you to permission at the product level so we can hand that of to that team. We construct our OS as a content view: CV_<os> RHEL 6Server P_<product1> # Ok, in reality you add the repository but this is for representation, this is owned by <product1> P_<product2> # Owner is <product2> But also: CV_<product> P_<product> We will also allow the following CCV_<os>_<product> # This can be permissioned to <product> team to manage CV_<os> # But they can't modify <os> CV_<product> # But they can modify <product> This is so that (for instance) we can control what goes into the OS and use the RBAC controls to prevent the owner of <product> from being able to modify that but allow them to control their own content views and publish / promote as they see fit. The we tie these to hostgroups structured: HG_<os>/<region>/<lifecycle> # Assign CV_<os> here or HG_<os>/<region>/<lifecycle>/<product> # Assign CCV_<os>_<product> here We then use the same methodology for activation keys etc. So an activation key is: AK_<os>_<lifecycle> # Assigns all the products / os which is in content view CV_<os> and is assigned to HG_<os>/<region>/<lifecycle> AK_<os>_<product>_<lifecycle> We build these programmatically. On Wednesday, November 9, 2016 at 6:21:12 PM UTC-5, Alan Evans wrote: > > Is there any guide or are there any recommendations for naming/labeling > products and repos? > > Is CentOS, CentOS 6, CentOS 6 x86_64 a product? > What are people doing for CentOS/EPEL? > > If left to it's own devices katello just replaces spaces with underscores > for product/repo labels. > > What about other "products?" > Is Katello a product? Katello 3.2? > Puppet? Puppet PC1? > Puppet Enterprise? Puppet Enterprise 2016.4? or is the product "Puppet" > with repos for the versions? > > I am leaning toward: > > Product: CentOS 6 (centos-6) > Repo: CentOS 6 x86_64 OS - centos-6-x86_64-os = > http://mirror.centos.org/centos/6/os/x86_64/ > Repo: CentOS 6 x86_64 Updates - centos-6-x86_64-updates = > http://mirror.centos.org/centos/6/updates/x86_64/ > - or more generally - > Repo: CentOS $major $arch $repo - lower(centos-$major-$arch-$repo) = > lower(http://mirror.centos.org/centos/$major/$repo/$arch/) > > Product CentOS 7 (centos-7) > Repo: CentOS $major $arch $repo - lower(centos-$major-$arch-$repo) = > lower(http://mirror.centos.org/centos/$major/$repo/$arch/) > > Product EPEL 6 (epel-6) > Repo: EPEL $major $arch - lower(epel-$major-$arch) = > http://dl.fedoraproject.org/pub/epel/$major/$arch/ > > Puppet Enterprise (puppet-enterprise) > Repo: Puppet Enterprise 3.7.2 EL7 x86_64 - > puppet-enterprise-3.7.2-el-7-x86_64 = > https://puppet-master:8140/packages/3.7.2/el-7-x86_64 > Repo: Puppet Enterprise 2016.4 EL7 x86_64 - > puppet-enterprise-2016.4-el-7-x86_64 = > https://puppet-master:8140/packages/2016.4/el-7-x86_64 > > Thoughts? > -Alan > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
