Differences

This shows you the differences between two versions of the page.

@@ Line 1: / Line 1: @@
+====== CIP Technical Steering Committee F2F Meeting ======
+Date: 19 March, 2018
+===== Roll Call =====
+TSC members
+  * Members
+    * Hidehiro Kawai (Hitachi) (Representative) (Voting)
+    * Takehisa Katayama (Renesas) (Voting)
+    * Yoshi Kobayashi (Toshiba) (Representative) (Voting) - Chair
+    * SZ Lin (MOXA) (Representative)
+    * Jimmy Chen (MOXA)
+    * Wes Huang (MOXA)
+    * Fero Chou (MOXA)
+    * Harry Jhou (MOXA)
+    * Wolfgang Mauerer (Siemens) (Representative) (Voting)
+    * Masato Minda (Plat’Home) (Representative)
+  * Participants
+    * Agustin Benito Bethencourt (Codethink)
+    * Hiroshi Mine (Hitachi)
+    * Yoshiyuki Nitta (Toshiba)
+    * Jeff ErnstFriedman (The Linux Foundation)
+===== Action items from previous F2F meeting =====
+  * AI (Shibata(LTSI)): Coordinate a f2f meeting with Greg Kroah-Hartman at OSS Japan
+  * AI (CIP Testing): Renesas will setup the LAVA slave once the master is setup.
+  * AI (CIP Core)(all): Making a list of packages (core packages) (Due date: 31st March, 2018)
+  * AI (IEC62443): Request members ask business units for what documentation and best practices they can share with the rest of CIP, preferably in English to be shared with CIP.
+  *
+===== Proposed topics to be discussed during F2F meeting =====
+  * Debian contribution plan
+    * Not just funding to person or projects in Debian
+    * What can CIP do for Debian?
+      * Any proposal?
+  * Real-time
+    *
+  * CIP: What’s next?
+    * Yoshi propose an discuss about it.
+  * Chair
+  *
+===== Discussions =====
+==== Report from CIP TSC F2F meeting @ ELC-NA ====
+=== CIP SLTS kernel version alignment with other project ===
+  * Projects to be considering version alignment
+    * LTSI/AGL/Debian
+  * Tsugikazu Shibata from LTSI share his concern
+    * Following the latest LTS is the best way to maintain (Do not cherry pick)
+    * AI - Coordinate a f2f meeting with Greg Kroah-Hartman at OSS Japan
+      * Gauging interest in collaborating on LTS not just between projects but with individual organisations allowing projects, organizations to focus on specific areas of expertise and need.
+  * (Comment) MOXA has engineers, they would like to know how to join the LTS effort. Is there any document?
+    * CIP is very similar to the LTS process, an overwhelming majority of the work is being done upstream.
+    * The best process is to set up an ‘onboarding’ meeting with Ben
+      * (AI) Agustin Benito Bethencourt will try to set up something for the Taiwan timezone on Thursday (3/22) or (3/27)
+=== CIP SLTS kernel maintenance ===
+  * CIP kernel 4.4.120-cip20 released.
+  * Latest Renesas patches under review.
+  * Ben H. trip to DebConf sponsorship approved by CIP.
+  * Talk about CIP kernel paper for OSSJ presented.
+  * Moxa has developers to maintain CIP kernel
+    * Has SZ Lin contacted Ben H. already?
+      * Yes, but I haven't got reply yet
+  * Kernel maintenance
+    * [[https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance|https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance]]
+=== CIP Core packages ===
+  * Define set of packages to support for a 10-year time frame to help establish long term cost estimates.
+  * By end of March each member will define a package name/set and from which version specified by package. If a package is not relevant in terms of the 10 year window do not include it. We should begin to be inclusive at the ** initial review.**
+    * Can get an initial list from Debian packages
+    * Debian LTS comes with restrictions on which packages work with each version
+  * Please send package list to **cip-members**
+**.**
+=== CIP/EdgeX  ===
+  * CIP is an Associate EdgeX Foundry member
+  * Yoshi will forward **best** emails to cip-members
+=== Real-time ===
+  * Discussion with the Stable RT Group. RT Group won’t back port anything from the current mainline unless it contains something that doesn’t touch the core in any sense. The goal is to have all the versions using the same tooling. Will list missing features for old versions - establishing minimum version for features
+=== Reference board ===
+  * Aria10 is able to run with mainline kernel without additional patches
+  * Cyclone-V
+    * About 100 patches need to be added
+    * AI(Hitachi): For CV, need to clarify which features are missing in mainline kernel
+  * For new CIP kernel, each company can propose new boards as reference platform
+    * Same boards for 4.4 are also acceptable
+=== Industrial communication protocol (OPC-UA) ===
+  * Future topic
+=== Update/Upgrade strategy ===
+  * We are focused on super long term support. Consider a strategy for live updates for minor versions. Challenge is the effect of upgrade beyond the kernel. Consider estimates on cost of five 2-year upgrades vs. one 10-year upgrade.
+  *
+=== ARM64 ===
+  * Renesas will release new board in this summer.
+=== Other updates ===
+  * Yoshi nominated himself to serve as TSC Chair for an additional 12 month term to begin 1 APril 2018. The nomination was seconded by Wolfgang. Without objection or additional nominations, Yoshi nomination was approved for TSC Chair for an additional 12 months.
+==== CIP Testing  ====
+  * B@D
+    * Latest CIP kernel tested with B@D (build/boot).
+    * Updated kernelci within B@D
+    * Improvements to ease the network configuration in corporate environments
+    * In progress: Renesas board support.
+      * Zoran also working on this.
+  * Work being done by LF (Ryan Day):
+    * prepare CIP environment in AWS (4 hours)
+AWS creation of a lava and kernelci instance (4 hours)
+install and configure lava via docker (2 hours)
+install and configure kernelci via docker (2 hours)
+DNS configuration for both instances (1 hour)
+  * AI: Ranasas will setup the LAVA slave once the master is setup.
+==== Plans for [[https://events.linuxfoundation.org/events/open-source-summit-japan-2018/|OSS-J]]  ====
+  * Polo shirts for the CIP members ([[https://scalablepress.com/_catalog#?category=Polos|https://scalablepress.com/_catalog#?category=Polos]])
+    *
+  * Demo materials
+    * One-pager with schedules of talks
+    * Swag: Booth takeaways and a Call-To-Action
+      * CTA: Contribute?, Implement?, Upgrade?, Join?
+        * Should focus on one or two
+  * Talks
+    * Agustin : CIP kernel related talk presented.
+    * Yoshi
+    * SZ
+    * Wolfgang

Wiki

User Tools

Site Tools

Differences

Page Tools