[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

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)
_______________________________________________
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/JB3R3GIG3AG3K6BMGWWGPYK5BWFOAV7P/

Reply via email to