Hello, I’m trying to sync the Chef repository (hosted in package.io) into Foreman (theforeman.org) which uses Pulp but I’m not having any luck. When I contacted support at package.io, it turns out that they store everything in S3 storage in the background and only expose over http what yum needs to be able to see the packages.
However, this is apparently not enough for pulp to be able to do repo-discovery and sync the repository. What does pulp expect when it’s looking at a repository? (e.g. it looks like pulp breaks if the actual URI of the rpm is not the same as the URI of the directory structure) Are these expectations documented somewhere? In short I want to give the guys at package.io a list of what pulp expects to see if there is anything they can do about supporting it. Thanks, David From: [email protected] [mailto:[email protected]] On Behalf Of packagecloud.io support Sent: Friday, January 30, 2015 1:45 AM To: Somers-Harris, David | David | OPS Subject: Re: Repo Syncing Joe Jan 29 4:44pm Yes we are using S3. It's likely that pulp and similar tools would use the actual metadata found in the repository as opposed to traversing the directory structure itself. Can you share some example URLs that work and I can show you similar URLs on packagecloud? In theory, pulp should simply need to know where to find the yum metadata and everything else will be taken care of itself. -- Joe Damato [email protected]<mailto:[email protected]> David | David | Ops Somers-Harris Jan 29 9:34am Hi Joe, Thanks for the reply. Foreman uses Pulp for handling its repositories. http://www.pulpproject.org/ I think it basically does an http scrub with something similar to rsync. We don't mind hosting large amount of data locally, it gives us more control and reduces our bandwidth. I think Package Cloud would either need to simulate the full directory over http or Pulp would need to have a plugin to understand your API. Do you use object storage compatible with S3? Regards, David Somers-Harris Global Operations Department [[email protected]] Joe Jan 26 7:58am Hi David: No, that's not possible because packagecloud doesn't work that way -- there are no actual directories mapped to a filesystem as you would get if you were using createrepo. I have no idea how Foreman works, but if you can provide more details on how Foreman's syncing/mirroring works, I can probably help you figure out what you need to do to accomplish this. packagecloud serves up files and metadata at URLs that yum and apt expect but those URLs are just an abstraction over how we store the data. Keep in mind that packagecloud is actually able to retain all previous versions of uploaded packages, which means that if you are mirroring the entire Chef Stable Enterprise Linux repository for any individual version of Enterprise Linux, you will be consuming *considerable* disk space on your side. -- Joe Damato [email protected]<mailto:[email protected]> David | David | Ops Somers-Harris Jan 26 7:24am Hello, I would like to see directory listing under https://packagecloud.io/chef/stable/el so that I can sync to my local repo into Foreman<http://theforeman.org/>. Is this possible? Thanks, David [http://secure.helpscout.net/notification/convo/read/67557052/170135027/] {#HS:67557052-1014#}
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
