# Progress
* Improved support for ARM KVM devices on LAVA
* Added support for qcow2 images by converting them to raw images after
downloading
* Initial VM groups patchset submitted for review
# Plan
* improvements on the VM groups patchset
* VM groups testing
--
Antonio Terceiro
Software Engineer - Linaro
http://www.linaro.org
# Progress #
* LAVA test CARDs
* Trying to build whole Android and got some problem. Figuring out the
problem.
* LAVA packaging environment setup
# Plan #
* [CARD-489]
* [BUG-1296880]
Hi Ryan,
I was trying to rerun some tests at my end via LAVA on armv8 FVPs using 14.04 hwpack.
What I see is that LAVA fails prematurely stating that
Traceback (most recent call last):
File "/srv/lava/.cache/git-cache/exports/lava-dispatcher/2014.03-17-g9381215/lava_dispatcher/actions/boot_control.py", line 105, in run
client.boot_linaro_image()
File "/srv/lava/.cache/git-cache/exports/lava-dispatcher/2014.03-17-g9381215/lava_dispatcher/client/base.py", line 508, in boot_linaro_image
self._boot_linaro_image()
File "/srv/lava/.cache/git-cache/exports/lava-dispatcher/2014.03-17-g9381215/lava_dispatcher/client/base.py", line 481, in _boot_linaro_image
self.proc = self.target_device.power_on()
File "/srv/lava/.cache/git-cache/exports/lava-dispatcher/2014.03-17-g9381215/lava_dispatcher/device/fastmodel.py", line 325, in power_on
self._check_needed_files()
File "/srv/lava/.cache/git-cache/exports/lava-dispatcher/2014.03-17-g9381215/lava_dispatcher/device/fastmodel.py", line 188, in _check_needed_files
self.config.simulator_bl1)
RuntimeError: No SECURE FLASHLOADER found, u'bl1.bin'
Looking at the 14.04 hwpack I see that now there are 2 sets of bl* images there one for FVPs and another for Juno.
LAVA default config has
simulator_bl1 = bl1.bin
simulator_bl2 = [bB][lL]2.*.bin
simulator_bl3 = [bB][lL]31.*.bin
simulator_uefi = uefi_fvp-base.bin
fastmodel.py
# SECURE FLASHLOADERs are needed only for base and cortex models
if self._bl1 is None and self.config.simulator_bl1:
raise RuntimeError('No SECURE FLASHLOADER found, %r' %
self.config.simulator_bl1)
which I guess gets 'checked' by lava whether the needed files present and results in a runtime failure.
With the latest hardware packs, can you please confirm how does the bl images get unpacked?
Are they in some new folder structure because of platform variants are present?
Please advice.
For the moment I could not get LAVA to work with the latest hardware pack contents due to this issue.
Thanks
Basil Eljuse...
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
# Progress #
* Cards
* CARD-1257 (https://cards.linaro.org/browse/CARD-<https://cards.linaro.org/browse/CARD-1257>
1257)
* LAVA-1281
* good progress on dialog with notification and bundle stream selection
# Plan #
* CARD-1257
* LAVA-1281
* Vacation
# Issues #
* No issues
* Vacation from April 29 through May 9
--
--
Georgy Redkozubov
# Progress #
* LAVA-765 - Implement fastboot devices as drivers
* fastboot
* nexus10
* k3v2
* capri
* ifc6410
* LAVA-765 - Use SIGKILL to deal with adb/fastboot processes that timeout
* Refactor Fastboot Image Delivery
* Only require boot partition
* Extendable partition list
* Support deploy_linaro_kernel on ifc6410
* Generic Fastboot Support
* Add target_type to schema
* Allow other distributions to work properly on fastboot devices
* Dispatcher consolidation
* python web server -> _python_file_system in Target class
* soft_reboot and hard_reboot in Target class
* Toolchain Benchmark Job working on ARMv7
* Code reviews
* Presented at Northwest Linux Fest
# Plan #
* VM-Groups
* Deliver new fast boot support
* Production testing
--
Tyler Baker
Technical Architect, LAVA
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
For those using the packages already, this is an update which brings
the packaging back into line with current master (i.e. development
deployments, ahead of current production deployments / release branch).
https://wiki.linaro.org/Platform/LAVA/LAVA_packaging
lava-server | 2014.03.25.12.25-1 | sid | armhf, arm64, amd64, i386,
source
lava-dispatcher | 2014.03.25.10-1 | sid | armhf, arm64, amd64,
i386, source
LAVA is migrating to packaged deployments instead of using
lava-deployment-tool and the work is progressing as a pair of shared
branches on git.linaro.org which then build Debian packages hosted on
people.linaro.org.
LAVA has been operational on ARMv7 platforms like the arndale for a
little while already, although SATA or eMMC is recommended rather
than SD. A full LAVA install should be expected to need 20G for short
term usage, rising according to the number of devices and the number of
tests / log files. Tyler has been using this ARM support to regularly
update www.armv7.com with the packages, so that users can view the
changes without needing to install.
The packages are built for Debian unstable and include a migration to
django1.6 from the django1.4 used in current deployments. Also, the
frontend is being migrated to bootstrap.css for improved usage on
mobile devices and a simpler design overall. Other deprecated code has
been dropped as a result of the migration to django1.6.
The packages are not a direct upgrade for existing instances at this
time, not least because the base distribution needs to be Debian
unstable currently.
Dependencies like json-schema-validator, django-testproject and others
are being added to Debian (and will migrate into Ubuntu Utopic Unicorn
14.10 when the Ubuntu merge process restarts after the Trusty Tahr
release). Some testing has been done using the Debian packages on
Ubuntu Trusty Tahr 14.04LTS but the final packages will need backports
of a range of dependencies to Trusty if users want to remain on a
Ubuntu LTS base. The next Debian stable release - Jessie - will have
all the necessary support for LAVA and Debian Jessie is expected to be
the new base distribution for production LAVA deployments, rolling on
to the next Debian testing at some point after the Jessie release.
There are still issues to fix in the packaged branches, principally
completion of the bootstrap.css port and javascript updates. Updates to
lava-server and lava-dispatcher master branches are being cherry-picked
into the packaging branch alongside these fixes.
The packages support configuring lava-server as a remote worker but
note that this does, as with current lava-deployment-tool instances,
involve having all of LAVA installed on remote workers. This is an
upstream issue within LAVA and there are plans to fix this and let
remote workers only need lava-dispatcher installed, without the rest of
django or postgresql.
The packages have been operating properly and running limited LAVA tests
on developer boxes within the LAVA team for some months but are only now
getting wider testing. If you are interested in the new packaging
approach, feel free to install a new instance using Debian unstable.
To install the packages, add the apt source and emdebian-archive-keyring
package as specified in the wiki. It is recommended to always install
postgresql before starting the install of lava-server. If you already
have the Linaro Tools PPA in your apt sources, you may want to install
the top level 'lava' package to get all of the environment. (Note: if
you don't have the 'devscripts' package installed already, install just
'devscripts' with the --no-install-recommends option first.) The main
package to install is lava-server which will also bring in
lava-dispatcher and lava-tool. If using a virtual machine, remember to
setup bridging or install openvswitch-switch (and modprobe the
openvswitch module) outside the VM to be able to interact with LAVA
from outside the VM.
If you are interested in running LAVA on other distributions, like
Fedora, then please use the packaging branches of lava-dispatcher and
lava-server and note the dependency requirements outlined on the wiki
page:
https://wiki.linaro.org/Platform/LAVA/LAVA_packaging
The Debian packaging for LAVA is maintained at www.github.com/Linaro
The packaging branch is still in development and package dependencies
are likely to change, as described on the wiki. An official download of
the tarballs for packaging will be made available once the packages are
ready for production deployments and the migration of existing
instances has had more testing.
Packages are updated manually at the moment (due to the need for cherry
picking updates) but tools are included to rebuild the packages from
the packaging branch.
--
Neil Williams
=============
http://www.linux.codehelp.co.uk/
# Progress #
* Production rollout for critical fix on Tuesday
* Good progress on integration and testing of VM group patches
* Fix for performance issue on the LAVA scheduler daemon
https://review.linaro.org/1687
# Plan #
* Land VM groups support
--
Antonio Terceiro
Software Engineer - Linaro
http://www.linaro.org
