3 Commits

Author SHA1 Message Date
Jean-Philippe Evrard
50f3fd6df7 Ensure the user_secrets file is updated
We shouldn't allow any arbitrary secret file to be updated in the
leap process, but instead ensuring the file present in
J/K/L will be properly updated to the end of the process.

If you had set the variable in those playbooks, you would
naturally CREATE a new file, alongside the existing user_secrets,
with the risks of:

- Having different values
- Having precedence issues depending on the file name

Change-Id: I2873318e2f1fd34673e95f8eb77a0001d649df1e
2017-08-31 09:27:55 +00:00
ZhongShengping
2c4f4cc434 Update URLs in documents according to document migration
Change-Id: I213c3a4569d0ba67c6f373e44dbfa8a37c24599b
2017-07-14 13:54:50 +08:00
Kevin Carter
2438ad03ab Added leap upgrade tooling
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>
2017-02-01 14:27:07 +00:00