
Add the label "app.starlingx.io/component=platform" to pods to ensure kubernetes run it on the platform cores. Additionally, the review [1] introduced a problem when changing the chdir path in the trident install task. This resulted in the installer being unable to locate the custom templates. [1]: https://review.opendev.org/c/starlingx/ansible-playbooks/+/887424/13/playbookconfig/src/playbooks/roles/k8s-storage-backends/netapp/tasks/main.yml#86 Test Plan: PASS: Install trident PASS: Check if pods have the label 'app.starlingx.io/component' with the value 'platform' Story: 2010612 Task: 50258 Change-Id: I051c328edddf5b997c192e96f9be4ed34743b554 Signed-off-by: Erickson Silva de Oliveira <Erickson.SilvadeOliveira@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.
References
Description
Languages
Jinja
70.4%
Python
21.3%
Shell
8.2%