<div dir="ltr">Thank you all for your answers, that makes sense.<div><br></div><div>I guess what I failed to ask was about repository naming schemes and repository discovery, so my example wasn't the best.</div><div><br></div><div>Say I am shipping version 2.0 (of some imaginary software) to our customers. Bug fixes will continue to be pushed to the 2.0 repository.</div><div><br></div><div>Later, I am shipping version 2.1, 2.2 etc. Presumably these go into their own repo.</div><div><br></div><div>I would like to have a programmatic way of comparing repositories, so that I can write a wrapper around yum that notices the presence of a "new" repository and offers the possibility of an upgrade to the user of said wrapper. In other words, I don't want to automatically update my customers to 2.1 if they're not ready to consume it, but I do want them to periodically run yum update and fetch bug fixes (or security fixes from upstream repos).</div><div><br></div><div>So: can pulp repositories be grouped in a logical way? I noticed pulp-admin repo group exists, is that the way to do it? The docs at <a href="https://pulp-user-guide.readthedocs.org/en/pulp-2.2/admin-client/repositories.html">https://pulp-user-guide.readthedocs.org/en/pulp-2.2/admin-client/repositories.html</a> seem to imply there is further development needed to make this useful.</div><div><br></div><div>Second: is there any meta-information about repositories in yum, that would group a bunch of repos together? I would prefer not to parse HTML when trying to determine new versions of the repositories.</div><div><br></div><div>Thank you again!</div><div>Mihai</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 11, 2015 at 2:10 PM, Baird, Josh <span dir="ltr"><<a href="mailto:jbaird@follett.com" target="_blank">jbaird@follett.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div lang="EN-US" link="blue" vlink="purple"> <div> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi,<u></u><u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">We create dated snapshots of RHEL repositories (using pulp rpm repo copy). For instance, for 7Server, we may have the following repo path:<u></u><u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">/pulp/repos/rhel/7Server/x86_64/snapshot/20150727/{os,extras,rhscl,etc}<u></u><u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Our configuration management system allows us to define a snapshot date for each tier of host in our environment (DEV, QA, PROD, etc). When we cut a new snapshot (usually quarterly), we 'pulp rpm repo copy rpm' from the "bleeding edge" RHEL repository (which is synced nightly) to the snapshot repository. All DEV hosts get pointed at the new repository for testing, and eventually we point all PROD hosts to the new snapshot date once the updates have been tested.<u></u><u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">For each dated snapshot, we also have an "emergency" repository:<u></u><u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">/pulp/repos/7Server/x86_64/snapshot/20150727/emergency<u></u><u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">This repository is used to promote critical/emergency packages out of band. In this case, we again use 'pulp rpm repo copy' to promote individual packages from the 'bleeding edge' repository into the dated 'emergency' snapshot repository. This makes critical packages immediately available to all hosts currently assigned to that snapshot without having to cut an entirely new snapshot of all packages.<u></u><u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Our hosts are provisioned using the snapshot repositories as well, which ensures that all systems have a consistent set of packages. Hope this helps.<u></u><u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thanks,<u></u><u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Josh<u></u><u></u></span></p> <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p> <div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"> <div> <div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in"> <p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:pulp-list-bounces@redhat.com" target="_blank">pulp-list-bounces@redhat.com</a> [mailto:<a href="mailto:pulp-list-bounces@redhat.com" target="_blank">pulp-list-bounces@redhat.com</a>] <b>On Behalf Of </b>Mihai Ibanescu<br> <b>Sent:</b> Friday, September 11, 2015 12:43 PM<br> <b>To:</b> pulp-list<br> <b>Subject:</b> [Pulp-list] Repository layout<u></u><u></u></span></p> </div> </div><div><div class="h5"> <p class="MsoNormal"><u></u> <u></u></p> <div> <p class="MsoNormal">Hi,<u></u><u></u></p> <div> <p class="MsoNormal"><u></u> <u></u></p> </div> <div> <div> <p class="MsoNormal">Is there a best practice document for how to keep a set of systems on a specific version of a distro? <u></u><u></u></p> </div> <div> <p class="MsoNormal"><u></u> <u></u></p> </div> <div> <p class="MsoNormal">Say, all the testing was done against Centos 6.5, but 6.6 and 6.7 are out. I want my production systems to work with 6.5 but my QA is on 6.6 and I am developing against 6.7.<u></u><u></u></p> </div> <div> <p class="MsoNormal"><u></u> <u></u></p> </div> <div> <p class="MsoNormal">I am trying to figure out how to lay out the repositories in pulp. I suspect the answer is 3 different repos, and creatively/carefully copying errata (with their packages) from 6.7 into the 6.5 repo.<u></u><u></u></p> </div> </div> <div> <p class="MsoNormal"><u></u> <u></u></p> </div> <div> <p class="MsoNormal">Please don't ask why I wouldn't want to be on latest all the time. It is a somewhat contrived example of a real-life situation.<u></u><u></u></p> </div> <div> <p class="MsoNormal"><u></u> <u></u></p> </div> <div> <p class="MsoNormal">Thank you!<u></u><u></u></p> </div> <div> <p class="MsoNormal">Mihai<u></u><u></u></p> </div> </div> </div></div></div> </div> </div> </blockquote></div><br></div>