The run_bluval.sh script creates the environment needed by Blueprint Validation Framework and it calls blucon tool to run the tests.
The script can be found in jjb/shell/
usage: ./jjb/shell/run_bluval.sh -n <blueprint_name>
-r <results_dir> results dir
-b <blueprint_yaml> blueprint definition
-k <k8s_config_dir> k8s configuration folder
-j <k8s_master> k8s master
-u <ssh_user> ssh user
-s <ssh_key> path to ssh key
-l <layer> blueprint layer
-o run optional tests
-v <version> version
The script can be configured by setting shell variables before calling the script or using parameters. Below is an example of shell configuration before calling the script.
export K8S_MASTER_IP=172.16.10.36
export K8S_SSH_USER=ubuntu
export K8S_SSH_KEY=/var/lib/opnfv/mcp.rsa
export BLUEPRINT=iec
export LAYER=k8s
export VERSION=master
export OPTIONAL=yes
The script can be called using parameters detailed below:
-n <blueprint_name> The blueprint name is mandatory. The tests are run using the file validation/bluval/bluval-$blueprint_name.yaml
-r <results_dir> The location to where to store the results. If this parameter is not provided then path $(pwd)/results is used
-b <blueprint_yaml> The yaml file used to run the tests. This file is copied in validation/bluval/ folder before running the blucon tool
-k <k8s_config_dir> The location where the script copies the kube config files needed for access to the cluster. If not provided the path $(pwd)/kube is used
-j <k8s_master> The IP address of k8s master node. If this parameter is not given the script will use $K8S_MASTER_IP
-u <ssh_user> User to connect to k8s master node. If this is not set then $K8S_SSH_USER will be used
-s <ssh_key> Path to key used to connect to k8s master node. If login is done using password then the $K8S_SSH_PASSWORD
-l <layer> The blueprint layer to be used. If not set, $LAYER will be used.
-o : If used, the blucon will run the optional tests also.If not set, than $OPTIONAL will be used.
-v <version> Version to be used. If not set than $VERSION will be used.
1. Steps needed to add tests in CI for a new lab for IEC tests:
- Modify jjb/validation/lab.yaml and add a new lab in validation_lab section:
validation_lab:
- enea
- new_lab
2. Add the project in jjb/iec/iec.yaml and take as reference validation-enea-daily-{stream}.
'validation-new_lab-daily-{stream}.
3. Modify the project parameters to match your lab configuration
2. Steps needed to add tests for a new blueprint in CI :
- If your tests run in a different lab make sure you added the new lab
- Modify the yaml file for your blueprint and add a new project in the
builders:
- trigger-builds:
section after the deploy project was executed to make sure that test run after the deplo
3.Set the BLUEPRINT parameter to the name of your blueprint
4.Update the other parameters to match your configuration