StarlingX Ansible Playbooks
51a8df2f73
Subcloud prestage operations were intermittently failing rsync due to incompatible file permissions. Occasional ostree CLI commands get issued which create transient files under the given repo. .tmp directory and various files get created, renamed, and deleted (e.g., .lock, tmp.X, summary). These files are owned by root, whereas the repo's files are owned by sysadmin during rsync operation on the target. This update excludes the tmp pattern during the rsync operation since they are not required. This also modifies file permissions during the rsync to be ugo+rw. Closes-Bug: 2092319 TEST PLAN: - PASS: DC Scale lab batch subcloud prestage - PASS: Prestage a subcloud running N release with N-1 load for install. Restore the subcloud to N-1 release from backup. Verify the restore is successful. - PASS: Prestage a subcloud with an N-1 subcloud with a major release. Verify that the deployment of a major release is successful. - PASS: Prestage a subcloud with a minor release. Verify that the deployment of the minor release is successful. Change-Id: Ia63be9f4de552efbd1551857b0b5864c87879a23 Signed-off-by: Jim Gauld <James.Gauld@windriver.com> |
||
---|---|---|
examples | ||
playbookconfig | ||
.ansible-lint | ||
.gitignore | ||
.gitreview | ||
.yamllint | ||
.zuul.yaml | ||
CONTRIBUTORS.wrs | ||
debian_build_layer.cfg | ||
debian_iso_image.inc | ||
debian_pkg_dirs | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
test-requirements.txt | ||
tox.ini |
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.