I would create a repo called "latest" which I would sync every quarter. Right after every sync, I would create the snapshot "2016XXYY" by copying all the content of the "latest" repo to the snapshot repo:
# Do once: pulp-admin rpm repo create --repo-id latest --feed https://server.com/path/to/the/repo/ # Do every quarter: pulp-admin rpm repo sync run --repo-id latest pulp-admin rpm repo create --repo-id 2016XXYY pulp-admin rpm repo copy all --from-repo-id latest --to-repo-id 2016XXYY The snapshot repo won't take any extra disk space as it's just a bunch of symlinks. On Fri, Jun 17, 2016 at 5:08 PM, Kodiak Firesmith <kfiresm...@gmail.com> wrote: > Well an RPM repo copy job is basically just a ton of symlinks. The > problem you'll have is each time you do it if you want the old stuff gone > before updating -latest to the newest snapshot copy you'll have to remove > everything in latest then re-copy. > > I don't see an easier way but then again we roll risky - we let the > updates come as they appear upstream. > > On Fri, Jun 17, 2016 at 12:00 PM, Baird, Josh <jba...@follett.com> wrote: > >> Yeah, this does work. I was hoping to be able to somehow do this via the >> API or pulp-admin since that’s how we create the snapshots. >> >> >> >> *From:* Kodiak Firesmith [mailto:kfiresm...@gmail.com] >> *Sent:* Friday, June 17, 2016 11:57 AM >> *To:* Baird, Josh <jba...@follett.com> >> *Cc:* pulp-list@redhat.com >> *Subject:* Re: [Pulp-list] Publishing web-accessible symlinks >> >> >> >> Dunno how technically correct this solution is, but it seems to work: >> >> $pwd >> /var/www/pub/yum/https/repos/ >> >> $sudo -u apache ln -s rhel-os/server/7/7Server/x86_64 rhel-7-latest >> >> $ls -lah >> drwxr-x---. 3 apache apache 33 Jun 17 10:38 rhel-os >> lrwxrwxrwx. 1 apache apache 31 Jun 17 11:49 rhel-7-latest -> >> rhel-os/server/7/7Server/x86_64 >> >> Contents of my RHEL 7 repos are now avail at rhel-7-latest: >> https://pulp-beta.somecollege.edu/pulp/repos/rhel-7-latest/ >> >> That's a helluva lot simpler than my original thought for you quandry >> which would be to create a blank repo called rhel-7-server-latest, do an >> rpm copy job on all the rpms in your latest snapshot, then tear that >> -latest repo down and recreate quarterly with the new latest quarterly >> snapshot. >> >> - Kodiak >> >> >> >> >> >> On Fri, Jun 17, 2016 at 11:21 AM, Baird, Josh <jba...@follett.com> wrote: >> >> Hi, >> >> >> >> We cut quarterly snapshots of the RHEL repositories and publish them as >> ‘/rhel/7Server/x86_64/snapshot/2016XXYY.’ I’m looking for a way to create >> a ‘latest’ symlink (/rhel/7Server/x86_64/snapshot/latest -> 2016XXYY) that >> links to the latest snapshot date available. >> >> >> >> Is there any way to create and publish web-accessible symlinks with Pulp? >> >> >> >> Thanks, >> >> >> >> Josh >> >> >> _______________________________________________ >> Pulp-list mailing list >> Pulp-list@redhat.com >> https://www.redhat.com/mailman/listinfo/pulp-list >> >> >> > > > _______________________________________________ > Pulp-list mailing list > Pulp-list@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-list >
_______________________________________________ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list