Skip to content

Latest commit

 

History

History
121 lines (98 loc) · 6.65 KB

ELISA-AeroWG-Meeting-20230216.md

File metadata and controls

121 lines (98 loc) · 6.65 KB
Raw

logo

ELISA Aerospace Working Group

Minutes

16 Feb 2023

Agenda

  • Roll Call
  • Brief Notices
  • Announcements
  • 2023 Goals
  • Prioritize Discussion Topics
  • Closing
    • Next Steps
    • Action Items
    • Round Table

Roll Call

Attended this meeting

  • Steve VanderLeest – Boeing
  • Qasim Majeed
  • Wanja Zaeske - DLR
  • Matt Kelly - Boeing
  • Martin Halle – TUHH
  • Ulises V

Attended in the past

  • Sebastien Boria
  • Sam Bristow
  • Olivier Charrier – Wind River
  • Shuah Khan – Linux Foundation
  • LenkaKT – TUL CZ
  • Sam Thompson – Rapita
  • Richard Wagener
  • Chuck Wolber – Boeing
  • Jeremy York - Boeing

Brief Notices

  • ELISA Project meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal, or foreign antitrust and competition laws.
  • Email communication will be treated as documentation and be received and made available by the Project under the Creative Commons Attribution 4.0 International License. Please refer to the ELISA Technical Charter section 7 subsection iv. for details.
  • The discussions in these meetings are exploratory. The opinions expressed by participants are not necessarily the policy of the companies.
  • No recordings of working group meetings are permitted. Special provisions may be arranged for recording in advance with explicit consent of the participants.
  • The kernel and LF Code of Conduct applies to all communication with this project

Announcements

Upcoming Conferences

2023 Goals

  • Establishing our operations as a new working group
  • Survey on the state of the art within aerospace on use of Linux and associated certification approach and equivalent Design Assurance Level (DAL)
  • Identify the challenges to adopting Linux in aerospace
  • Identify candidate use cases using Linux

Discussion Topics

Rank-ordered discussion topics

  • How to organize our work, our documents, software
    • Workflow - should we use a branch and merge strategy for most members?
    • Assign at least a few people as owner/maintainer to approve merges (perhaps a WG vice-chair)
  • Survey on the state of the art (not only from aero, but from other industries)
    • What would be a collaborative approach? Github wiki? Overleaf?
    • Need to better define the scope of the survey - what should be included or not?
    • How will we split up the effort between authors to avoid duplication of effort?
      • Relate papers to projects, assign one of the survey paper authors to address that collection of work related to the project
      • Define the threshold for determining if someone is listed as an author or simply listed in acknowlgement
    • Outcome: White paper at first, eventually Published paper
  • Needs for compiling documentation (Shuah and Kate, starting with work from Medical Devices WG)
  • What features must be supported? How do de-risk (or even deactivate) those not needed?
  • Achieving high Design Assurance Level (DAL) DO-178C processes
  • Proving real-time performance
  • Aerospace use cases
    • Identify typical architectures and platforms for avionics
    • must clearly articulate expectations in order to make suggestions to other working groups (e.g., tools WG)
    • Candidates
      • PX4 + Linux - PX4 It can be on any Posix OS (including Linux)
      • ARINC653 sim - And there is our ARINC653 simulator using Linux Namespaces + CGroups
  • Tooling
    • What tool needs are unique to Aerospace?
    • Coordinating with Tools WG (not duplicating their work)
  • How to abstract OS behaviors needed for avionics and real-time safety-critical requirements.
    • Can I simulate (early) what I need from an OS and refine requirements.
    • For example, try something in hypervisor or formal language early.
  • Compare/contrast Linux approach to COTS avionics OS offerings
  • Terminology of partitions and ARINC 653 – do we see Linux as the partitioning environment itself or does it become a host OS within a partition?
  • The link between Linux support on top of architecture (especially the newest ones, such as RISC-V)

Closing

Next Steps

  • Organize our ongoing agenda for discussion [mostly done for now]
    • Start collecting literature on state-of-the-art [All]
      • Review recorded presentation on state of real-time Linux
      • Establish list of resources for anyone interested in getting started with Linux in aerospace – the problem and possible solutions

Action Items

  • Invite Stefano Stabellini from AMD to a future meeting for discussion on hypervisor [S. VanderLeest] (consider co-meeting with the system WG)
  • Check how to assign roles for our github [S. VanderLeest]
  • If interested in co-authoring survey, notify Martin Halle ([email protected]) of your interest and email underwhich you would like to register for Overleaf
  • Forward our 2023 goals to TSC [S. VanderLeest]
  • Establish document areas [S. VanderLeest]

Round Table