47a3a4826f
As part of story 2010591 the hard-coded values for L4 ports in puppet were moved to sysinv.common.constants and exported there to "system.yaml". But the bootstrap runs prior to this file availability, hence the port definitions are not available, and barbican failed during the subcloud bootstrap. To avoid that we are exporting all L4 ports that were exported to system.yaml to the runtime.yaml file to be available during bootstrap. Test Plan: [PASS] AIO-DX standalone install/unlock/enable [PASS] AIO-DX system controller install/unlock/enable [PASS] AIO-SX subcloud install/unlock/enable Closes-Bug: 2025361 Depends-On: https://review.opendev.org/c/starlingx/config/+/887372 Change-Id: I8ed58954338181bc32806f7f448f6ec280027830 Signed-off-by: Andre Kantek <andrefernandozanella.kantek@windriver.com>
stx-ansible-playbooks
StarlingX Bootstrap and Deployment Playbooks
Execution environment
- Unix like OS (recent Linux based distributions, MacOS, Cygwin)
- Python 2.7
Additional Required Packages
The playbooks in this repo have been verified with the following versions of Ansible and StarlingX playbooks dependencies:
- sshpass 1.06
- python2-ptyprocess 0.5
- python2-pexpect 4.6
- python2-netaddr 0.7
ansible2.7.5
Supported StarlingX Releases
The playbooks in this repo are compatible with the following StarlingX releases:
- 20.01
Executing StarlingX Playbooks
Executing Bootstrap Playbook
Please refer to StarlingX Deployment Guides, section
Configuration controller-0 of the respective system
configuration for instructions on how to set up and execute the
bootstrap playbook from another host.