This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
agl-testframework:setup [2016/10/12 13:49] jsmoeller |
agl-testframework:setup [2019/11/26 16:07] (current) jsmoeller |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | + | FIXME | |
- | ===== Setup ===== | + | |
- | //The instructions are WIP// | + | |
- | + | ||
- | * First setup AGL-JTA (fuego) and Lava (see respective docs atm, exactsteps follow here soon) | + | |
- | * We use a custom deploy task (CIAT.lava_deploy instead of CIAT.build_deploy) to commission the board through lava. Once the board is up, we follow the predefined workflow. | + | |
- | + | ||
- | * Caveats: | + | |
- | * AGL-JTA/Fuego assumes access through ssh to the board, right now we use a VPN between JTA and the Lava instance. This should be replaced by a transparent remote API (to support distributed aspect). Support exists but needs to be enhanced (LAVA 'hack' session). | + | |
- | + | ||
- | ===== Adaptions / Scripts ===== | + | |
- | * You need to setup /var/lib/jenkins/lava.yaml with the server and credentials. | + | |
- | * LAVA needs the nbd-root patches (not yet upstream, find the modifications here: not polished, yet ) | + | |
- | * Dispatcher - https://paste.debian.net/795073/ | + | |
- | * Scheduler - https://paste.debian.net/795075/ | + | |
- | * http://bit.ly/lavasetup | + | |