warning: long mail
CIP is a Linux Foundation initiative to create a commodity Linux
based platform for train railway control systems, power plants, etc
which needs to be maintained for a very long time. In extreme cases, for
50 years. The first outcome is the CIP-kernel, based on 4.4 LTS and
maintained for now by Ben Hutchings, a colleague of mine.
This week, within the CIP (Civil Infrastructure Platform) project, we
have published a VM where we have integrated LAVAv2 and KernelCI on
Debian so any developer can test a specific kernel in a board attached
to his/her laptop. You have probably read in this mailing list some
questions coming from some colleagues of mine from Codethink.
Since the project is initially focused on the CIP kernel, it was natural
to select LAVA and KernelCI as our default tools. We would like to see
in the near future our CIP kernel as part of kernelci.org We move slowly
though since CIP is still a young project with very limited resources
but for now, and due to the very unique requirements CIP needs to
address, safety critical requirements among them, we need to get
absolute control of the testing infrastructure/service we will use.
As a previous step towards building our own testing/reporting
infrastructure and service, understanding LAVAv2 and promoting it among
the developers involved in this initiative is essential. I think that
B@D will be useful for this purpose, allowing us to start testing and
sharing the results among CIP devs. Codethink has invested a significant
amount of effort in creating a step by step deployment-configure-test
guide. Any feedback is welcome.
B@D is meant to significantly reduce the entry level effort to use both,
LAVA and KernelCI. We consider B@D as a downstream project of LAVAv2 and
KernelCI. Hopefully, once we start using it within CIP we will be able
to provide meaningful feedback on this list.
The team behind B@D, is subscribed to this list and the #linaro-lava IRC
channel. We have our own mailing list cip-dev for general support of CIP
related topics, so B@D too, but our idea is to route users here for LAVA
specific questions that are unrelated with the set up of the environment
and participate in supporting them up to the the best of our knowledge,
if you think that is a good idea. We are unsure yet about the level of
success we will get with this effort though.
Since probably for many of you this is the first news you get about CIP
and B@D, feel free to ask me or my colleagues. We will do our best to
answer your questions.
You can get all the technical information about B@D at feature page.
Feel free to download it. The integration scripts are located in
gitlab.com under AGPLv3 license. Our cip-dev mailing list is
obviously an open one.
I would like to finish thanking the devs for the great work done in LAVA
and to those of you who have helped the Codethink guys to get to this
point. LAVAv2 and KernelCI are complicated beasts, hard to swallow
without support, and at the same time, very useful. I guess that is part
of the beauty.
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink