f7470252cb
As part of rehoming, the keystone password for sysinv is updated for
the new SystemController value. A callback then comes from keystone
to sysinv in which the secrets that contain the password used to
authenticate to the docker registry for each namespace are updated.
However, since the playbook needs to restart sysinv right away,
there is a racing condition between this callback and the sysinv
restart. To prevent this, this change adds a script that makes a
RPC call to sysinv, to run the audit that updates the credentials
in the secrets in a synchronous way (w/o waiting for the callback).
PASS: Rehome a SX subcloud
Confirm that the registry secrets were updated
PASS: Enroll SX subcloud
Depends-on: https://review.opendev.org/c/starlingx/config/+/963219
Closes-bug: 2126680
Change-Id: If595916b87e2c0cbfce60721547ea74d6ac4b168
Signed-off-by: Marcelo de Castro Loebens <Marcelo.DeCastroLoebens@windriver.com>
stx-ansible-playbooks
StarlingX Bootstrap and Deployment Ansible1 Playbooks
Execution environment
- Unix like OS (recent Linux based distributions, MacOS, Cygwin)
- Python 3.8 and later
Additional Required Packages
In addition to the pakages listed in requirements.txt and test-requirements.txt, the following packages are required to run the playbooks remotely:
- python3-pexpect
- python3-ptyprocess
- sshpass
Supported StarlingX Releases
The playbooks are compatible with StarlingX R8.0 and later.
Executing StarlingX Playbooks
Bootstrap Playbook
For instructions on how to set up and execute the bootstrap playbook
from another host, please refer to the StarlingX Documentation2, at
Installation Guides, section Configure
controller-0 of the respective system deployment type.
Developer Notes
This repository is not intended to be developed standalone, but rather as part of the StarlingX Source System, which is defined by the StarlingX manifest3.