Differences

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

@@ Line 1: / Line 1: @@
+====== CIP Technical Steering Committee F2F Meeting ======
+Date: 11 March, 2018, 1p-5:30p
+Room: Forum Suite on the 3rd floor
+Bridge:
+===== Roll Call =====
+TSC members
+  * Jeff ErnstFriedman (The Linux Foundation)
+  * Hidehiro Kawai (Hitachi) (Representative) (Voting)
+  * Hiroshi Mine (Hitachi)
+  * SZ Lin (MOXA) (Representative)
+  * Masato Minda (Plat’Home) (Representative)
+  * Takehisa Katayama (Renesas) (Voting)
+  * Chris Paterson (Renesas)
+  * Wolfgang Mauerer (Siemens) (Representative) (Voting)
+  * Jan Kiszka (Siemens)
+  * Daniel Wagner (Siemens)
+  * Daniel Sangorrin (Toshiba)
+  * Yoshiyuki Nitta (Toshiba)
+  * Yoshi Kobayashi (Toshiba) (Representative) (Voting) - Chair
+Invited Participant
+  * Tsugikazu Shibata (AGL)
+===== Action items before F2F meeting =====
+  * AI (all): Making a list of packages (core packages)
+===== Proposed topics to be discussed during F2F meeting =====
+  * Kernel version alignment with other projects (LTS/LTSI/AGL/Debian)
+    * 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.
+  * CIP kernel maintenance
+    * SLTS kernel maintenance plan
+    * [[https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance|https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenanc]]
+    *
+  * Security standard for industry (IEC62443-4)
+    *
+  * 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.
+  * 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 =====
+==== 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)
+    *
+==== CIP SLTS kernel maintenance ====
+  * Kernel maintenance
+    * [[https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance|https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance]]
+  * Possible scenarios 2018 in relation with the kernel:
+    * b. Increase the scope (features and hardware support) of 4.4 maintenance and pick another kernel (hopefully LTS + Debian + LTSI + CIP kernel pick the same kernel version) in 2018.
+      * CIP need to ask Ben if feature backports are acceptable by him.
+  * Topics to be discussed in F2F meeting
+    * Q: Who will maintain the current CIP kernel after August?
+      * CIP ask Ben to extend kernel maintenance one more year.
+      * CIP start to develop CIP kernel maintenance team
+    * Q: What will CIP do to make the general alignment towards a single kernel version happen?
+      * CIP try to align with other projects
+      * How can we align kernel version with different projects?
+        * CIP try to pick up kernel from Debian and LTS
+    * Q: Based on available manpower/resources, will we start the maintenance of a new kernel later this 2018 or we simply appoint the kernel and start later on.
+      * At the time Debian start maintain
+  *  Moxa has developers to maintain CIP kernel
+    * Contact to Ben by email cip-dev
+  *
+==== CIP/EdgeX  ====
+  * CIP is an Associate EdgeX Foundry member
+  * Yoshi will forward **best** emails to cip-members
+==== CIP Testing  ====
+  * 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.
+==== 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
+==== 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.
+  *
+==== 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.

Wiki

User Tools

Site Tools

Differences

Page Tools