4b8611200b
When bootstrapping a system, the sysinv.conf does not have the use_syslog option set in the sysinv.conf. Because of that, sysinv.log and sysinv-api.log files are not created until the host unlock, when the configuration file is overridden and the option is set. This commit adds the use_syslog=True option in the sysinv.conf template used to bootstrap the system. Test plan: 1. PASS: Bootstrap a DC system with three subclouds. 2. PASS: During the bootstrap process, verify that the sysinv.log file is created after sysinv.conf is generated. 3. PASS: During the bootstrap process, verify that the sysinv-api.log file is created after the "Saving config in sysinv database" step. Closes-Bug: 2068767 Change-Id: I7ce56aa56114fb3e5234913bfe8a081bc6851612 Signed-off-by: Raphael Lima <Raphael.Lima@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.