civilinfrastructureplatform:tsc-meetings:tsc_mm_jul092018
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
civilinfrastructureplatform:tsc-meetings:tsc_mm_jul092018 [2018/09/20 15:56] yoshi removed |
civilinfrastructureplatform:tsc-meetings:tsc_mm_jul092018 [2018/09/20 15:57] (current) yoshi created |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== CIP Technical Steering Committee Meeting ====== |
| - | CIP Technical Steering Committee Meeting ====== | + | |
| - | Date: 03 September, 2018 | + | Date: 9 July, 2018 |
| ===== Roll Call ===== | ===== Roll Call ===== | ||
| Line 11: | Line 10: | ||
| * Masashi Kudo (Cybertrust) | * Masashi Kudo (Cybertrust) | ||
| * Nobuhiro Iwamatsu (Cybertrust) (Representative) | * Nobuhiro Iwamatsu (Cybertrust) (Representative) | ||
| + | * Hiroshi Mine (Hitachi) | ||
| * Hidehiro Kawai (Hitachi) (Representative) (Voting) | * Hidehiro Kawai (Hitachi) (Representative) (Voting) | ||
| - | * HIroshi Mine (Hitachi) | ||
| * Masato Minda (Plat’Home) (Representative) | * Masato Minda (Plat’Home) (Representative) | ||
| - | * SZ Lin (MOXA) (Representative) | + | * Takehisa Katayama (Renesas) (Voting) |
| * Chris Paterson (Renesas) | * Chris Paterson (Renesas) | ||
| - | * Takehisa Katayama (Renesas) (Representative) (Voting) | + | * Wolfgang Mauerer (Siemens) (Representative) (Voting) |
| - | * Daniel Sangorrin (Toshiba) | + | |
| * Dinesh Kumar (Toshiba India) | * Dinesh Kumar (Toshiba India) | ||
| + | * Daniel Sangorrin (Toshiba) | ||
| * Yoshi Kobayashi (Toshiba) (Representative) (Voting) - Chair | * Yoshi Kobayashi (Toshiba) (Representative) (Voting) - Chair | ||
| + | * | ||
| ===== Discussions ===== | ===== Discussions ===== | ||
| - | * | + | ==== Action items from F2F meeting ==== |
| + | |||
| + | * Reproducible builds | ||
| + | * YOSHI: Arrange a meeting with Chris Lamb | ||
| + | * Status: Had a meeting with Chris.L. CIP board will decide where we go. | ||
| + | * Kernel development for next CIP kernel | ||
| + | * MOXA: Send the board support package to upstream | ||
| + | * SZ: Working in progress | ||
| + | * Spectre/Meltdown | ||
| + | * Gregkh slides | ||
| + | * [[https://github.com/gregkh/presentation-spectre|https://github.com/gregkh/presentation-spectre]] | ||
| + | * LazyFP information | ||
| + | * [[http://blog.cyberus-technology.de/posts/2018-06-06-intel-lazyfp-vulnerability.html|http://blog.cyberus-technology.de/posts/2018-06-06-intel-lazyfp-vulnerability.html]] | ||
| + | * Daniel.S is backporting the rest of patches for it. | ||
| + | * Arm vulnerability list: [[https://developer.arm.com/support/arm-security-updates/speculative-processor-vulnerability|https://developer.arm.com/support/arm-security-updates/speculative-processor-vulnerability]] | ||
| + | * Renesas wants to backport Spectre/Meltdown mitigations on 4.4.y | ||
| + | * Spectre variant 1 | ||
| + | * For x86 only backport 2nd wave of patches | ||
| + | * Many drivers still need to be fixed | ||
| + | * Spectre variant 2 | ||
| + | * No patches available for ARM | ||
| + | * Meltdown (variant 3/3a) for ARM | ||
| + | * Only required for Cortex-a75/72/57/15 (RZ/G1) | ||
| + | * Spectre variant 4 | ||
| + | * No patches available for ARM | ||
| + | * AI: tidy up this information | ||
| + | * Cybertrust is interested in this issue. | ||
| + | * Planning to provide first revision of patch. | ||
| + | * Not sure on timescales yet though. | ||
| + | * Patches would need to be ported from upstream to LTS v4.4. | ||
| + | * Kernel maintainer | ||
| + | * Cybertrust: AI(CTJ) Check possible options for kernel maintenance | ||
| + | * CTJ answered to CIP | ||
| + | * Iwamatsu-san will be CIP kernel maintainer (20% to Sep, 40% from Oct.). | ||
| + | * Katayama-san | ||
| + | * If CIP itself has maintainer from CTJ, it is good situation. | ||
| + | * Maintainer should be one person. | ||
| + | * Iwamatsu | ||
| + | * Considering the maintenance system, I think that one person is better. | ||
| + | * AI(Yoshi): Ask to vote. | ||
| + | * | ||
| + | * CIP Core | ||
| + | * Codethink: Ask to Ben.H to get a feedback from Debian-LTS | ||
| + | * DebConf | ||
| + | * AI(LF): Send booth materials to DebConf (Table cover and roll stand). | ||
| + | * Shipping information | ||
| + | * Address for shipping items to DebConf: | ||
| + | |||
| + | AnHui Lee, Microelectronics and Information Research Center, | ||
| + | National Chiao Tung University | ||
| + | No.1001, University Rd., East Dist., Hsinchu City 300, Taiwan (R.O.C.) | ||
| + | +886-3-5712121*31944 | ||
| + | |||
| + | Please label with //company name// and " //DebConf18 - job fair// " | ||
| + | |||
| + | * **Moxa: Due to event conflict, Moxa won't be able to demo products.** | ||
| + | * **Giveaways: CIP LEGO** | ||
| + | * **Whitepaper** | ||
| + | * **AI(LF/TSC): make sure when it is ready.** | ||
| + | * ELC-E | ||
| + | * AI: Yoshi: Submit a talk to ELC-E | ||
| + | * Under review process. | ||
| + | * | ||
| ==== CIP Core packages ==== | ==== CIP Core packages ==== | ||
| Line 34: | Line 96: | ||
| * Ben H. will evaluate these criteria and its impact before attending to DebConf. | * Ben H. will evaluate these criteria and its impact before attending to DebConf. | ||
| * Based on Ben H. feedback, CIP will decide to contact the Freexian leads before the DebConf or not. | * Based on Ben H. feedback, CIP will decide to contact the Freexian leads before the DebConf or not. | ||
| - | * AI(Daniel.S): Send to public mail list to get feedback. (DONE) | ||
| - | * (On going. See above) | ||
| * Criteria for prioritizing security fixes: | * Criteria for prioritizing security fixes: | ||
| - Member package lists | - Member package lists | ||
| Line 43: | Line 103: | ||
| - Security software | - Security software | ||
| - Language runtimes/compilers | - Language runtimes/compilers | ||
| - | * OpenJDK may not be possible | + | * AI(Daniel.S): Send to public mail list to get feedback. |
| - | * Comments | + | |
| - | * LTS: We should send package list with source packages | + | |
| - | * AI(Daniel S.): Ask to Raphael for the package list format. | + | |
| - | * Initial reference implementation with meta-debian however, we need to decide if we are going to use other build system (e.g. ISAR) for reference implementation and include more packages in the base layer. | + | |
| - | * <SZ> There is a discussion thread in Debian to discuss the "armel/armhf arch qualification for buster (Debian 10)" | + | |
| - | * [[https://lists.debian.org/debian-arm/2018/08/threads.html#00009|https://lists.debian.org/debian-arm/2018/08/threads.html#00009]] | + | |
| - | ==== Event participation ==== | + | ==== DebConf ==== |
| - | === DebConf === | + | * Who will attend? The last day to confirm attendance is 6/21 |
| + | * Ben, Wolfgang, SZ, Nobu, Kazu and Yoshi | ||
| + | * Booth should be managed by Wolfgang, SZ, Nobu, Kazu and Yoshi. | ||
| + | * Job fair will be held 28th July(Sat). | ||
| + | * Kazu and Nobu (and maybe SZ) | ||
| + | * AI(Yoshi) ask to them to run the booth. | ||
| + | * CIP will have a booth. | ||
| + | * Address for shipping items to DebConf: | ||
| - | * Reproducible builds | + | AnHui Lee, Microelectronics and Information Research Center, |
| - | * Action items | + | National Chiao Tung University |
| - | * CIP | + | No.1001, University Rd., East Dist., Hsinchu City 300, Taiwan (R.O.C.) |
| - | * Speak to board members | + | +886-3-5712121*31944 |
| - | * Level of funding | + | |
| - | * Structure of contract | + | |
| - | * Specify the goals | + | |
| - | * (DONE) Submit package list which need to be reproducible | + | |
| - | * Ask to LF, how to make contract with RB (in Progress, 8/20) | + | |
| - | * **September or October is the best timing** | + | |
| - | * **After freeze, it is difficult to make reproducible** | + | |
| - | * **RB need to have contract 3 month before the freeze** | + | |
| - | * [[https://docs.google.com/document/d/1xhN5Wi5zyuocq4OtbSghfyHfrf0mGBrQ_t7JG_A6jwI/edit#|https://docs.google.com/document/d/1xhN5Wi5zyuocq4OtbSghfyHfrf0mGBrQ_t7JG_A6jwI/edit#]] | + | |
| - | * **Need to approve in CIP Board** | + | |
| - | * **(9/3) YOSHI wrote a proposal in formal format and send it to CIP board members** | + | |
| - | ==== CIP kernel team ==== | + | ==== AI(LF): Send booth materials to DebConf (Table cover and roll stand). ==== |
| - | + | ||
| - | * Discussed at DebConf to decide the structure of CIP kernel team | + | |
| - | * CIP kernel team will focus both 4.4 and next CIP (4.20 or 5.0) | + | |
| - | * <SZ> When is the freeze date for backporting new features in kernel 4.4 | + | |
| - | * Originally we say approx 5 years. | + | |
| - | * We have to make commitment how many years CIP allow to backport features | + | |
| - | * CIP kernel team will structured with | + | |
| - | * 1 mentor (Ben H.) | + | |
| - | * 2 maintainers for CIP kernel (Iwamatsu-san and bootlin), 1 maintainer for CIP-RT (Daniel. W) | + | |
| - | * Other members from each company such as MOXA and Toshiba (Daniel S.) | + | |
| - | * AI(Kernel team members): Define milestone for next CIP kernel | + | |
| - | * Wait until which version Debian will choose. | + | |
| - | * Kernel configuration | + | |
| - | * Initial blacklist has already prepared by Ben | + | |
| - | * RT will be clarified by Daniel W. | + | |
| - | * Config vs. Board | + | |
| - | * To be discussed | + | |
| - | * AI(SZ): Ask to have weekly kernel team meeting at 5pm(JST) (Need to check time for other timezones) | + | |
| - | * Done. Please join the meeting. | + | |
| - | US-West US-East UK DE TW JP | + | |
| - | 01:00 04:00 09:00 10:00 16:00 17:00 | + | |
| - | * Intel L1 Terminal Fault | + | |
| - | * [[https://www.intel.com/content/www/us/en/architecture-and-technology/l1tf.html|https://www.intel.com/content/www/us/en/architecture-and-technology/l1tf.html]] | + | |
| - | * Some fixes in 4.4.148 | + | |
| - | * https://lkml.org/lkml/2018/8/16/229 | + | |
| - | + | ||
| - | ==== CIP kernel-next ==== | + | |
| - | + | ||
| - | === Version === | + | |
| - | + | ||
| - | * Originally it was thought that v4.20 (or v5.0) would be the next LTS. It now looks like v4.19 will be the next LTS Kernel - [[https://www.kernel.org/category/releases.html|https://www.kernel.org/category/releases.html]] | + | |
| - | * Does anyone have confirmation of the above from Greg? | + | |
| - | * LTS v4.9 will now be supported for 6 years, perhaps v4.19 will be too. | + | |
| - | * Does anyone know what Kernel Debian will be using? Or when they will make a decision? | + | |
| - | + | ||
| - | === Schedule === | + | |
| - | + | ||
| - | * When will CIP make a final decision on the Kernel version? | + | |
| - | * When does CIP plan to make the first cip-next release? | + | |
| - | + | ||
| - | === Support === | + | |
| - | + | ||
| - | * What Kernel configs will we support? | + | |
| - | * What hardware/reference platforms will CIP support? | + | |
| - | * All/subset of the current v4.4-CIP reference platforms? | + | |
| - | * Renesas RZ/G2M | + | |
| - | + | ||
| - | === Maintenance === | + | |
| - | + | ||
| - | (copied from above) | + | |
| - | + | ||
| - | * 1 mentor (Ben H.) | + | |
| - | * 2 maintainers for CIP kernel (Iwamatsu-san and bootlin), 1 maintainer for CIP-RT (Daniel. W) | + | |
| - | * Other members from each company such as MOXA and Toshiba (Daniel S.) | + | |
| ==== Kernel maintenance and testing ==== | ==== Kernel maintenance and testing ==== | ||
| Line 131: | Line 127: | ||
| === Kernel maintenance === | === Kernel maintenance === | ||
| - | * Transition to new CIP kernel maintainer | + | * Working on a new kernel release prior to OSSJ |
| - | * Where will the CIP repo be stored? Gitlab.com? | + | |
| - | * Before End of August | + | |
| - | * Maintainership permission and merge rules for the CIP kernel team | + | |
| - | * ELCE 2018 kernel maintainers meeting? | + | |
| - | * (AI:Yoshi) CIP will have a kernel maintainers meeting at ELCE 2018 | + | |
| - | * (9/3) Jeff is working to book a room for the meeting. | + | |
| - | * L1tf mitigation patches expected for the coming CIP kernel release. | + | |
| - | ==== CIP Testing ==== | + | === Testing === |
| - | * [ACTION]We need a maintainer of the kernelci service. | + | * KernelCI vs Squad |
| - | * Currently there are no CIP administrators for either server. Ideally member companies should do this. One admin? Or multiple admins? | + | * [[https://qa-reports.linaro.org/|https://qa-reports.linaro.org/]] |
| - | * Distributed testing | + | * [[https://github.com/Linaro/squad|https://github.com/Linaro/squad]] |
| - | * KernelCI: [[https://kernelci.ciplatform.org/|https://kernelci.ciplatform.org/]] | + | |
| - | * Lava Master: [[https://lava.ciplatform.org/|https://lava.ciplatform.org/]] | + | |
| - | * Both of the above installations have default content. We need to personalise the servers for CIP. | + | |
| - | * B@D needs to be updated to submit results to KernelCI server. | + | |
| - | * Remote LAVA Labs need to be integrated into the Lava master. | + | |
| - | * For B@D updates please follow the [[https://wiki.linuxfoundation.org/civilinfrastructureplatform/journal|journal]]. | + | |
| + | ==== CIP Testing ==== | ||
| + | * CIP decide to move to centralized environment | ||
| + | * B@D status | ||
| + | * Distributed LAVA server/lab status | ||
| + | * Test case creation/contribution | ||
| + | * Next steps | ||
| + | * Setup KernelCI instance in centralized server | ||
| + | * Put test results to KernelCI | ||
| + | * Does any member already set up LAVA internally? | ||
| + | * Moxa has jenkins/ LAVA testing system internally, Moxa can share it when it’s stable enough. | ||
| + | * | ||
| - | ==== EdgeX/CIP Core ==== | + | ==== Other topics ==== |
| - | + | ||
| - | * Completed: Run Docker with CIP Core plus additional packages from Deby (meta-debian) | + | |
| - | * Next: Try to run EdgeX demo on the filesystem | + | |
| - | * Issue: CIP-core need to have public IP address | + | |
| - | * OOM killer kills services because of low-memory machine | + | |
| - | * | + | |
| - | + | ||
| - | ==== Rolls on GitLab ==== | + | |
| - | * Started to use new roll management (Thanks, Agustin) | + | * SZ |
| - | * TSC representatives from each company will be owners, as well as the tool admin, at group level. | + | * COSCUP & openSUSE.Asia GNOME.Asia |
| - | * We will have no group maintainers by default since we will not have repos at this level but we will enclose them in subgroups. So at this group level we will provide Developer or Reporter roles only to CIP participants. | + | * [[https://2018.coscup.org/|https://2018.coscup.org/]] |
| - | * We assign the maintainer role to those who should have it, because they are responsible of a specific area, at subgroup level. | + | English Page [[https://2018.coscup.org/en|https://2018.coscup.org/en]] |
| - | * Specific people can hold the maintainer role at repo (project) level based on the subgroup maintainer decision. | + | * AI(Yoshi): Send slide PPT file to SZ |
| - | * FYI: Rules for new repository creation or new project launch | + | * # of Attendee: about 1000 |
| + | * OpenChain will attend the conference | ||
civilinfrastructureplatform/tsc-meetings/tsc_mm_jul092018.txt · Last modified: 2018/09/20 15:57 by yoshi
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
