Make validation inputs configurable through Mistral

[Tomas Sedovic]

A lot of the validations have some input that can be configured via Ansible environments. For example the undercloud-ram validation lets the expected RAM amount to be changed by passing `-e min_undercloud_ram_gb=...` to ansible-playbook.

This mechanism is not exposed in the Mistral worflow but it should be.

It would let the UI control certain aspects of the validations and when we run them in the CI, we could adapt these values to the ones expected in the CI (e.g. lower expected RAM and disk space values).

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.openstack.org/383763
Reason: Abandoning this patch per the TripleO Patch Abandonment guidelines (https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html). If you wish to have this restored and cannot do so yourself, please reach out via #tripleo on freenode or the OpenStack Dev mailing list.

[Juan Antonio Osorio Robles (juan-osorio-robles)]

We're going to re-do the whole validation framework. So this should be part of the spec and not a bug.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Gael Chamoulaud (<email address hidden>) on branch: master
Review: https://review.openstack.org/383763

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/644603
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=5762772fdf1d3ec70407c31f90aad41589e5efe2
Submitter: Zuul
Branch: master

commit 5762772fdf1d3ec70407c31f90aad41589e5efe2
Author: Gael Chamoulaud <email address hidden>
Date: Tue Mar 19 16:45:05 2019 +0100

    Make validation inputs configurable via Mistral

    The validations have certain values (e.g. the amount of RAM necessary
    for the undercloud node) configurable, but these were not exposed
    through Mistral.

    This adds a new `--inputs` parameter to the `run-validation` script
    which takes a path to a YAML or JSON file with the additional
    inputs (i.e. Ansible extra-args) defined.

    And the `run_validation` action now optionally takes an `inputs`
    dictionary which gets passed to `run-validation`.

    Closes-Bug: #1625547
    Implements: blueprint validation-framework
    Signed-off-by: Gael Chamoulaud <email address hidden>

    Change-Id: I8944cf7133d47869d26974fd123cd93c98425f17
    Co-authored: Tomas Sedovic <email address hidden>

[OpenStack Infra (hudson-openstack)]

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