====== CIP Technical Steering Committee Meeting ====== Date: 8 May, 2017 ===== Roll Call ===== * Noriaki Fukuyasu (The Linux Foundation) * Hiroshi Mine (Hitachi) * Takehisa Katayama (Renesas) * Chris Paterson (Renesas) * Yoshi Kobayashi (Toshiba) * Daniel Sangorrin (Toshiba) * Agustin Benito Bethencourt (Codethink) * Masato Minda (Plat’Home) * Wolfgang Mauerer (Siemens) ===== Agenda ===== * Roll Call * Updates and Discussions * OSSJ preparation * Preparation for CIP workshop on 30th May * CIP kernel development * Board @ Desk / CIP kernel Testing * ProjectX * U-boot policy * DebConf * Whitepaper Status * Other topics ===== Updates and Discussions ===== ==== OSSJ preparation ==== * **Propose ideas for demo booth. (Please add your proposal.)** * TOSHIBA: Power Plant Controller with CIP kernel * Plat’Home: Simple IoT Demo. (This demo does not require ethernet. It uses the LTE) * Siemens: IoT2040 device that runs CIP kernel (just the device, no active showcase). Depends on whether export control can be solved or not. * The device will be send to LF office at Yokohama. * Renesas: Demonstrate CIP test framework on RZ/G reference platform (same as Agustin’s [[https://gitlab.com/cip-project/testing/issues/70|demo on BBB]]) * The booth AV/Furniture orders must be completed by May 15th. * Please sign up to the event within May 8th as much as possible. * **AI(LF): Tweet on CIP speeches and demo showcase.** ==== Preparation for CIP meeting on 30th May ==== * Proposed schedule * 11:00-15:00 TSC meeting (Lunch included) * 15:00-17:00 Workshop (Proposed) * [[https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipconferences#workshops-and-meetings|https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipconferences#workshops-and-meetings]] * RSVP required * 16:30-17:00 CIP Booth setup * Tuesday, May 30: 16:30-17:00 * booth setup hours **Tuesday, May 30:** 1:00pm - 5:00pm (Annie and Nori have to check with the event team if we can start setting up the booth after 5pm) * On Tuesday, We only setup basic staffs such as panel stand and tables * Wednesday, May 31: 7:30am - 8:00am * All booths MUST be fully set by 8:00am Wednesday morning * NOTE: Booth Tear-Down Hours: Friday, June 2: 4:00pm - 6:00pm * Place: Tokyo Conference Center Ariake (Room location will announce later.) ==== CIP Kernel Development ==== * Kernel security tracker * Ben H. created scripts to track CVEs across mainline and stable branches * [[https://lists.cip-project.org/pipermail/cip-dev/2017-April/000221.html|https://lists.cip-project.org/pipermail/cip-dev/2017-April/000221.html]] * [[https://gitlab.com/cip-project/cip-kernel-sec|https://gitlab.com/cip-project/cip-kernel-sec]] * RT_PREEMPT support * Daniel Wagner proposed for RT kernel maintenance * [[https://lists.cip-project.org/pipermail/cip-dev/2017-April/000225.html|https://lists.cip-project.org/pipermail/cip-dev/2017-April/000225.html]] * CIP will invite Steven Rostedt to CIP workshop * Need to create RT repo under the GitLab/cip-project * Aldo include the -rt repos in the scripts to track CVEs * Kernel feature support * Under evaluation by Ben H. * Kernel update to LTS 4.4.60 on its way ==== Board @ Desk / CIP kernel Testing ==== * The tentative release date is May 16th. * Agustin will confirm it on Wednesday. * Currently the team is working on running existing tests successfully on the BBB board. * Check last report: [[https://lists.cip-project.org/pipermail/cip-dev/2017-May/000228.html|https://lists.cip-project.org/pipermail/cip-dev/2017-May/000228.html]] * Milo Casagrande and Daniel Sangorrin mentioned B@D as a part of test spec discussion for KernelCI and Fuego. * [[https://lists.cip-project.org/pipermail/cip-dev/2017-April/000226.html|https://lists.cip-project.org/pipermail/cip-dev/2017-April/000226.html]] * KernelCI move to container based approach. * > // - Will the KernelCI project collaborate on the board-at-desk-single-dev VM or create a new container? // > // + If creating a new one, do you have enough resources or can you give us an approximate date?// * (Comment from Milo) We don't really collaborate with them on that, strictly speaking, but we try to help them whenever we can and whenever they need help. Our approach with the container is slightly different compared to the VM one: we are looking at how to "containerize" the system in order to deploy it, but more "on the cloud" side than "on the desk" side (although, with Docker, it should be fairly portable). * [Agustin}: not much activity on this front by KernelCI: [[https://github.com/kernelci/kernelci-docker|https://github.com/kernelci/kernelci-docker]] There are plans to provide KernelCI in a container since the very beginning of the KernelCI project. * [[https://lists.cip-project.org/pipermail/cip-dev/2017-April/000223.html|Dev meetings]] * Open to use appear.in if Google services represents an issue. * Chris: I can now use Google Hangouts, cannot use appear.in (firewall). * [[https://lists.cip-project.org/pipermail/cip-dev/2017-April/000215.html|Proxy-related issues]] on first install * Agustin: To download the built kernel? * Daniel: Max retries exceeded with url: /kvm/standard/stretch-2.img.gz * Renesas reported last week they have successfully executed the BBB healthcheck with B@D using the downloadable .box. ==== ProjectX ==== * No updates during this period. * Now, Project X works on x86_64, BBB, Altera Cyclone-V. * What’s next? * Have a rootfs for testing? * Create a Debian’s binary based rootfs ==== U-boot Policy ==== * WIP on wiki. Please review: * [[https://wiki.linuxfoundation.org/cip/u-boot|https://wiki.linuxfoundation.org/cip/u-boot]] ==== DebConf ==== * **Jan & Wolfgang completed the sponsorship application. Annie and Nori will take care the invoice when it arrives.** * **(AI: Yoshi) Submit a talk to Debconf (Deadline: 3rd June)** ==== White Paper Status ==== * **Done** [[.|Back to the parent page]]