The exit 0 is not recommended:
- If this script is forked, it will exit 0 anyway, so the exit
is useless
- If this script is in the same shell, it will exit current fork
with no valid reason
Change-Id: Id86af084e0c93856986814b14ad55c4bc8c8e613
The leapfrog is quite static, and a deployer can only run
scripts before and after the process.
By adding this, a deployer can alter the re-deploy behavior.
It can now run playbooks or shell scripts after the migrations,
and modify the re-deploy behavior (by adding more playbooks for
example).
Change-Id: Idde1e94d014fe4ca527568641a04c847a710d801
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>
