Improve the validation result format

[Tomas Sedovic]

When a validation is run, the output is whatever Ansible produces. Which can be noisy sometimes and might hide the error report in a ton of irrelevant text.

We should investigate changing the Ansible output to highlight the most relevant information. In addition, we could make the output more structured so the UI can apply some formatting.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/379348

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/375477
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=e10338ce4adc99efe9e5764d7a4b85c5a5c6d883
Submitter: Jenkins
Branch: master

commit e10338ce4adc99efe9e5764d7a4b85c5a5c6d883
Author: Tomas Sedovic <email address hidden>
Date: Tue Sep 20 15:11:31 2016 +0200

    Add a validation-specific Ansible output callback

    The validations have a few specifics in how they're used and what
    information is important. So this formats the validation output in a way
    that should highlight the failures themselves and make it more obvious
    what went wrong and what to do when a validation fails.

    Change-Id: I9730f2dd04868c5de46ae90bd545865d17aec530
    Closes-Bug: #1625526

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/379348
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=c25c30bb0be55c6aa180e0ba1d0858e0d0b890fa
Submitter: Jenkins
Branch: master

commit c25c30bb0be55c6aa180e0ba1d0858e0d0b890fa
Author: Tomas Sedovic <email address hidden>
Date: Thu Sep 29 12:21:40 2016 +0200

    Configure run-validation to use the custom output

    The validations now have a custom Ansible formatter that shows a better
    report on the validation run, what failed and why, etc. This makes it
    available to our Mistral workflows.

    Change-Id: Iebe26e3e2922dafc7f93837c4315cebf14563f6d
    Depends-On: I9730f2dd04868c5de46ae90bd545865d17aec530
    Closes-Bug: #1625526

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/392859

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/392859
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=caa1c40b0631d4920b144ffc0eb46a4e7bb55ed7
Submitter: Jenkins
Branch: stable/newton

commit caa1c40b0631d4920b144ffc0eb46a4e7bb55ed7
Author: Tomas Sedovic <email address hidden>
Date: Tue Sep 20 15:11:31 2016 +0200

    Add a validation-specific Ansible output callback

    The validations have a few specifics in how they're used and what
    information is important. So this formats the validation output in a way
    that should highlight the failures themselves and make it more obvious
    what went wrong and what to do when a validation fails.

    Change-Id: I9730f2dd04868c5de46ae90bd545865d17aec530
    Closes-Bug: #1625526
    (cherry picked from commit e10338ce4adc99efe9e5764d7a4b85c5a5c6d883)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/393467

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/393467
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=c58bcf9f236b757f25331a8c16298c0db40ea815
Submitter: Jenkins
Branch: stable/newton

commit c58bcf9f236b757f25331a8c16298c0db40ea815
Author: Tomas Sedovic <email address hidden>
Date: Thu Sep 29 12:21:40 2016 +0200

    Configure run-validation to use the custom output

    The validations now have a custom Ansible formatter that shows a better
    report on the validation run, what failed and why, etc. This makes it
    available to our Mistral workflows.

    Change-Id: Iebe26e3e2922dafc7f93837c4315cebf14563f6d
    Depends-On: I9730f2dd04868c5de46ae90bd545865d17aec530
    Closes-Bug: #1625526
    (cherry picked from commit c25c30bb0be55c6aa180e0ba1d0858e0d0b890fa)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-common 5.4.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-common 5.5.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-validations 5.2.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-common 5.4.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-validations 5.1.1 release.