StarlingX Ansible Playbooks
b1e846a35f
This change updated SX to DX migration playbook to support IPsec when migrated to DX. The migration playbook is supposed to run on System Controller to migrate subclouds. Test Plan: PASS: In a DC system, define an overrides file, then run the migration playbook in System Controller to migrate a SX subcloud, verify the migration is successful, and verify IPsec is configured and enabled in the migrated DX subcloud. Story: 2010940 Task: 50791 Change-Id: I76666b8c29cbd3f84bfa8f6ab4f03e7c26bd0fe4 Signed-off-by: Andy Ning <andy.ning@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.