old run-upgrade script should be left in place

[Darren Birkett]

The original run-upgrade script in kilo was being used, and is what was tested, in our environments. The new rewritten script may be better, but IMHO we should leave the old one in place, and rename the new one to run-upgrade-new.

This gives deployers the option of still using the original script, on which they may have based their upgrade tooling, but also the option of moving to the new script in the future once they are able to complete testing with that too.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit 72eaf7c5f263b9ca78b5c35f4b4b48dd3e5ef335
Author: Darren Birkett <email address hidden>
Date: Fri Oct 16 10:21:59 2015 +0100

    put old run-upgrade script back

    This commit puts the original run-upgrade script back in place as
    run-upgrade-old.sh

    Whilst the new script is undoubtedly better, the original script should
    remain in tree to be used by deployers who may have built some tooling
    around it.

    Closes Bug: #1506788

    Change-Id: Iad783c07ef746463e2b52be4bc9857bd63993691

[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.