====== CIP Technical Steering Committee F2F Meeting ====== Date: 30 May, 2017\\ Time: 11am-3pm (12pm-1pm Lunch)\\ Place: Tokyo Conference Center Ariake **Boardroom** , [[http://www.tokyo-cc.co.jp/eng/features_a_floor3f.html|Level 3F]], on the Ariake side. Tokyo conference center ariake. Ariake Central Tower 3rd&4th Floor. 3-7-18 Ariake, Koto-ku, Tokyo 135-0063 ===== Roll Call ===== * Noriaki Fukuyasu (The Linux Foundation) * Hiroshi Mine (Hitachi) (V: Voting member) * Takuo Koguchi (Hitachi) * Hidehiro Kawai (Hitachi) * Takehisa Katayama (Renesas) (V) * Wolfgang Mauerer (Siemens) (V) * Yoshi Kobayashi (Toshiba) (V) * Daniel Sangorrin (Toshiba) * Agustin Benito Bethencourt (Codethink) * Masato Minda (Plat’Home) * Annie Fisher (The Linux Foundation) ===== Agenda Discussion ===== * Roll Call * Technical Roadmap and milestones * Election of TSC Chair * Kernel Feature ===== Election of TSC Chair ===== * Yoshi Kobayashi (Toshiba) has been elected by the voting member of the TSC as the chair, to serve till end of March, 2018. ===== Technical roadmap and milestones ===== ==== SLTS kernel ==== * Goal: Set Up a SLTS kernel * Status: 4.4.69-cip4 has released * Action items: * (Ben): Review kernel features and make a list of features which may not able to support by CIP * Most of CIP members would like to have Overlay FS in CIP kernel * [Sangorrin] I will send Ubuntu backported patches to CIP * http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/log/fs/overlayfs * [Agustin] * The proposal is that Ben H. finishes the overview first and then we evaluate the features that are currently not supported in order to prioritise them. * Ben H. can work on those features. My suggestion is that instead of him doing the work, he acts as reviewer/mentor of Members kernel hackers. ==== CIP testing Phase 1 ==== * Goal: A single developer can test CIP kernel at their desk. * Status: For B@D, need to clarify OSS license * Action items: * OSS license issue has to be fixed before release * Need to revise announcement document and descriptions to avoid to use "software". Instead of “software”, we should use “tools” in any document * Make an announcement * [Sangorrin] Please consider adding the proxy support and port number patches I sent (e-mail: Problems installing "Board at desk"). * [Agustin] noted. We will if we haven’t. * LF will go back to Scott at the Linux Foundation to determine if the replacement of the term “software” with the term “tools” is sufficient. ==== CIP testing Phase2 ==== * Goal * Functional tests are working on CIP reference boards * More tests with boards * Sharing test results * More close to KerneCI and LAVA (e.g. Upstreaming) * KernelCI is moving to Docker. Shall we contribute to it? * [Sangorrin] in case it’s done, use two separated Dockerfiles. * Action items * Start to use board test, continue to consider collaborations and share inputs, outputs and configurations through the mail list (to be created). Also, utilize a repo to make the logs available, if that is found to be scalable with a plan for alternative storage. * Define test sets. Provide a checklist and discuss. * Collaborate with upstream projects * KernelCI * Lava * [Sangorrin] Fuego includes LAVA support now. * [Sangorrin] Proxy support is needed in LAVA. * Fuego * [Sangorrin] I added CIP kernel tests to Fuego (build test, kselftests) * [Sangorrin] Testing BOF session on Friday 14:00~14:50 * [Sangorrin] CVE tests were added to LTP recently. * [Sangorrin] I will contribute to LTP with support for stable kernel versions. * More boards for testing * Identifying how to share the test results Members reviewed Action-2 on https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting?rev=1496115658 Proposal: Move to Action-2 for next CIP testing\\ Motion to approve: Wolfgang Mauerer\\ Second: Takehisa Katayama\\ Approved. ==== Project-X ==== * Goal: Create minimum Debian (source code/binary) based root file system with CIP kernel * Deby, ISAR, ELBE * “Building Debian-Based Products: Experiences in Collaboration - Baurzhan Ismagulov, ilbers GmbH” (31st May, 14:00~) * Deby slides: * http://elinux.org/images/2/2e/MiniDebianConfJapan-Yoshi.pdf * Status: x86 and Beaglebone Black and Cyclone-V supported * License * MIT for meta-projectx recipes (Same as Yocto Project) * Action items: * Start CI with customized rootf: Siemens & Toshiba * Renesas board support need to be added ==== RT kernel preparation ==== * Goal: Merge RT patch with CIP kernel for each CIP release then test it. * License: GPLv2 for CIP kernel + RT * Status: Daniel Wagner is working for this topic * Action items: * For RT Kernel prep, ask Steven R. to assist Daniel W. * Current state * CIP maintain RT and non-RT * Issue: how to reduce effort to maintain two kernels * Action(DW): Learn how Steven R. maintains the current stable-rt Kernel * Action(TSC): CIP needs to define the process to release the CIP Kernel with RT patch. ===== Base-layer discussion ===== * Toolchain version * U-boot policy * Will move to next TSC session ===== Real-time Linux Project ===== * Boards for testing * Yoshi asked to RTL and they can accept boards from CIP for testing * Will CIP provide a hardware for testing? * They have Beaglebone Black. But they don’t have Renesas RZ/G1M * AI: Yoshi already mentioned Renesas RZ/G1M. Need to confirm by TSC * The process to add the board is the follows * The board has to be a part of CIP RH * Ask them to add boards (done) Yes. we can add boards. * Please make sure, that the boards fulfil the requirements explained in this document: * [[https://ci-rt.linutronix.de/download/system-requirements.pdf|https://ci-rt.linutronix.de/download/system-requirements.pdf]] * It would be great, if you could use our prepared rfs * [[https://ci-rt.linutronix.de/download/target-elbe-rfs/|https://ci-rt.linutronix.de/download/target-elbe-rfs/]] * Send it to them * Todo: We may need to provide setup instruction for the board * Action items * Renesas will review the RT requirements document and then provide a recommendation. * Siemens to consider CIP as reference board after an internal review. ===== Action items from this F2F meeting ===== * Action (AF): LF will go back to Scott at the Linux Foundation to determine if the replacement of the term “software” with the term “tools” is sufficient. * Action (YK): For RT Kernel prep, ask Steven to assist Daniel W. * Action (DW): Learn how Steven R. maintains the current stable-rt Kernel * Action (TSC): CIP needs to define the process to release the CIP Kernel with RT patch. * Action (WM & YK): Start CI with customized rootf: Siemens & Toshiba * Action (TK): Renesas will review the RT requirements document and then provide a recommendation. * Action (WM): Siemens to consider CIP as reference board after an internal review. * Action (Hitachi): Prepare documents for Functional Safety discussion for F2F (October) * Action (YK): To send current prioritization to Takehisa Katayama ===== Next meeting ===== * F2F meeting * ELC Europe 2017 * Would like to discuss more about Functional Safety * Conference call * 12 of June, 2017 (regular conference call) Review of Booth Schedule Chairman closed the session at 14:59