<div dir="ltr"><a class="gmail_plusreply" id="m_-566526620781443193plusReplyChip-0" href="mailto:JDavis@douglas.co.us" target="_blank">@Jim Davis</a> My takeaway from this is that we need a verbatim mirror feature for pulp_rpm. Thanks for sharing that use case. </div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 22, 2020 at 11:28 AM Jim Davis <<a href="mailto:JDavis@douglas.co.us" target="_blank">JDavis@douglas.co.us</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div lang="EN-US"> <div> I do think it is important that it is possible to have a verbatim repo replication happen in a true mirror fashion rather than massaging it. We have audits we need to pass and a file by file “bits is bits” comparison from what we have and what is available in the official repo may likely fail. I have been looking at the workflows docs and all the associated script samples over the last few days. It is an interesting read but no where near the rpm repo create and rpm repo sync that will give me an exact mirror (honestly, I was looking for the easy button to mirror an external repo). My requirements are also that I sync only when the patching process needs refreshed and everything gets tested with that snapshot. Outside of that manual sync, the repo would remain static. I haven’t looked at squeezer yet but I will. Everything else I do is ansible based. Many thanks! Jim From: Matthias Dellweg <<a href="mailto:mdellweg@redhat.com" target="_blank">mdellweg@redhat.com</a>> Sent: Tuesday, September 22, 2020 5:11 AM To: Jim Davis <<a href="mailto:JDavis@douglas.co.us" target="_blank">JDavis@douglas.co.us</a>> Cc: <a href="mailto:pulp-list@redhat.com" target="_blank">pulp-list@redhat.com</a> Subject: Re: [Pulp-list] Simple use case of mirroring external repos in pulp3 <div> <div> Hi Jim, </div> <div> thanks for reaching out. I think the use case you are describing here is best described in <a href="https://pulp-rpm.readthedocs.io/en/latest/workflows/create_sync_publish.html#sync-publish-workflow" target="_blank"> https://pulp-rpm.readthedocs.io/en/latest/workflows/create_sync_publish.html#sync-publish-workflow</a> . </div> <div> And yes it is necessary to sync, publish and distribute that repository to have a mirror. Also this mirror will AFAIK republish the synched repository in its own layout. (Anyone, please help me out if i'm wrong!) </div> <div> We have recently discussed the possibility to republish synched repository versions in a verbatim manner (including all files and original metadata in their original relative location). Let us know if that is an important use case for you. </div> <div> As of the CLI for pulp3, it is in a very ealy poc/planning phase. But personally, i would love to hear if you made any experience with using the ansible modules in <a href="https://galaxy.ansible.com/pulp/squeezer" target="_blank">https://galaxy.ansible.com/pulp/squeezer</a> (also incomplete, but there are some for use with RPM facilities). </div> <div> Matthias </div> </div> <div> <div> On Mon, Sep 21, 2020 at 10:27 PM Jim Davis <<a href="mailto:JDavis@douglas.co.us" target="_blank">JDavis@douglas.co.us</a>> wrote: </div> <blockquote style="border-color:currentcolor currentcolor currentcolor rgb(204,204,204);border-style:none none none solid;border-width:medium medium medium 1pt;padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in"> <div> <div> For some time now I have built up several pulp2 mirrors of various upstream rpm repos to make local updates run faster and to segregate environments. I do not require client registration so it is a dirt simple setup for basic OS patching. It is trivial to rebuild my rpm repositories if needed and to sync them as needed via scripts using pulp_admin. I’m trying to figure out how to do this with pulp3 – and I’m still a bit puzzled. The pulp3 ansible deploy method is really quite slick. One issue down. Simply mirroring outside repos is quite common with pulp2 usage and documented everywhere in the webnets but not so much for pulp3. I realize the CLI went away but surely there must be some pulp2 to pulp3 task equivalence somewhere or maybe someone has real world examples written up already and hasn’t yet published them. Searching/reading/searching gives me lots of information on complex issues around document versioning, history, plugins, API usage, pulp3 architecture, etc. For me this makes a simple migration to pulp3 more difficult for probably the easiest use case out there. Am I too early to the game to consider a move or is it all in front of me but in a million pieces! Thanks Jim </div> </div> _______________________________________________ Pulp-list mailing list <a href="mailto:Pulp-list@redhat.com" target="_blank">Pulp-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/pulp-list" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-list</a> </blockquote> </div> </div> </div> _______________________________________________ Pulp-list mailing list <a href="mailto:Pulp-list@redhat.com" target="_blank">Pulp-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/pulp-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-list</a></blockquote></div>