CIP Testing projectBoard At Desk (B@D)

Agustin Benito Bethencourt, Codethink

Robert Marshall, Codethink

AGL - CIAT meeting

29th August 2017

Civil Infrastructure Platform (CIP)

2

Provide a super long-term maintained

industrial-grade embedded Linux platform.

Platinum Members

Silver Members

Current members

Who are Codethink?

● Provide software engineering & consultancy services.

● Expert in Linux and Open Source software.

● Focus on embedded and automotive industry.

● UK Headquarters, serving clients in EU, US and Asia.

● Independent and unbiased.

● Membership: AGL (2015), OIN (2010), CIP (founder

member), GENIVI (2012)...

Why Codethink?Open Source company.

+

Embedded experience.

+

Passionate about creating, building &

delivering complex Linux systems.

The speakers: @toscalix and @rajm

● Agustín Benito Bethencourt: Principal Consultant at

Codethink Ltd

● Robert Marshall: software engineer at Codethink Ltd

● Previous work in the open: GENIVI GDP maintenance.

● Currently involved in CIP testing project

Talking points

1. Testing service architecture.

2. Proposed testing service architecture for CIP.

3. B@D: why, description and status.

Testing service architectures

Testing service architectures

● In corporate environments.

● In open environments:

○ Centralised service.

○ Semi-decentralised service.

○ De-centralised service

Proposed testing service architecture

for CIP

Transparent & de-centralised

service architecture.

What does decentralised reallymeans in CIP context?Sharing results is far from enough. CIP needs to ensure transparently that any

engineer is:

1. ...using the same tests...

2. ...to test the same CIP system...

3. ...on the same boards...

4. ...with the same tool set...

5. ...under the same environment...

6. ...producing the same reports...

7. ...comparable through canonical logs.

Why a decentralised testing servicefor CIP?● Cost.

● Manpower availability.

● Priorities within CIP.

● Adaptability to CIP nature.

● Dependencies.

● Experience from analysing other projects: kernelci.org ,

LTSI, AGL, openSUSE, openStack.

Board at Desk

B@D

Board @ Desk is KernelCI + LAVAv2 in a

single VM deployable in your development

machine to automatically run

builds/tests in a board directly

connected to it.

Board @ Desk

The tools: KernelCI + LAVAv2

● Manage board farms, load systems on boards, execute

programs/scripts and collect output.

● Builds kernels from any given repository.

● Dashboard for build/boot results visualization.

● Highly configurable reports.

● Run simple tests on distributed board farms through a

centrally managed system at large scale.

Why B@D

● KernelCI + LAVAv2 designed for systems testing.

● kernelci.org hosted by a mature organization, with well

defined governance and policies: Linaro.

● kernelci.org supported by the kernel community.

● Kernelci.org in production since early 2015. LAVA older.

● Company ecosystem around it.

Why B@D● KernelCI + LAVA designed primarily as a service.

● High entry threshold. Some configurations and deployment

can be improved.

● Main use case is kernel development, not system

maintenance.

● CIP focused in a very limited number of trees and boards.

● B@D adaptable to different/future service architectures if

required.

As a result, by using B@D...

… a developer with a board will:● Deploy a testing environment locally.

● Configure the testing environment for their use case.

● Test locally a pre-built system.

● Visualise / analyse the results locally, comparing them with expected results.

● Report those results in the open if desired.

… in minutes, clean and easy.

B@D today

● Latest stable version: 0.9.1.○ Downloadable provisioned as VM image.

● Latest code: self provisioning through Vagrant.

● Run healthchecks on QEMU.

● Daily healthchecks on beaglebone black sent to the

cip-testing-results mailing list.

B@D latest features

● Added Windows 10 (as host SO) support.

● Deployable behind web-proxy supported.

● LAVA update in progress: from 2016.12 to 2017.7

Follow the current effort:

● Testing project at gitlab.com under cip-project group.

● CIP testing project management wiki page.

B@D: at ELCE 2017

● New release including the latest features.

● Create reports focused on maintenance.

● B@D 101 training session on Sunday Oct 22nd (time to be

confirmed)

● Meeting to define coming priorities.

AGL and CIP collaboration

● CIP is designed to sustain limited efforts over a very long

period of time. CIP is a good partner when thinking about

maintenance.

● Any testing service requires a significant investment up

front. AGL is a good partner when thinking about intensive

efforts.

● “lab in a box” can become the initial collaboration point.

Thanks.

Questions?