Download to read offline
Uploaded byLinaro
LAS16-503: LAVA V2 migration
LAS16-503: LAVA V2 migration Speakers: Neil Williams Date: September 30, 2016 ★ Session Description ★ Remaining tasks in the migration and next steps. ★ Resources ★ Etherpad: pad.linaro.org/p/las16-503 Presentations & Videos: http://connect.linaro.org/resource/las16/las16-503/ ★ Event Details ★ Linaro Connect Las Vegas 2016 – #LAS16 September 26-30, 2016 http://www.linaro.org http://connect.linaro.org
LAS16-503: LAVA V2 migration
- 1. Next steps inthe V2 migration Neil Williams
- 2. ENGINEERS AND DEVICES WORKING TOGETHER Recently addedsupport ● LXC & HiKey for AOSP testing in V2 ○ Other fastboot devices will be added ● Juno support ○ UBoot ○ UEFI ○ AOSP using LXC ○ Modifiable firmware on Versatile Express platforms ● LuvOS & bare metal testing. ● Overdrive ● Publishing API ○ https://archive.validation.linaro.org/
- 3. ENGINEERS AND DEVICES WORKING TOGETHER Existing support ●In use: ○ arndale, b2120stxh410, beaglebone-black, cubietruck, D02, D03, juno-uboot, lxc, mustang, nexus9, overdrive, panda, panda-es, qemu, x86 ■ QEMU support for multiple architectures ■ Replaces kvm device type ● In development ○ hi6220-hikey ○ juno ○ fast models ○ Versatile Express
- 4. ENGINEERS AND DEVICES WORKING TOGETHER Checking usecases for: ● D01 ● nexus10 ● hi3716cv200 ● highbank ● midway ● (fastmodels) ● tshark ● vayu
- 5. ENGINEERS AND DEVICES WORKING TOGETHER Migration -preparation ● Continue adding new deployment / device support ○ ifc6410, apq8016-sbc (dragonboard410c) ○ IPMI support ● Add worked examples and documentation ● Make all devices on all instances usable with V2 ● V2 healthchecks for all devices on all instances ● Make some devices on production exclusive to V2 ● Retain V1 data until all teams have sufficient V2 results ○ 3 months? ● Announcements made on the lava-announce mailing list ○ All users of LAVA should subscribe.
- 6. ENGINEERS AND DEVICES WORKING TOGETHER Migration -2017 ● Announce date when V1 submissions will be disabled. ○ When V2 device support covers all teams and instances. ● Release with V1 submissions disabled ○ Disable V1 scheduler ■ Any remaining V1 jobs in the queue would be invalid. ■ Reject submission of any V1 job. ■ Remove Resubmit button from V1 ○ Drop V1 code from lava-dispatcher codebase. ● Announce date for starting removal of V1 data ○ When all teams have 3(?) months of V2 results. ● Release with database migrations to delete: ○ Bundle, BundleStream, Filter, Image Reports, Image Reports 2.0 ● Release without any V1 code.
- 7. Questions #LAS16 For further information:www.linaro.org LAS16 keynotes and videos on: connect.linaro.org