x/browbeat
Code Issues Proposed changes
ec23a6009e
browbeat/ansible/check
History
jkilpatr b768d626df Correct bug report save location 
Moves bug report save location to the playbook directory
on the machine running ansible, I feel that this is an odd
place to put anything but it seems to be intended behavior.

This commit changes where the bug report is saved and where
the CI script checks for the output file, until a consistent
version of this is checked in CI will fail often.

Change-Id: I94d221d718fb13779bf056ae83376851f82a355b
2016-09-14 15:03:48 -04:00
..
group_vars Correct bug report save location 2016-09-14 15:03:48 -04:00
roles Check if Gnocchi api processes is > 1. 2016-09-07 07:52:56 -04:00
templates Implement Suggestions 2016-08-31 15:14:25 -04:00
browbeat-example-bug_report.log Adding example of Overcloud Check 2016-01-05 16:13:43 -05:00
README.rst convert remaining markdown to rst. 2016-06-22 09:57:01 +01:00
site.yml Correct bug report save location 2016-09-14 15:03:48 -04:00

README.rst

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 checks directory.

bug_report.log

This 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.