# Validation Framework Design Architecture

## Goals:

The goals of redesigning the VF architecture is:

* the simplification of the Core of the VF, meaning that the VF is only a wrapper logger on top of Ansible and should be fairly easy to use and to jump in.
* Less dependencies
* modularity: The VF should be able to be pluged with external Validations repository, even lambda Ansible playbooks, run it, log the results and output and report it.
* the logging and reporting. The VF should affort a real gain in terms of Logging and Reporting Ansible output.
* Interoperability: The VF should be able to run from everywhere on every type of machine:
* From $somewhere I want to execute this set of validations on my cloud, servers ...
* being non-openstack oriented: Validations can serve as many fields as possible, other than openstack and tripleo.

## Constraints:

* Keep current usability and TripleO focus
* The CLI for Openstack and TripleO should be kept
* Backward compat

## Steps:

1. Create or improve a CLI in validations-libs
* with argprase
* get ride of osc_lib
* decrease all the dependencies with Openstack
2. get ride of validation-common and merged into validations-libs (eventually rename validation-libs)
* V-libs will contains a
* /callbacks
* /roles
* /playbooks
* /libraries
3. Change the governance to non-tripleo or even non-openstack