With the new dispatcher code getting closer to production, it's important to understand how LAVA works and how it will work so you can get the most out of your LAVA installation
This session (starting in 10 minutes) will be an introductory walk-through of how to develop in LAVA followed by a short Q&A session
LAVA & the Django Request/Response Cycle
LAVA is built with 2 primary systems, the scheduler and web interface, "lava-server" and the system that communicates with the hardware targets "lava-dispatcher"
(Reference Graphic: https://www.reddit.com/r/django/comments/2vjyrc/djangos_requestresponse_cycle_a_visual_guide/
How to add new code to the LAVA Dispatcher
Extending the dispatcher to allow LAVA to control a new device or execute a new use-case is a very common activity, it's also important to understand how the unit and functional tests are integrated
How to extend LAVA to control external hardware
It's just software right? We'll quickly discuss two methods for using LAVA to control external test equipment. 1. test-definition based control, 2. protocol integration.
Questions & Answers