# Progress
* Investigated and designed a solution for supporting automatic network
bridging on the host for vm group jobs. Draft code written.
* Relesed lava-tool 0.11 (and 0.11.1)
* Wrote patches for 2 important bugs related to vm groups:
* lava multinode helpers missing from vmgroup jobs
https://bugs.launchpad.net/lava-dispatcher/+bug/1317504
* not possible to submit vmgroup job from lava-tool
https://bugs.launchpad.net/lava-tool/+bug/1317467
# Plan
* Having those bug fixes landede and deployed to production
* Tackle a couple of other high priority bug fixes that are pending
* Implement support for manual signaling for starting the VMs of a VM groups
job to support the use case of native building qemu as part of the host test
definition.
--
Antonio Terceiro
Software Engineer - Linaro
http://www.linaro.org
Hello,
We have just released lava-tool version 0.11. This version adds a new
--block option to the `lava-tool submit-job` command, that will make
lava-tool block until the job finished running on LAVA.
In the near future this feature will be expanded so you can watch the
job run from your terminal.
The sources are available on PyPi:
https://pypi.python.org/pypi/lava-tool
Binary packages for Ubuntu are available in the Linaro tools PPA:
https://launchpad.net/~linaro-maintainers/+archive/tools/
--
Antonio Terceiro
Software Engineer - Linaro
http://www.linaro.org
Today the LAVA team was discussing how we could make LAVA aware of
known-good images for each device type. The use case is: when learning
LAVA, engineers will often not know exactly which images to use, and
they usually don't care much as they want first to learn how to use LAVA
itself.
To solve this problem, we came up with the following proposal.
The LAVA admin should be able to configure the URL of a mini-database of
know good images for each of its device types. The proposed format is a
very simple YAML hash like this:
----------------8<----------------8<----------------8<-----------------
kvm:
action: deploy_linaro_image
parameters:
image: "http://url.to/kvm.img"
kvm-arm:
action: deploy_linaro_kernel
parameters:
kernel: "http://url.to/zImage"
rootfs: "http://url.to/rootfs"
dtb: "http://url.to/dtb"
arndale:
action: deploy_linaro_image
parameters:
image: "http://url.to/arndale.img"
----------------8<----------------8<----------------8<-----------------
LAVA will just poll this database from time to time, but won't care how
it is kept up to date. LAVA admins can make the generation of this
database part of their automation.
In Linaro, we should probably generate this data from
releases.linaro.org. Fathi, can we generate this as part of the release
process? If not, can we at least have a MANIFEST of the full contents of
each release, so that we can generate that database on our side?
Assuming the directory strutcure of releases is stable, the output of
`find .` inside the release directory should be good enough.
--
Antonio Terceiro
Software Engineer - Linaro
http://www.linaro.org
lava-server | 2014.04.06.13.52-1 | sid | armhf, arm64, amd64, i386, source
lava-server | 2014.04.06.13.52-1 | jessie | armhf, arm64, amd64, i386, source
lava-server | 2014.04.08.12.04-1 | unicorn | amd64, source
lava-server | 2014.04.08.12.04-1 | trusty | amd64, source
lava-dispatcher | 2014.04.06.13-1 | sid | armhf, arm64, amd64, i386, source
lava-dispatcher | 2014.04.06.13-1 | jessie | armhf, arm64, amd64, i386, source
lava-dispatcher | 2014.04.08.10-1ubuntu1 | unicorn | amd64, source
lava-dispatcher | 2014.04.08.10-1ubuntu1 | trusty | amd64, source
There had been problems with the Ubuntu build of lava-server but those
are now fixed and the Debian build uses the same Apache configuration. The
helpers in the lava-dev package allow for local builds on Ubuntu and a
few selectively copied packages mean that lava-server is now
installable on Debian testing (Jessie) as well as unstable (sid).
NOTE: The Ubuntu builds may not always be the absolute latest code
until the release process is formalised but when Unicorn is updated the
same source will be copied into Trusty. The builds are also only for
64bit x86 (amd64) currently as these are local developer builds.
All repositories continue to use the emdebian-archive-keyring package
for SecureApt.
apt sources for Debian
======================
deb http://people.linaro.org/~neil.williams/lava sid main
deb http://people.linaro.org/~neil.williams/lava jessie main
Ubuntu
======
*Ensure the universe component is enabled for the base installation*
deb http://people.linaro.org/~neil.williams/ubuntu unicorn main
deb http://people.linaro.org/~neil.williams/ubuntu trusty main
NOTE-2: It is strongly recommended *NOT* to migrate existing LAVA
instances on Precise 12.04LTS to Trusty 14.04LTS at this time. There is
more to do to ensure that the job log files are moved efficiently.
lava-deployment-tool is *NOT* capable of installing a LAVA instance on
Trusty and l-d-t is *not* capable of migrating a LAVA instance to
django1.6 which is used in the packaging.
The Ubuntu packages have only been lightly tested but the server does
run. The trusty repository simply includes some dependency packages
which have already been included into Utopic Unicorn through the
auto-merge with Debian. (If someone wants to do backports of those to
Trusty, feel free.)
There will be no packaging support for Ubuntu releases older than
Trusty 14.04LTS or Debian suites older than Jessie due to the need for
django1.6.
Other distributions
===================
Patches welcome .... if anyone is already working on Fedora packaging
or wants to work on Fedora support, just do so & let us know if there
are problems.
There is one remaining dependency which is due to be merged into
lava-server - linaro-django-xmlrpc. Other changes in the packaging
branch are mainly cherry-picked updates from master for lava-server and
lava-dispatcher.
--
Neil Williams
=============
http://www.linux.codehelp.co.uk/
# Progress
* landed vm groups suppport, already functional
* updated vm groups documentation on image requirements
# Plan
* Add bridge setup support to vm groups implementation so that VMs can join the
same LAN as the host.
--
Antonio Terceiro
Software Engineer - Linaro
http://www.linaro.org
lava-server | 2014.04.06.13.52-1 | sid | armhf, arm64,
amd64, i386, source
lava-dispatcher | 2014.04.06.13-1 | sid | armhf, arm64,
amd64, i386, source
This update includes the VM groups support and folds the
linaro-dashboard-bundle code into lava-dispatcher (documentation into
lava-server).
The update will replace any existing packages of
linaro-dashboard-bundle and linaro-dashboard-bundle-doc and restart
both the lava-scheduler daemon and apache2 (if the lava apache config
file is found in /etc/apache2/sites-enabled/).
See
http://lists.linaro.org/pipermail/linaro-validation/2014-April/002336.html
for full information on the packaging of LAVA for Debian unstable.
The following dependencies of LAVA are now available in Debian
unstable, Debian testing (Jessie) and Ubuntu Utopic Unicorn:
django-testproject
json-schema-validator
In addition, django-testscenarios is now available in Debian unstable
and Ubuntu Utopic Unicorn and will migrate into Debian Jessie in 5 days.
Upgrading or installing LAVA using the packages will preferentially use
these packages and all updates to these packages will be available in
the same way.
--
Neil Williams
=============
http://www.linux.codehelp.co.uk/
