RETIRED, Extra Ansible roles to automate TripleO deployments
yatinkarel
fa93a6a3bc
featureset_override_file_output contain some additional vars like standalone_custom_env_files. To reproduce a job we want to have same set of override's given in a job so let's use job.featureset_override instead, if standalone_environment_files is part of featureset_override then standalone_custom_env_files will be calculated within standalone role. Closes-Bug: #1897155 Change-Id: I7dbd8f1e34cabd41504150c886cbe9ff166b50ea |
||
---|---|---|
ci-scripts | ||
config | ||
playbooks | ||
releasenotes | ||
roles | ||
zuul.d | ||
.ansible-lint | ||
.gitignore | ||
.gitreview | ||
.pre-commit-config.yaml | ||
.yamllint | ||
bindep.txt | ||
LICENSE | ||
molecule-requirements.txt | ||
other-requirements.txt | ||
README.rst | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini | ||
vars |
Team and repository tags
Extra roles for tripleo-quickstart
These Ansible role are extending the functionality of tripleo-quickstart to do end-to-end deployment and testing of TripleO.
The documentation of each role is located in the individual role folders, and general usage information is in the tripleo-quickstart documentation.