Introducción a la iniciativa de la Linux Foundation llamada Civil Infrastructure Platform CIP. Descripción del problema que pretende resolver este grupo y sus primeros pasos Transparencias de la charla impartida en el OpenSOuthCode de Málaga, España.

1. Systems Software Experts
www.codethink.co.uk

2. Primeros pasos del Software
Libre en infraestructura civil
Civil Infrastructure Platform (CIP), a Linux Foundation
Initiative.
Agustín Benito Bethencourt
Principal Consultant - Codethink Ltd
OpenSouthCode, Málaga, ES, 2 de Junio de 2018
CC BY-SA

3. About Codethink

4. About Codethink
● Founded 2007 as an expert provider of Open Source, Linux and
embedded software services.
● Headquartered in Manchester, UK.
● 90+ staff, mostly systems software engineers and technical
consultants.
● Supporting 10 customers today - including global brands in
automotive, finance, medical devices, consumer electronics,
semiconductors.
● Owner-managed, independent, unbiased and ethical.

5. ● We deliver in reliable, transparent, honest relationships.
● We provide high-calibre people, and continuity.
● We are experts in Open Source and embedded software.
● We can slot into existing projects, adopt existing procedures.
● We handover all IP and documentation.
● You can stand us down if demand reduces.
Services Value Metrics

6. ● Founded by FOSS engineers.
● Long and successful track record in creating, supporting and
exploiting Open Source initiatives.
● Our people have been heavily involved in the development and
integration of FOSS components e.g. within Ubuntu, Debian,
GNOME, KDE, the Linux Kernel, etc.
● Support corporate customers in making the most of FOSS.
● Affiliated to OIN, GENIVI, The Linux Foundation (CIP and AGL).
Open Source experts

7. ● Scale Microcontrollers to servers
Operating systems
System components
Software tooling
● Technologies Linux, Android, RTOS, bare-metal
Qt, GTK+, Wayland, WebKit, GStreamer, OpenStack, OpenGL
C, Python, Assembly, C++, C#, Java, Haskell, Lua, Ruby
● Specialist skills Graphics
Speech recognition
Augmented reality
Algorithm optimisation
Signal processing
Virtualisation and containerisation
Systems Software Engineering

8. ● Open Source Integration with proprietary technology
Licensing
Upstreaming
Long-term maintenance strategy
● Process and Tooling Continuous delivery
Build and integration pipelines
Chain of custody from design to delivery
Automation
Metrics
● Technical architecture and system design review
Consultancy Services

9. R&D
● BuildStream - framework for modelling build and CI pipelines.
● MUSTARD - FOSS requirements and architecture tracking tool.
● Trustable Software - forum for the discussion and development of
software for safety and security critical applications.
● Baserock - tooling for traceable, reproducible building of software
systems.

10. Why Codethink?
Open Source company.
+
Embedded experience.
+
Passionate about developing, delivering and maintaining
complex Linux systems.

11. About the speaker

12. The speaker: @toscalix
● Principal Consultant at Codethink Ltd
● Experienced working in the open and managing the development,
delivery and maintenance of complex Linux based systems.
● Contributor in several FOSS communities (KDE, openSUSE…).
● Agustín represents Codethink Ltd at CIP.
● More about Agustín at his professional site.

13. Let’s start!

14. Session structure
1. About CIP: 5 minutes.
2. CIP problem statement:10 minutes.
3. CIP Activities: 10 minutes
4. The future: 5 minutes
5. Takeaways: 5 minutes
6. Q&A: 10 minutes
Total: 45 minutes

15. About CIP

16. About CIP
● Linux FoundationTM
Initiative formed in 2016 by Hitachi, Siemens,
Toshiba, Codethink and Plat’Home.
● Open Source project with code first approach.
● Governance: Board of Directors and TSC.
● For further information, check the Links slide.

17. Provide a super long-term maintained industrial-grade
embedded Linux platform.
Platinum Members
Silver Members

18. CIP goals: the initiative
● Create an industrial grade Linux based Open Source system.
● Maintain that system for a very long time.
● Open collaboration within the industry and with other
organizations.
● Promote Open Source best practices adoption within CIP
Members.

19. CIP goals: Codethink
● Exposure: show capabilities.
● Challenge ourselves as engineers and as an organization.
● Make an impact in the Open Source space.
● Support the Linux Foundation goals and activities.
● More about Codethink motivations in these articles [1] [2]

20. CIP problem statement

21. Product maintenance strategies
Open Source based systems delivery + maintenance models:
● Fire and forget: product release and no software maintenance.
● LTS approach: product release and time boxed service packs
including at least bug and security fixes.
● Rolling model: frequent updates. Stay as close as possible to
upstream.

