CIP Technical Steering Committee Meeting

CIP Technical Steering Committee Meeting

Date: 02 October, 2017

Roll Call

Agustin Benito Bethencourt (Codethink)
Annie Fisher (LF)
Noriaki Fukuyasu (LF)
Hiroshi Mine (Hitachi)
Hidehiro Kawai (Hitachi)
Masato Minda (Plat’Home)
Takehisa Katayama (Renesas)
Daniel Sangorrin (Toshiba)
Yoshi Kobayashi (Toshiba)
Wolfgang Mauerer(Siemens)

Agenda

Roll Call
Action items
Topic prioritization
Updates and Discussions

Updates and Discussions

ELC-E preparation

CIP schedule
Meetings
- CIP TSC meeting (Sunday 9:00-14:00 including lunch) @ (ROOM)
- CIP WS (Sunday 14:00-18:30) @ (Athens)
  - Workshop activities (proposals): ToDo: Agustin to set up a wiki page. Done
    - 14:00-15:00 AGL and CIP testing collaboration discussion

15:00-16:00 CIP kernel maintenance meeting (CIP members only) 16:00 to 17:30 B@D 101 training session (open prior registration) 17:30 to 18:30 CIP Kernel Q&A (open prior registration) 18:30(or 19:00)-20:00 Booth setup

Y2038 (Monday 11:45-12:45) @ (ROME) : 15 people appx
- Confirmed by Arnd.
- Request for topics. Depending on the questions, further experts can be invited. Make good use of this opportunity
Developer meeting (Kernel maintenance meeting for Everyone) (Tuesday 13:00-14:00) @ (Liben Room) reserved from 13:00-14:00) 10-15 people appx
- Agustin: can we start promoting this meeting? It will be open to devs interested in CIP (kernel+system), right after the CIP Talk
CIP Board meeting (Wed. 12:35-16:00) @ (Liben Room)
Demo @ booth
Please update DEMO sheet on this sheet
Equipment hire update (Annie)
- http://events.linuxfoundation.org/events/open-source-summit-europe/sponsors/guide
- Please check the guide for all options for demo booth
B@D 101 request for approval
Now that the budget has been approved, Agustin will talk to Nori/Annie to check what is available and what should be bought.[DONE]
Can we start creating an agenda for the F2F TSC meetings? (add to the “Things to be discussed in next F2F meeting” section further down)

Y2038

[Agustin] Meeting with Arnd during ELCE closed.
- Y2038 (Monday 11:45-12:45) @ (ROOM) : 15 people appx
- Confirmed Arnd presence.
- Call for agenda topics.
  - Depending on the agenda Arnd and Agustin are willing to invite further experts.
- Siemens and Renesas, Toshiba has confirmed the presence.
- Should we invite people interested from other LF group
- [AI] Members should should ask developers within the companies if they would have any questions to Agustin and Arnd prior to the meeting.

CIP Core update (Project-X) 1/2

Project proposal
- A project proposal is available at the following URL:
  - https://docs.google.com/document/d/1c0VBbOrF-DxGE1rMDaxGklbxxgEtZupXuZ_POkjWLyY/edit#
  - Also posted to cip-members ML
- Action items
  - License review and approval
    - TSC voting members
    - Linux Foundation legal team
      - CIP would like to ask potential risks for IP
  - Vote
    - TSC voting members

CIP Core update (Project X) 2/2

Milestones
- Deby board support [OK]
- B@D support for testing CIP Core on Renesas iwg20m [OK]★
  - Requires a remote power switch
  - No KernelCI support, only LAVA
  - Actually, I’m using LAVA on docker since B@D is not released yet
    - Agustin: this Thursday we will know when B@D will be released (before ELCE).
- Wiki page [OK]
  - https://gitlab.com/cip-playground/project-x/wikis/Introduction-to-the-CIP-Project-X
  - https://wiki.linuxfoundation.org/civilinfrastructureplatform/start#project-x
- Official release and press release [ONGOING]
- ISAR board support [TODO]
- Select SLTS packages [TODO]
Deby support status
- Renesas iwg20m [OK]
- QEMU x86-64 [OK]
- BBB [OK]
- Cyclone V [OK]★
B@D integration status
- Renesas iwg20m [OK]
- QEMU x86-64 [TODO]
- BBB [TODO]
- Cyclone V [TODO]

Yocto Distribution

(Notes from Chris but he is unable to attend the call today)

Sean Hudson started a conversation on cip-dev with regards to creating a meta-cip layer to work with OpenEmbedded.
Does the CIP project want to start work on this officially? Or leave it to those outside of the project to come up with their own implementation?
- [YOSHI] This is not decided yet. I replied to Sean as he follows:
  - The goal here is to see if we can actually build file system based on CIP base-layer and Yocto layers by using Poky. Do the same thing as the Project X does but using CIP kernel and limited number of Debian source code AND OE layers. To make it a bit clearer, I assume the combination as the follows for the goal: CIP base-layer (Kernel + limited number of long-term supported OSS packages from Debian) + Poky + OE-layers But the following combination might be a good at starting point. CIP kernel + Poky + OE-layer
Originally it was the aim of the project to support both Debian and Yocto distributions.
Options to add Yocto support:
- a) Create a new project like Project-X (Project-Y?)
  - This would keep both distributions completely separate
- b) Enhance Project-X (CIP-Core) with a meta-cip layer
  - This would allow both distributions to be “CIP-Core”, but I’m not sure how such an implementation would work.
    - Kas project could be an option to implement both in one.

LTS to be supported for 6 years?

(Again from Chris, sorry!)

https://arstechnica.com/gadgets/2017/09/android-users-rejoice-linux-kernel-lts-releases-are-now-good-for-6-years/
Big impact for CIP, given that Kernel v4.4 will now be supported until 2022 by Greg.
- [YOSHI] this is a good news. I think.

Kernel Maintenance

Report from week 38 and 39 sent to cip-dev ML. Please review it
- Reviewed and applied patches for new hardware support in 4.4
- Reviewed patches in 4.4-stable branch. The idea is to release a new kernel soon (before ELCE)

CIP Testing

Board @ Desk

Report from week 38 and 39 sent to cip-dev ML. Please review it
- initramfs issues solved.
  - Daniel: why not using CIP Core instead of a custom initramfs.
    - https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipsystembuildhowto
    - https://gitlab.com/cip-project/cip-testing/board-at-desk-single-dev/merge_requests/41
  - Daniel: it’s not necessary to use the default prompt that LAVA expects. You can confiture it.
    - https://gitlab.com/cip-project/cip-testing/testing/issues/136
- Several fixes merged.
- Next step B@D 1.0 release.
  - Daniel: Will I have some days to integrate it with CIP Core before ELCE?
    - Agustin: the current (yet to be confirmed) plan is to release end of week 41. If we cannot, then we will talk to you so we provide you what you need so you do not have to wait until the release is done. We should know if we can or not beginning week 41.

Table of Contents