User Tools

Site Tools


civilinfrastructureplatform:ciptestingmanagement

This is an old revision of the document!


CIP testing management

Board At Desk planning and progress

In this section you can follow how the project is progressing and the plans for the coming weeks. As described in the CIP Testing project description page 4 actions describe what this effort is about. Those actions has been decomposed in several milestones, described below. Check the diagram for further detail:

CIP testing high level action plan

  • B@D Improvements (orange): tasks related with updating B@D and adding new functionality requested by CIP Members or required to accomplish the overall goals (again, described in the CIP Testing project description page.
  • Action 2 preps and signing (gold/pear): preliminary tasks to configure B@D capabilities needed to reach the goals of this second action. One of the key ones, originally not fully supported by LAVA and KernelCI, is the handling of signatures/hashes so we ensure that the main components of the environments (tests, logs, reports, kernels/systems, firmware, etc) are signed so CIP Members can trust the obtained results.
  • Health-checks (blue): the current health-check needs to be improved in order to guarantee that the correct tests, board, B@D version, system version, etc. are being used during the testing process before sharing the testing results, as a way to guarantee that they are meaningful and, up to certain point, reproducible.
  • Reporting (pink): the current reports that LAVA and KernelCI produce are designed for the kernel (developer) community. They need to be adapted to the CIP use case, which is more focused on maintenance.
  • Increase test Coverage (green): once the system is configured, the focus will turn into increasing the test coverage of both, the CIP kernel and the core system.
  • ELCE 2017 (yellow): ELCE is a major milestone for CIP, so for the CIP Testing project. Some key tasks will be executed during and before the event to promote the usage of B@D and to discuss future steps.

The current diagram is a modified kanban board that shows the current state of the Testing project at high level. It will be updated regularly. For a more fine grain analysis, please check CIP testing management instance at gitlab.com.

CIP testing high level action plan

The current goal is to present at ELCE the testing environment working, leaving refinements and none critical tasks for the weeks after the event.

Board at Desk Delivery processes and practices

Description of the processes and practices involved in the delivery of Board at Desk tools

CIP testing project management processes

Bugs management

* Check the CIP testing project bugs board

Release process howto

* readme.md should be modified before the signing.

* The box should be called cip_board_at_desk_v0.9.1.box.

* The sources as board-at-desk-single-dev.tgz etc placed in the sources directory beneath a directory containing the version number.

Marketing material and plan

B@D v0.9 release: social media campaign

Main messages:

  • B@D reduce the deployment, configuration and maintenance effort to those who want to test kernels.
  • KernelCI and LAVA are upstream.
  • B@D is an effort towards shared and trusted testing.

Remember that:

  • RD is Release Day: May 30th
  • RT is Release time: 17:00 EDT / 22:00 UTC / 23:00 UK / 00:00 CEST (May 31st) / 07:00 JST (May 31st) This is due to the fact that the release will take place during the opening of the Open Source Summit Japan.

Links to be included:

Twitter
  • Hashtag to be used: #ciptesting #linuxfoundation #linux #lava #kernelci #ossummit
  • Remember to use a shorten URL service to be able to include more characters.
English Japanese Chinese Spanish
RD-1 Learn about the testing effort within the @linuxfoundation CIP initiative http://bit.ly/2mZMHmx #ciptesting #linux 瞭解更多關於 @linuxfoundation CIP 協會的測試工作 http://bit.ly/2mZMHmx
RT-12 Interested in kernel & embedded linux testing? CIP will have news tomorrow http://bit.ly/2mZMHmx #ciptesting #linux #linuxfoundation

http://bit.ly/2mZMHmx #ciptesting #linux #linuxfoundation | – |

RT-1 What if you could test a kernel in your board connected to your laptop using #lava & #kernelci ? #ciptesting #linux #linuxfoundation 如果你透過筆電上的 #lava 以及 #kernelci 就能對板子上的 kernel進行測試? #ciptesting #linux #linuxfoundation
RT CIP project released VM with #lava & #kernelci to test #linux kernels locally More news http://bit.ly/2rhSILs #linuxfoundation #ossummit CIP 專案發佈包含 #lava 以及 #kernelci 的 VM, 可用來對 #linux kernels 進行本地測試更多消息可參閱 http://bit.ly/2rhSILs #linuxfoundation #ossummit Proyecto CIP lanza máquina virtual con #lava y #kernelci para testar el kernel #linux localmente. Noticia completa http://bit.ly/2rhSILs
RT+1 #linux kernel testing with #lava & #kernelci in a VM. Check the news from CIP project http://bit.ly/2rhSILs #ciptesting #linuxfoundation 透過 VM 中的 #lava 以及 #kernelci 來對 #linux kernel 進行測試更多消息可參閱 CIP 專案 http://bit.ly/2rhSILs #ciptesting #linuxfoundation
RT+12 Interested in #lava & #kernelci ? Now integrated in a VM you can deploy & use http://bit.ly/2rhSILs #ciptesting #linux #linuxfoundation 對 #lava 以及 #kernelci 有興趣嗎? 現在他們已經整合進 VM, 你們可以透過它來進行部屬以及使用 http://bit.ly/2rhSILs #ciptesting #linux #linuxfoundation
RD+1 Learn more about the #ciptesting effort to test the CIP #linux kernel at the #OSSummit in booth http://bit.ly/2rhSILs #linuxfoundation #OSSummit 有展位來提供更多關於測試 CIP #linux kernel 以及 #ciptesting 工作的相關消息 http://bit.ly/2rhSILs #linuxfoundation
Linkedin
  • Hashtag to be used: #ciptesting #linuxfoundation #linux #lava #kernelci #ossummit
English Japanese German Spanish
RD-1 The Civil Infrastructure Platform is a Linux Foundation initiative focused on building a commodity industrial grade Linux based system and maintain it over a long period of time. Testing this system is an strategic activity. Tomorrow May 31st the CIP testing team will release their first deliverable, a Virtual Machine where LAVA and KernelCI have been integrated in order for any developer to test linux kernels, like the CIP kernel, in her own machine with a reference board attached to it. Learn more about this testing effort and stay tuned for the release announcement. https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting.
RT The Civil Infrastructure Platform, a Linux Foundation Initiative is happy to announce the release of a Debian based Virtual Machine that will allow developers to test Linux kernels on a board attached to their own machine using LAVA and KernelCI, that is, the same tools used in the successful kernelci.org project. Check the release announcement for further information: http://bit.ly/2rhSILs
RD+1 If you are interested in testing Linux kernels please take a look at what the CIP testing project is doing. LAVA and KernelCI have been integrated in a single Debian based virtual machine allowing any developer to use these tools to test a kernel in a board attached to their own computer. The CIP developers have also created a step by step howto that severely simplifies the configuration process. Try it out and let them know what you think. http://bit.ly/2rhSILs
  • Groups we can publish the announcement in:
    • LKML
    • Linux Users
    • FOSS professionals
    • FLOSS professionals
    • Linux Foundation
    • Any specific related with civil infrastructure? DELETEME

B@D v0.9 release: release announcement

English version

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

The Civil Infrastructure Platform project[1], a Linux Foundation Initiative, is happy to announce the publication of Board At Desk - Single Dev. (B@D) v0.9.1, a customised and easy to deploy instance of KernelCI[2] and LAVA[3] 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, http://www.kernelci.org .

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[4] 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 effort. Finally, CIP intends to increase the number of developers and organizations willing to participate in http://www.kernelci.org by providing a simple mechanism to evaluate the technologies involved in what CIP consider B@D's upstream projects (LAVA and KernelCI).

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.

2. 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 B@D v0.9.1 can be found in the B@D Feature Page[5].

If you are interested in testing kernels using this version of the tooling please meet the developers at the cip-dev mailing list[6]. 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[7]. More general information about the CIP testing project can be found in the CIP wiki[8].

You can also read this release announcement on the CIP project blog[9]

[1] https://www.cip-project.org/ [2] https://github.com/kernelci/ [3] https://validation.linaro.org/ [4] https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipdownload [5] https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingboardatdesksingledevfeaturepage [6] https://lists.cip-project.org/mailman/listinfo/cip-dev [7] https://gitlab.com/cip-project/cip-testing/testing/boards [8] https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting [9] http://bit.ly/2rhSILs

civilinfrastructureplatform/ciptestingmanagement.1502707638.txt.gz · Last modified: 2017/08/14 10:47 by Agustin Benito Bethencourt