Need to have working quantum-tarball jobs

The venv-rename has merged, so I have updated the copy job with the new name, so the tarball job now gets past that point.

The strange name comes from the fact that quantum has a version.py that uses 'git describe' to try to construct a version name. Jenkins tags builds in its local repository before running jobs, and the tarball name is based on that tag. I think the right solution is to make quantum's version naming like glance.

After that, the directory permissions on the tarball server are incorrect for glance. I will fix those _after_ the tarball job is otherwise running to our satisfaction.

Hi James,

Is there a dump of the failure? Anything you need from our team to get this working? I appreciate you working on getting quantum into standard release management.

Ah, just saw the review on quantum. will get that reviewed asap.

Reviewed: https://review.openstack.org/3072
Committed: http://github.com/openstack/quantum/commit/c6ffd875df384313e7b22214b75e00f735c06338
Submitter: Jenkins
Branch: master

commit c6ffd875df384313e7b22214b75e00f735c06338
Author: James E. Blair <email address hidden>
Date: Tue Jan 17 08:02:10 2012 +1100

    Base version.py on glance.

    This makes setting and calculating the versioning of quantum more
    like other OpenStack projects, simplifying the work of the CI
    and Release Management teams.

    Addresses bug 916018 which prevents the quantum-tarball job from
    running correctly.

    Change-Id: I5b006ccc3d31c5d213c703853dfa38f04d983918

This is fixed for master, and the milestone version of the job looks the same so once there is a milestone-proposed branch that is branched after the venv rename, it should work (but can't be tested now).