[ https://ovirt-jira.atlassian.net/browse/OVIRT-2034?page=com.atlassian.jira.p... ] eyal edri updated OVIRT-2034: ----------------------------- Epic Link: (was: OVIRT-403)

Recreate the transactional CI mirrors with Pulp -----------------------------------------------

Key: OVIRT-2034 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2034 Project: oVirt - virtualization made easy Issue Type: New Feature Components: CI Mirrors Reporter: Barak Korren Assignee: infra

Right now, the CI mirrors are created and maintained by a set of custom scripts and jobs. It seems that [Pulp|https://pulpproject.org/] can do what our current system does. The reason behind not using it when we first made the mirrors system was out desire to provide a quick solution and avoid adding more services to maintain. There are however, quite a few reasons to want to switch to pulp: # Aside from RPMs it can also manage other interesting kinds of resources like Containers, DEB packages and Python packages. # If it works well for us - we can maintain less code by dropping the existing mirror management code # It has built-in distribution mechanisms that can be useful to scale it up. # It seems it has support for assigning packages to multiple repos. This cab be used as a tagging mechanism to implement OVIRT-2033

-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)