For yum, I disable fastestmirror, set hard-coded repo sites, then configure an http_proxy.

For apt, I set hard-coded repo sites, then configure an http_proxy.

This seems much lighter weight then cloning an entire OS distribution, when most packages aren't going to be installed anyways.

ps: if you leave fastestmirror enabled, then the download site will change randomly, so a proxy is worthless. Also, the centralized site that fastestmirror talks to seems to be highly unstable, and returns spurious errors, which cause the ansible yum module to abort, but only sometimes. This isn't a bug in ansible, but in the yum python module that ansible uses.

On 02/27/2014 07:15 AM, Michael DeHaan wrote:
We've been through this discussion a bit before, and we believe the
repoquery needs to be there.

I'm a bit more curious about why you are spending so much time in the
operation and most people are not.

When using yum in any sort of important setup, I almost always create a
yum mirror with reposync, etc, and even in our testing, we're not seeing
any major timing issues with the yum options at all.

yum_rhn_plugin can sometimes be a very very different story (hence even
more reason to mirror content).

--
You received this message because you are subscribed to the Google Groups "Ansible 
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/530F7A50.8070902%40brainfood.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to