Because "newton" is the last release LEAP upgrades are compatible with
there's no need to build a migration venv for newton. All of the newton
specific migrations will be run during the redeployment phase so this
venv has no specific purpose and is simply prolonging an already long
maintenance.
Change-Id: I06f23ed3bfdca5f1d5d56cb9fabd53cab01b83b6
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
Leapfrogs currently only work with Juno/Kilo
releases as certain parts are hard coded.
This patch adds support for handling
multiple releases and attempts to remove some
duplicate code with loops.
Also adds a UPGRADES_TO_TODOLIST variable check on
migration.sh and upgrade.sh to ensure the list of
releases to be ugpraded to are set if the commands
are ran individually.
Change-Id: Ia56f073863533d4b6fa58b78b59b5086c7f9a331
run_ansible wrapper should work in the latest checkout of OA,
which should be in a REDEPLOY folder instead of just
a static "/opt/openstack-ansible"
Change-Id: I4d20fd7480f2f38e55d3f081c0c0f11726458583
Some providers may have a different bootstrapping script,
and probably want to use their own instead of always
bootstrapping the OSA one for the leap.
We should be able to give a script as env var, and use
that script for installing an ansible that works for leapfrog.
Change-Id: I034d3dace52ae092e04d4573c6299b464153084d
While we could do better by using other mechanisms than shell
scripts, this commit sticks to the current method of doing (having
marker files), to mark steps that were missing a marker.
On top of it, you couldn't resume from a leapfrog that's started
from a shell script, because the readlink failed.
Change-Id: I73f09bb8214741772545c73fac5e5fdb5698c52e
This change:
- discovers the current running version to know what
to leap from, because we can't assume Juno only.
At the same time it introduces a human verification
of the source branch.
- removes the useless "-v" of the runs that produced
an undesirable output, making the interface less
"user friendly".
Change-Id: I04e4780bf5f58638addbd992eab7152f288532ae
Co-Authored-By: Jean-Philippe Evrard <jean-philippe@evrard.me>
This change adds upgrade tooling that will take a Juno based
OpenStack-Ansible cloud and upgrade it to Newton. The tooling
will run a deployment through all of the needed steps upgrading
the environment and skipping all of the OpenStack releases in
between.
**This tooling should be considered experimental at this time**
Change-Id: I1880794717b9e47786ae255ea1afa57d805cde8e
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
