How to use pulp3 to match a pulp2 configuration

Support
#1

I am building a pulp3 environment, and having trouble doing repo administration

In pulp2 I had the following
oracle8_base repo (mirrored from oracle yum) - updated each day, and published
oracle8_base_“dated” repo - a copy of the latest modules in the oracle8_base repo on a date, and then published.

I’m trying to build this in pulp3, and not having a lot of success.
I’m building a “rpm remote” repository, then a “rpm repository” for a date, which is a sync against the “rpm remote” and then doing a “rpm publication” and ,“rpm distribution” of the “rpm repository”
I sync the “rpm repository"date”" against the “rpm remote”, but this is using a large amount of space in the tmp filesystem (to the extent that the sync fails when there is 100Gb of spare disk space)

I have:
[root@node ~]# pip list | grep pulp
pulp-cli 0.21.4
pulp-glue 0.21.4
pulp-rpm 3.24.0
pulpcore 3.41.0
[root@node ~]#
Oracle Linux Server release 9.3
NAME=“Oracle Linux Server”
VERSION=“9.3”

is this the correct process?

#2

You should probably look at the “workflows” section in the rpm plugin docs.

But one thing to start off: I think you only need a single repository and a single remote. If you then sync daily you will get an immutable repository version each day. You can then publish that repository version to obtain your daily publication. At last you can decide whatever publication(s) you want to distribute at what base_path by providing one distribution for each.

About the use of diskspace in the sync task, there has recently been some movement. Not quite sure it’s related: file:// sync deletes files from directory · Issue #4681 · pulp/pulpcore · GitHub

1 Like