The first step for LAVA development is understanding its architecture. The major LAVA components are depicted below:
+-------------+
|web interface|
+-------------+
|
v
+--------+
+---->|database|
| +--------+
|
+-----------+------[worker]-------------+
| | |
| +----------------+ +----------+ |
| |scheduler daemon|---→ |dispatcher| |
| +----------------+ +----------+ |
| | |
+------------------------------+--------+
|
V
+-------------------+
| device under test |
+-------------------+
On single-server deployments, both the web interface and the worker components (scheduler daemon + dispatcher) run on a same server. You can also install one or more separated worked nodes, that will only run scheduler daemon + dispatcher.
LAVA is written in Python, so you will need to know (or be willing to learn) Python. Likewise, the web interface is a Django application so you will need to Django if you need to modify the web interface.
Also, you will need git.
LAVA online document is written with RST format. You can use the command below to generate html format files.:
$ cd lava-server/
$ make -C doc html
$ iceweasel doc/_build/html/index.html
(or whatever browser you prefer)
The best way to protect your investment on LAVA is to contribute your changes back. This way you don’t have to maintain the changes you need by yourself, and you don’t run the risk of LAVA changed in a way that is incompatible with your changes.
Upstream uses Debian, see Developing LAVA on Debian or Ubuntu for more information.
You are welcome to use the bug tracker of your chosen distribution. The maintainer for the packages in that distribution should Register with Linaro as a Community contributor with Linaro (or already be part of Linaro) to be able to forward bug reports and patches into the upstream LAVA systems.
If you, or anyone on your team, would like to register with Linaro directly, this will allow you to file an upstream bug, submit code for review by the LAVA team, etc. Register at the following url:
If you are considering large changes, it is best to register and also to subscribe to the Linaro Validation mailing list and talk to us on IRC:
irc.oftc.net
#linaro-lava
You can use GitHub to fork the LAVA packages and make pull requests.
It is worth sending an email to the Linaro Validation mailing list, so that someone can migrate the pull request to a review:
This is a short guide on how to send your patches to LAVA. The LAVA team uses the gerrit code review system to review changes.
If you do not already have a Linaro account, you will first need to Register with Linaro as a Community contributor.
So the first step will be logging in to gerrit and uploading you SSH public key there.
There are two main components to LAVA, lava-server and lava-dispatcher.
git clone http://git.linaro.org/git/lava/lava-server.git
cd lava-server
git clone http://git.linaro.org/git/lava/lava-dispatcher.git
cd lava-dispatcher
git review -s
We recommend never working off the master branch (unless you are a git expert and really know what you are doing). You should create a topic branch for each logically distinct change you work on.
Before you start, make sure your master branch is up to date:
git checkout master
git pull
Now create your topic branch off master:
git checkout -b my-change master
Extra dependencies are required to run the tests. On Debian based distributions, you can install lava-dev. (If you only need to run the lava-dispatcher unit tests, you can just install pep8 and python-testscenarios.)
To run the tests, use the ci-run script:
$ ./ci-run
Unit tests cannot replicate all tests required on LAVA code, some tests will need to be run with real devices under test. On Debian based distributions, see Developer package build. See Writing a LAVA test definition for information on writing LAVA test jobs to test particular device functionality.
Make sure that your changes do not cause any failures in the unit tests:
$ ./ci-run
Wherever possible, always add new unit tests for new code.
From each topic branch, just run:
git review
If you have multiple commits in that topic branch, git review will warn you. It’s OK to send multiple commits from the same branch, but note that 1) commits are review and approved individually and 2) later commits will depend on earlier commits, so if a later commit is approved and the one before it is not, the later commit will not be merged until the earlier one is approved.
When reviewers make comments on your change, you should amend the original commit to address the comments, and not submit a new change addressing the comments while leaving the original one untouched.
Locally, you can make a separate commit addressing the reviewer comments, it’s not a problem. But before you resubmit your branch for review, you have to rebase your changes against master to end up with a single, enhanced commit. For example:
$ git branch
master
* my-feature
$ git show-branch master my-feature
! [master] Last commit on master
! [my-feature] address revier comments
--
+ [my-feature] address reviewer comments
+ [my-feature^] New feature or bug fix
-- [master] Last commit on master
$ git rebase -i master
git rebase -i will open your $EDITOR and present you with something like this:
pick xxxxxxx New feature or bug fix
pick yyyyyyy address reviewer comments
You want the last commit to be combined with the first and keep the first commit message, so you change pick to fixup ending up with somehting like this:
pick xxxxxxx New feature or bug fix
fixup yyyyyyy address reviewer comments
If you also want to edit the commit message of the first commit to mention something else, change pick to reword and you will have the chance to do that. Just remember to keep the Change-Id unchanged.
NOTE: if you want to abort the rebase, just delete everything, save the file as empty and exit the $EDITOR.
Now save the file and exit your $EDITOR.
In the end, your original commit will be updated with the changes:
$ git show-branch master my-feature
! [master] Last commit on master
! [my-feature] New feature or bug fix
--
+ [my-feature] New feature or bug fix
-- [master] Last commit on master
Note that the “New feature or bug fix” commit is now not the same as before since it was modified, so it will have a new hash (zzzzzzz instead of the original xxxxxxx). But as long as the commit message still contains the same Change-Id, gerrit will know it is a new version of a previously submitted change.
After placing a few reviews, there will be a number of local branches. To keep the list of local branches under control, the local branches can be easily deleted after the merge. Note: git will warn if the branch has not already been merged when used with the lower case -d option. This is a useful check that you are deleting a merged branch and not an unmerged one, so work with git to help your workflow.
$ git checkout bugfix
$ git rebase master
$ git checkout master
$ git branch -d bugfix
If the final command fails, check the status of the review of the branch. If you are completely sure the branch should still be deleted or if the review of this branch was abandoned, use the -D option instead of -d and repeat the command.
If you haven’t got a clone handy on the instance to be used for the review, prepare a clone as usual.
Gerrit provides a number of ways to apply the changes to be reviewed, so set up a test branch as usual - always ensuring that the master branch of the clone is up to date before creating the review branch.
$ git checkout master
$ git pull
$ git checkout -b review-111
To pull in the changes in the review already marked for commit in your local branch, use the pull link in the patch set of the review you want to run.
Alternatively, to pull in the changes as plain patches, use the patch` link and pipe that to patch -p1. In this full example, the second patch set of review 159 is applied to the review-159 branch as a patch set.
$ git checkout master
$ git pull
$ git checkout -b review-159
$ git fetch https://review.linaro.org/lava/lava-server refs/changes/59/159/2 && git format-patch -1 --stdout FETCH_HEAD | patch -p1
$ git status
Handle the local branch as normal. If the reviewed change needs modification and a new patch set is added, revert the local change and apply the new patch set.
All developers are encouraged to write code with futuristic changes in mind, so that it is easy to do a technology upgrade, which includes watching for errors and warnings generated by dependency packages as well as upgrading and migrating to newer APIs as a normal part of development.
There is no pressure or expectation on delivering python 3.x code. LAVA is a long way from being able to use python 3.x support, particularly in lava-server, due to the lack of python 3.x migrations in dependencies. However it is good to take python 3.x support into account, when writing new code, so that it makes it easy during the move anytime in the future.
Developers can run unit tests against python 3.x for all LAVA components from time to time and keep a check on how we can support python 3.x without breaking compatibility with python 2.x
Pylint is a tool that checks for errors in Python code, tries to enforce a coding standard and looks for bad code smells. We encourage developers to run LAVA code through pylint and fix warnings or errors shown by pylint to maintain a good score. For more information about code smells, refer to Martin Fowler’s refactoring book. LAVA developers stick on to PEP 008 (aka Guido’s style guide) across all the LAVA component code.
To simplify the pylint output, some warnings are recommended to be disabled:
$ pylint -d line-too-long -d missing-docstring
NOTE: Docstrings should still be added wherever a docstring would be useful.
In order to check for PEP 008 compliance the following command is recommended:
$ pep8 --ignore E501
pep8 can be installed in debian based systems as follows:
$ apt-get install pep8
LAVA has set of unit tests which the developers can run on a regular basis for each change they make in order to check for regressions if any. Most of the LAVA components such as lava-server, lava-dispatcher, lava-tool, linaro-python-dashboard-bundle have unit tests.
Extra dependencies are required to run the tests. On Debian based distributions, you can install lava-dev. (If you only need to run the lava-dispatcher unit tests, you can just install pep8 and python-testscenarios.)
To run the tests, use the ci-run / ci-build scripts:
$ ./ci-run
to LAVA - Board addition howto? Requirements for a device in LAVA
What do I need to create a test image for LAVA? What do I need to create a master image for LAVA? * 8GB SD Card
TODO
Coming soon.