[Pulp-list] Incremental Pulp Imports

Michael Hrivnak mhrivnak at redhat.com
Wed May 14 13:13:23 UTC 2014


It sounds like you've already been through the documentation, but for others' reference, it is here: http://pulp-rpm-user-guide.readthedocs.org/en/pulp-2.3/recipes.html#export-repositories-and-repository-groups

When you do an incremental export, you get the files that are required to upload each additional unit to the disconnected pulp. The json blobs are meant to be passed right in to the upload API. I don't recall off the top of my head their exact content, but presumably they contain the "unit_key" and "metadata" required to pass into this call: https://pulp-dev-guide.readthedocs.org/en/pulp-2.3/integration/rest-api/content/upload.html#import-into-a-repository


----- Original Message -----
From: "Edward khalaf" <ezkhalaf at gmail.com>
To: pulp-list at redhat.com
Sent: Monday, May 12, 2014 8:54:19 PM
Subject: [Pulp-list] Incremental Pulp Imports


I have a Pulp server pulling in packages from Red Hat and need to be able to update an external Pulp server that is in a closed environment. I have created the incremental exports with the pulp-admin utility. I noticed in the documentation that pulp-admin did not have the ability to import incremental exports and that the REST API should be used. I noticed in the export there were json files for errata and package info. I'm a bit of a noob and can't figure out how to use the REST API to import my updates. Can someone point me in the right direction?!? 


Pulp-list mailing list
Pulp-list at redhat.com

More information about the Pulp-list mailing list