in kilo, repo-clone-mirror syncs a lot of unneeded data from the upstream mirror

[Darren Birkett]

The directory structure that currently makes up the default upstream repo server (rpc-repo.rackspace.com) that the repo-clone-mirror play clones from looks like this:

756M container_images
14M downloads
4.0K index.html
4.7M links
612M mirror
1.3G openstackgit
24M os-releases
2.4G pools
626M python_packages
4.0K README
3.9M reports
875M rpcgit
0 rpc-trusty-container.tgz
2.4G venvs

Already excluded are

/repos (no longer present in the upstream repo)
/mirror
/rpcgit
/python_packages

see https://github.com/openstack/openstack-ansible/blob/kilo/playbooks/repo-clone-mirror.yml#L34-L38

We can save more data transfer and time if we also exclude:

/openstackgit
/downloads
/venvs
/container_images

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: kilo
Review: https://review.openstack.org/278343

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/278343
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=aff56426c4bb6f64948e2f684a531eb4b07f01c2
Submitter: Jenkins
Branch: kilo

commit aff56426c4bb6f64948e2f684a531eb4b07f01c2
Author: Darren Birkett <email address hidden>
Date: Wed Feb 10 12:52:10 2016 +0000

    only sync the necessary directories in repo-mirror-sync

    This commit switches the rsync method to only include the necessary
    directories to be synced, and thereby excludes all additional
    directories not needed by kilo, and speeds up the clone of the
    upstream repo mirror (by default rpc-repo.rackspace.com).

    Change-Id: I199f5ca876ae2f57ee2f6b3474f476f74829efee
    Closes-Bug: #1544035

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 11.2.15 release.