c60b55ec83
This commit enanbles Ansible linting and does some
minor refactoring to make existing Ansible roles
compatible with the new rules.
Several Ansible linting rules have been excluded to keep the number
of changes from being too onerous.
Also a new script in ci-scripts is used to check very config file
included in the Browbeat repo for validity using the template
Browbeat uses when it runs.
Here's a list of the new linting rules
* Ansible tasks must have names
* When you use shell you must use become not sudo
* Using become_user without using become is not allowed
* If a repo is pulled it must be a pinned version of commit, not latest
* Always_run is deprecated don't use it
* Variables without {{}} and not in when statements are deprecated don't use them
* No Trailing whitepaces
* YAML checking, catches big syntax errors but not less obvious ones
Change-Id: Ic531c91c408996d4e7d8899afe8b21d364998680
|
||
|---|---|---|
| .. | ||
| group_vars | ||
| roles | ||
| templates | ||
| browbeat-example-bug_report.log | ||
| README.rst | ||
| site.yml | ||
Browbeat Ansible Checks
The Browbeat Ansible checks playbook will scan a given deployment to check for known configuration issues.
Output from Checks
Once the Checks playbook completes there will be a report generated in the browbeat results directory.
bug_report.logThis will contain each of the hosts that were scanned, and their known issues. Some of the issues will have BZ's associated with them, use the BZ link to learn more about the bug, and how it can impact your deployment. There will be Checks that do not have a BZ associated, these are simply suggestions.