Monthly Archives

May 2017

Civil Infrastructure Project – Year One Update + Whitepaper Release

By | Blog

We’ve launched the Civil Infrastructure Platform (CIP) project just over a year ago, and since then, we have made a lot of progress in making Linux usable in industrial grade environments such as power plants, railway systems, and so on. The followings outlines the achievements since the inception of the project.

  • Organized a scheme to maintain the Linux Kernel for 10+ years, including appointing of CIP super long term support (SLTS) kernel, Ben Hutchings.
  • Established v4.4 as the first CIP SLTS Kernel.
  • Identified the reference hardware platform we will target to maintain; Beaglebone Black and Renesas RZ/G1M.
  • Building up a concept of “Base Layer”, which consists of the Linux kernel and very basic components that would be used in the industrial grade system environment.
  • Started a test framework project, Board @ Desk, that will enable anyone to test the CIP Kernel in their environment and share the test result, that will result in a reduction to the testing effort among those who use CIP Kernel for their system.

CIP has been delivering a measurable amount of output over the last year or so.

Today, we are very pleased to inform all of you that CIP recently added even more value to our industry; investing in the Real Time Linux Project, the first formal release of Board @ Desk, and our Whitepaper publication.

  1. Investment in Real-Time Project

Again, our work is to develop a software “Base Layer” to support mission critical systems like power plants and train systems, etc. Those systems require hard, real-real time capability, so it is very critical for us that the Real Time patches be integrated into the mainline kernel sometime in the near future.  To make that happen, CIP decided to take action.

Today, we would like to announce that CIP has become a Gold Member of the Real Time Linux Project hosted at the Linux Foundation.  To be very clear, by becoming a member of Real Time Linux Project, we are not paying money only and are letting someone else do the work, but we will be making a real commitment to the mainlining of the Real Time patch set, ensuring it will happen.

CIP members will not only be contributing to the upstream Kernel, but will also make sure to maintain it so the industry can rely on the use the kernel for their real business.  To do so, CIP member, Daniel Wagner, Siemens, has become the maintainer of -rt series of CIP Kernel.

  1. Formal Release of Board @ Desk

One of the pain-points for the industry has been testing.  We all do testing. In many cases, we all do very similar (if not exactly the same) testing at each company separately, yet testing has been the area which there has not been much collaboration among the open source community up until some years ago.

Recently, we’ve seen this situation changing. Testing has become one of the hot areas of open source collaboration. LTSI launched a testing project 3-4 years ago, called JTA, and the project has now become the origin of an independent project called Fuego, maintained by Tim Bird.  It has also become a source of a testing framework used by Automotive Grade Linux (AGL), called CIAT. Linaro has developed LAVA and is supporting the Linux Kernel community through the kernelci.org project.

For CIP developers, we would like to take this opportunity to announce the release of “Board @ Desk”, an instance of LAVA and KernelCI integrated by Codethink for CIP that should allow a customised and easy to deploy instance of the kernelci.org and LAVA projects that should allow developers to test Linux kernels on boards connected to their own development machines using the tooling used by one of the most successful Open Source and distributed testing projects, kernelci.org.

With this effort, the CIP project is trying to create a first step towards “trusted testing” within CIP for every member and the CIP kernel maintainer.

  1. New Publication

Finally, we have an announcement regarding our new publication.

CIP is a very engineering-centric project in nature. Our main focus is not a sexy and innovative technology, but rather more conservative maintenance work to establish a foundation for the systems that have to run our society for many, many years.

Buildings

Thus, as already mentioned, it has been just over a year since CIP has been started and delivered a measurable amount of output, yet we have not reached out much to the developers to whom CIP can be valuable.  This whitepaper provides the information developers need to understand who we are and what we are doing, and what value our activities can have for them.

We will be distributing the hard copy of the white paper at our booth at Open Source Summit Japan, May 31st through June 2nd. If you are participating in the event, please make sure to come to our booth to pick up the white paper (both English and Japanese versions are available)

You can also download the whitepaper from here.
(Japanese version is also available here)

We are looking forward to seeing as many of you as possible at Open Source Summit Japan!

CIP Project releases a tool-box based on LAVA and KernelCI to test Linux kernels locally: Board At Desk v0.9.1

By | In the News

The Civil Infrastructure Platform project, a Linux Foundation Initiative, is happy to announce the publication of Board At Desk – Single Dev. v0.9.1, a customised and easy to deploy instance of the kernelci.org and LAVA projects that should allow developers to test Linux kernels on boards connected to their own development machines using the tooling provided by one of the most successful Open Source and distributed testing projects.B@D v0.9.1

This instance is provided in this first release in two forms:

  • As a vagrant VM image/recipe.
  • As a VM image, widely called box.

Please visit the CIP Testing project Download page to download the first release of Board At Desk – Single Dev. (B@D v0.9.1).

With this effort, the CIP project is trying to create a first step towards “shared and trusted testing” by every member and the CIP kernel maintainer. It also has as a goal to extend and simplify the current use case satisfied by kernelci.org, focusing on those embedded developers that have direct access to boards, by reducing the deployment, configuration and maintenance costs. Finally, CIP intends to increase the number of developers and organizations willing to participate in kernelci.org by providing a simple mechanism to evaluate the technologies involved in what CIP consider B@D’s upstream project.

Some of the most important actions taken by the team behind B@D have been focused in two areas:

  1. Merged the KernelCI and LAVAv2 Virtual Machines together into one.

KernelCI was based on Ubuntu v14.04, it used Nginx as the Web Server and SimpleHTTPServer for the Storage Server which is where the builds are stored. LAVA was based on Debian and used the Apache Web Server and the Django Content Management System for the Frontend Web Framework. Both web servers wanted to use port 80.

The current VM uses Debian Jessie only. It runs KernelCI on Nginx and LAVA on Apache on reassigned ports. The KernelCI Storage Server has been migrated over to use Nginx on a reassigned port.

  1. Connection to the board.

The released VM assumes the usage of an FTDI USB-to-Serial cable to connect the host machine to the Beaglebone Black. It uses ser2net to route the /dev/ttyUSB0 serial port to a TCP port on the host machine which allows the user to use telnet to communicate to the Beaglebone Black console for remote login and boot messages. It also allows LAVA to use tftp to transfer the kernel directly over to the board eMMC without needing to burn an SD Card.

This B@D version supports Beaglebone Black. Renesas RZ/G1M support is in progress and the rest of the CIP reference boards will be supported in the near future.

Further information about what you will find in Board At Desk – Single dev. (B@D v0.9.1) can be found in the B@D Feature Page.

If you are interested in testing kernels using this version of the tooling please meet the developers at the cip-dev mailing list. If you find bugs in KernelCI or LAVAv2 themselves, please report them upstream. If you find them in the configuration or any of the previously described topics, please report them in the CIP-testing bug tracker. More general information about the CIP testing project can be found in the CIP Testing Landing Page.