I have tried to use the pulp export functionality in an industrial context
(several hundred repos).
It works, but it isn't up to the task in my industrial context.
It might be ok for one or two repos, but for multiple related repos (e.g.
multiple versions of RHEL), there are severe issues:
* The expert process is very slow.
* Every repo exported contains its own full copy of each RPM. When
exporting related repos, this adds up to a huge amount of wasted space. So
much so that I could only export a fraction of my repos to a 6Tb HDD (pulp
internally stores all my repos in less than 2Tb by storing each RPM only
once, and sharing it between repos that need it).
This is just my experience of exporting repositories from pulp. Feel free
to try it out and add your own remarks.
Ben.
On 20 May 2016 4:32:35 am Jeremy Audet <[email protected]> wrote:
Is there anything about Satellite/Katello that negates being able to use
the Pulp features directly?
I don't know about that. Take my thoughts below with a grain of salt.
I don't know too much about Pulp itself but I'm sure there must be an
export mechanism.
Yes, Pulp has export mechanisms. For an example of how to export a
repository via the CLI, see export repositories and repository groups
<http://pulp-rpm.readthedocs.io/en/latest/user-guide/recipes.html#export-repositories-and-repository-groups>.
For a known-working example of how to export an RPM repository via the v2
API, see:
-
http://pulp-smash.readthedocs.io/en/latest/api/pulp_smash.tests.rpm.api_v2.test_export.html
-
https://github.com/PulpQE/pulp-smash/blob/master/pulp_smash/tests/rpm/api_v2/test_export.py
This code is known to function on Pulp 2.8 and master (2.9).
-Jeremy
----------
_______________________________________________
Pulp-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________
Pulp-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-list
