Greg, Thank you for your thoughts. This is the kind of discussion I was hoping for.
I considered using (and may still) a single "CentOS" repo and use activation keys to get boxes assigned to the right repos. As I mentioned to Jason I am still not clear on content-views but that is another topic. On Wednesday, November 9, 2016 at 9:50:42 PM UTC-7, Greg Swift wrote: > > Here's a run down of how i've tried approaching this, then I'll explain > why i've heard complaints from some users > > > Product: CentOS > Repos: > - el6-64-os > - el6-64-updates > - el6-64-extras > - el7-64-os > - el7-64-updates > - el7-64-extras > Seeing it actually done this way I am liking it a lot better. > Product: EPEL > Repos: > - el6-64 > - el7-64 > > Product: Internal > Repos: > - el6-noarch-product1 > - el6-noarch-product2 > - el7-noarch-product1 > - el7-noarch-product2 > > So on a rhel 6 box via yum the repos end up being named like this: > > ORG-CentOS-el6-64-os > ORG-CentOS-el6-64-updates > ORG-EPEL-el6-64 > ORG-Internal-el6-noarch-product1 > > What ends up being the problem is the katello UI. In several places you > are only given a list of repositories to select from, so based on the above > you get a list like this: > > Repos: > - el6-64-os > - el6-64-updates > - el6-64-extras > - el7-64-os > - el7-64-updates > - el7-64-extras > - el6-64 > - el7-64 > - el6-noarch-product1 > - el6-noarch-product2 > - el7-noarch-product1 > - el7-noarch-product2 > > So I have users that want to try different routes but that means some > interesting results, like these names in yum: > > ORG-CentOS-centos-6-64-os > ORG-CentOS-centos-6-64-updates > ORG-EPEL-epel-6-64 > ORG-Internal-el6-noarch-product1 > > which is just duplication. Or > Yeah I am not happy with having duplication all over like this either. The OCD part of me ticks when I do it or think of doing it. But yeah you are right, if you have only the repo name to look at you are missing some context. > > ORG-Linux-centos-6-64-os > ORG-Linux-centos-6-64-updates > ORG-Linux-epel-6-64 > ORG-Internal-el6-noarch-product1 > > Which loads even more things into a single product, which i'm not a fan of > but maybe it doesn't matter. > Yeah I would agree here. This would be overloading the "Linux" product and I think make things more confusing and complicated in the long run. > > Another concern that was raised was managing the repo selection in > activation keys. By grouping EL6&7 in the same Product and relying on > enabling/disabling in the activation keys it can be slightly annoying > managing a bunch of keys. Where as if we move to a Product like CentOS6, > then there is no enabling/disabling of repos to deal with. but we wrote a > simple bas function around that... but its definitely not ideal. > > So Far i'm leaning towards not changing from the first schema I mentioned, > but the UI is definitely annoying with it. > > You could file a feature request to include the product name or label when displaying repos. Maybe: "$repo_name ($product_name)" or "$product_name - $repo_name", the second of which has the interesting side effect of grouping things by product if sorted by name. And where labels are concerned display them like they are used in pulp. Pulp doesn't even have a conept of product, it just manages repos so pulp repo names just become "$product_label" + "_" + "$repo_label". > -greg > > On Wed, Nov 9, 2016 at 7:45 PM 'Jason B. Nance' via Foreman users < > [email protected] <javascript:>> wrote: > >> HI Alan, >> >> Regarding products, I organize by the upstream/vendor not by versions. >> For example, I have CentOS, OEL, and EPEL products. My content views are >> where I split up stuff into versions and such. >> >> Your examples look good to me. >> >> j >> >> >> ------------------------------ >> *From: *"Alan Evans" <[email protected] <javascript:>> >> *To: *"Foreman users" <[email protected] <javascript:>> >> *Sent: *Wednesday, November 9, 2016 5:19:54 PM >> *Subject: *[foreman-users] Naming products and repos? >> >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> >> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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.
