c29636eab5
os.path.join can accept arbitrary number of path likes, nesting the calls is therefore unnecessary. Signed-off-by: Jiri Podivin <jpodivin@redhat.com> Change-Id: I19010de832b2dd0b7f1b4940c9f770929d041053 |
||
---|---|---|
doc | ||
playbooks | ||
validations_libs | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.pre-commit-config.yaml | ||
.stestr.conf | ||
.zuul.yaml | ||
Dockerfile | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
Vagrantfile.centos | ||
Vagrantfile.ubuntu | ||
bindep.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
validations-libs
A collection of python libraries for the Validation Framework
Development Environment Setup
Vagrantfiles for CentOS and Ubuntu have been provided for
convenience; simply copy one into your desired location and rename to
Vagrantfile
, then run:
vagrant up
Once complete you will have a clean development environment ready to go for working with Validation Framework.
Docker Quickstart
A Dockerfile is provided at the root of the Validations Library project in order to quickly set and hack the Validation Framework. Build the container from the Dockerfile by running:
docker build -t "vf:dockerfile" .
Once the build is finished you can check the image id:
docker images
Then you can run the container and start to run some builtin Validations:
docker run -ti <image_id> /bin/bash
Then run validations:
validation.py run --validation check-ftype,512e