[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38996#comment-38996
 ] 

Roman Mohr commented on OVIRT-2590:
-----------------------------------

Thinking about our CI images it can avoid peaks on the network consumption. 
Right now you need all of our lanes to have run on each bare-metal machine 
until all nodes have a cache for each image. They have up to 8gb. It is another 
measure to reduce the amount of failing tests because of networking issues. 
Setting it up should be pretty simple. The mirror needs then just to be 
injected before starting docker.

> Cache Docker images in the datacenter
> -------------------------------------
>
>                 Key: OVIRT-2590
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2590
>             Project: oVirt - virtualization made easy
>          Issue Type: Improvement
>            Reporter: Roman Mohr
>            Assignee: infra
>
> What?
> As a user, I expect that I don't have to care about caching to speed up
> builds for  the good of the CI system itself.
> Right now there exists a whitelist for docker images, which will not be
> remove from the build slot after the build. Instead of that I expect a
> clean build environment and that in general all images which I regularly
> use are cached in the cluster via e.g. a pull-through-cache [1].
> Why?
> 1) Caching in a build slot is not very effective. CI runs do really-a-lot
> of almost identical things in a small time-window (e.g. days). If caching
> happens in the build-slot and many slots are present, then the cache
> utilization will be very low.
> 2) Whitelisting docker images extra for a slot where the registry runs in,
> is very error prone and since it is not cached across the cluster it is
> also very intransparent what the clear benefit for the user is. Especially
> when thinking about scaling a CI system, that seems to leak internal
> optimizations to the user. Fast builds are twice as important for the CI
> system than they are for the users (by default faster and lower utilization
> is always better than asking people to optimize on their side).
> [1] https://docs.docker.com/registry/recipes/mirror/



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100098)
_______________________________________________
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/G5VZHUUYMIXDH7BR3AXMSYIYFHNWPGFU/

Reply via email to