README

= Templates for Apertis tests =

The templates contains the set of templates we use for lava testing for Apertis
and a set of default profiles. These are intended to be used with the lqa tool,
available from: http://cgit.collabora.com/git/singularity/tools/lqa.git/

For lqa usage see the readme in the lqa source tree, minimal examples
for Apertis below:

To submit e.g. a minimal boot test to minnowboard (daily 15.12) targets use:

    lqa submit -g templates/profiles.yaml \
      -p apertis-15.12-daily-minnowboard-max-target \
      -t image_date:150624-001801 \
      -t image_version:14.00.25 \
      templates/minimal-tpl.json

The image_date variable specifies the image data of the image to use, see
https://images.apertis.org/daily/15.12/ for the list of
available images.

The image_version variable is also part of the image's filename.
The first part is incremented every quarter, the second part is 00
for daily builds or 01 for quarterly releases and the third is the
ISO week number (date +%W).

Note that lqa can replace any variable (either json items or {{variable}}) this
can for example be used to change the git-repo value to non-standard repository
to test tests before merging them for example:

    lqa submit -g templates/profiles.yaml \
      -p apertis-15.12-daily-minnowboard-max-target \
      -t image_date:150624-001801 \
      -t image_version:14.00.25 \
      -t git-repo:https://...@git.apertis.org/git/users/me/apertis-tests.git \
      -t revision:test \
      templates/minimal-tpl.json


For developer testing, some machines have a predeployed image available, saving
the time to re-deploy images on every test boot. An example minimal template
for that is available in templates/minimal-predeployed-1503-target-tpl.json (at
the time of this writing only setup for minnowboard max). Note that this images
are fully ephemeral, all changes to the filesystem will disappear on each boot