22. Product maintenance strategies
CIP chose as initial strategy the one that is expected to better match
Members business requirements in the coming years: LTS approach.

23. Maintenance in the Linux
world

24. CIP: Railway Control System
● 3 – 5 years development time.
● 2 – 4 years customer specific extensions.
● 1 year initial safety certifications / authorization.
● 3 – 6 months safety certifications / authorization for follow-up
releases (depending on amount of changes).
● 25 – 50 years product lifetime.

25. CIP: Power Plant Control System
● 3 – 5 years development time.
● 0.5 – 4 years customer specific extensions.
● 6 - 8 years supply time.
● 15 years hardware maintenance after latest shipment.
● 20 – 60 years product lifetime.

26. CIP vs other industries
3 to 4 times
longer

27. CIP challenge
● Can the LTS approach be extended? Super Long Term Support
(SLTS).
● Would it be possible create SLTS to SLTS transitions?

28. CIP Activities

29. Linux kernel maintenance
● Define a kernel maintenance strategy and process.
● Select a first kernel: v4.4 stable.
● Designate an initial kernel maintainer: Ben Hutchings, Codethink.
● Define maintenance policies. Collaborate upstream.
● Members kernel configurations analysis: done in the open.
● Patch review and kernel releases.

30. stable-rt kernel maintenance
● Define a -rt kernel maintenance strategy and process.
● Select a first -rt kernel maintainer (Daniel Wagner, Siemens).
● Collaborate upstream. Daniel Wagner designated as official
4.4-rt maintainer by the RTL project.
● Patch review upstream.
● Kernel releases based on CIP kernel releases.

31. Kernel testing
● Define a testing strategy: fully decentralised approach.
● Create a tool based on kernelci (B@D).
● Strategy changed: now semi-decentralised approach.
○ LF hosts a kernelci based service. Setup in progress.
○ B@D moves into maintenance mode.
● Collaboration around testing among CIP developers.

32. CIP Core
● Debian as reference sources and distro.
● Collaboration with the Debian project: DebConf sponsoring and
Debian LTS (under discussion).
● CIP Core first implementation based on Deby: Debian sources +
meta-debian + Bitbake + tested with Fuego.

33. Collaboration
● Mentoring engineers to participate in the Linux Kernel stable
review process.
● Sponsorship and Membership.
○ Linux Foundation events: ELC, ELCE and OSSJ. DebConf
2017/2018.
○ EdgeX Foundry associate member. RTL project Gold Member.

34. Other activities
● Y2038 and IEC62443-4 analysis.
● Promotion: talks, demos/booths at events.
● Reference platforms: BBB, Renesas IWG20M and Cyclone V.

35. The future

36. The future
● New blog post summarising Codethink activity within CIP.
● OSSJ 2018 sponsor. Booth with demos + 2 talks.
● New Member announcement.
● CIP testing infrastructure setup.
● Collaboration with AGL and kernelci.org on testing.

37. The future
● Agreement with Debian LTS. Debian sources selection.
● DebConf 2018 sponsorship and participation.
● ELCE 2018 sponsor. Booth + demos.
● Selection of the second CIP kernel around the end of 2018.
○ Towards CIP kernel = LTS kernel = Debian LTS kernel.

38. Takeaways

39. Takeaways
● There’s been Open Source in civil infrastructures for a long time.
● CIP tries to boost adoption but also contributions... the Open
Source way.
● There are outstanding challenges ahead of us. Is the SLTS a valid
approach?
● CIP is working on the basics, at a slow but steady pace.

40. Takeaways
CIP is one of the most conservative Open Source projects you can
find so probably one of the most boring too.

41. Takeaways
At the same time, those involved like to think that CIP might become
one of the most important software projects for our civilization. ☺

42. Thank you
Agustín Benito Bethencourt
@toscalix

43. Q&A

44. Systems Software Experts

45. Further content

46. ● CIP website.
● CIP whilepaper (2017).
● CIP wiki.
● CIP blog.
● cip-dev mailing list.
Links
● #cip at irc.freenode.net
● CIP v4.4 kernel.
● CIP v4.4-rt kernel.
● Board at Desk: B@D.
● CIP Core.

47. ● This presentation is license under the Creative Commons
Attribution-ShareAlike 4.0 International license: CC BY-SA.
● The license does not apply to Trademark affected content like:
○ Codethink:
○ Check the Linux Foundation TM
trademark policy.
○ CIP Member and third party organizations commercial brands.
© Codethink 2018
License