[JIRA] (OVIRT-902) Speed up mock_runner.sh setup time by using caches.

[Barak Korren (oVirt JIRA)]

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

Barak Korren commented on OVIRT-902:
------------------------------------

[~ykaul] The packages install is done by mock itself during the setup of the chroot - so could probably be sped up.

All the rest:
* The pip stuff
* The autogen w/o locale
* other package installs  
All come from inside check_patch.sh (from vdsm repo) so do not belong on this ticket.

Having said that, yum in the mock env is running through oVirt's proxy - so not really going to the internet (pre-post install script still takt time though which is why the mock setup is long).

We could probably find one way or another to make pip go through the proxy too to make it a little faster (Maybe export the "_http_proxy_" env var in to the mock env .to make scripts able to leverage it).

Looking deeper into our scripts, this can be found in mock_cleanup.sh:

{code}
# remove mock system cache, we will setup proxies to do the caching and this
# takes lots of space between runs
shopt -u nullglob
sudo rm -Rf /var/cache/mock/*
{code}

We probably need need remove that before we can gain any speed ups. But we must heed David's warning and make sure we zap the caches frequently enough so we don't fill up the slaves.


> Speed up mock_runner.sh setup time by using caches.
> ---------------------------------------------------
>
>                 Key: OVIRT-902
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-902
>             Project: oVirt - virtualization made easy
>          Issue Type: Improvement
>            Reporter: Barak Korren
>            Assignee: infra
>            Priority: High
>              Labels: mock, mock_runner.sh, standard-ci
>
> We've already known that setting up mock takes a while, but mock has some built-in caching features that should allow us to speed this up.
> We need to ensure those features are enabled by mock_runner.sh. The mock options to look at are:
> * root_cache_enable
> * yum_cache_enable
> Both these options should be set to true in the mock chroot config file.
> We've been using these option downstream in minimead and the vdsm build scripts, so they should be safe to use.



--
This message was sent by Atlassian JIRA
(v1000.610.2#100023)