The client utils will now run a new playbook to ensure that the local
archive directory is created early in the deployment process. This
change will allow us to build toward a swift-less deployment. All of
the client calls, save one, has been moved to use tripleo-common which
will assist us to better manage, and migrate from swift storage to a
local archive.
> As a product of this change all of the "webhook" calls have been
removed. which was deprecated as part of the Zaqar and Mistral work.
These calls were removed because several swift calls were tied into
them, and because mistral is no longer part of the stack, and has
been gone for a few cycles, we can safely remove these calls which
do nothing.
Depends-On: Ibe9b2ffe94cdf493fc84366979d1d78b8528ea1b
Change-Id: I7531612a49527f8a21df415c648acb41ac7a0b10
Signed-off-by: Kevin Carter <kecarter@redhat.com>
Fix misused ansible connection timeout and deployment timeout passed in
config download and ansible runner utility.
Allow ansible runner utility to be given a job_timeout as well.
Also fix the misuse of timeout parameters in related worklows. Add
--overcloud-ssh-port-timeout and use it to configure ansible connection
timeout for the DeleteNode interace of the involved
workflows. Then use the timeout parameter as real timeout instead of
mistakingly passing it as a connection timeout.
Add new unit test for ansible timeout in config_download. Add missing
coverage for the existing timeout-related params in other unit tests.
Closes-Bug: #1868063
Co-authored-by: Kevin Carter <kevin@cloudnull.com>
Change-Id: I2a4d151bcb83074af5bcf7d1b8c68d81d3c0400d
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
This change will now use an ansible playbook to parse the horizon URL
information from a heat stack and return the connection string
accordingly.
Story: 2007212
Task: 38429
Depends-On: https://review.opendev.org/#/c/706196/
Depends-On: I85cb99d47cf3cb4f3093fc856e9f6892115ff5ef
Change-Id: I78e68147fc30ff4d71edb023f553219d553b53a6
Signed-off-by: Kevin Carter <kecarter@redhat.com>
This change creates a context that mimics the Mistral context. This
allows us to short-circuit and cut Mistral out, calling the Python
action directly.
All plan list actions have been updated to use this new process and
the old mistral function has been deleted.
Story: 2007247
Task: 38594
Depends-On: https://review.opendev.org/#/c/706196/
Change-Id: I463b5e3d1c4c15dd859a841d65a5057716f84208
This change has two main parts:
* Ensure that when we ssh *via Mistral*, we always use
tripleo-admin. `--ssh-user` argument to any update/upgrade run
commands is now deprecated. The reason i didn't remove it completely
is that how current upgrade commands use ssh needed some mental
untangling, and i want us to keep an easy way back in case my
understanding is wrong here. Deprecation seems safer than outright
removal.
* On upgrade prepare and FFWD prepare, make sure that the
tripleo-admin user is created and authorized.
Note that for tripleo-admin creation and authorization, the
`--overcloud-ssh-user` parameter is used, and that one still
defaults to `heat-admin`, which is correct. So initially we connect
via whatever credentials user provided (which works on Nova+Ironic
envs unless user customized it), and from that point on we always
use tripleo-admin, which is common for all environments regardless
of any user customizations. This is how deployment already works
now, and after this change upgrades will work that way too.
Change-Id: Ib1a75a0a3f3b2a3bec00d8820c3a097620fa6256
Closes-Bug: #1801066
There were a couple spots where the deployment status was not properly
updated. The first was when the stack failed, the deployment status also
needed to be set to failed.
The second is when we start the config_download process, the status
needs to be set to deploying.
Depends-On: I87b97bcab3e8cec6bdbb79c0acb95a375bb2d2fa
Change-Id: Ida519df829450c1ce9216049d76bc098176c273b
Closes-Bug: #1795640
Kevin Carter