Aerospace, Military and Defence
Why don’t airborne systems use containers and Kubernetes?
By Chip Downing, senior market development director, aerospace & defence, Real-Time Innovations, Inc. L
ife would be a lot easier if we simply could travel down the path of least resistance. However, when creating highly competitive safety- critical avionics systems, this is not possible. The rigor of designing, developing and deploying with certified conformance to the RTCA DO-178C safety standard drives manufacturers down a path of high discipline, high investment and high commitment to achieve airworthiness. In today’s commercial and military systems, this rigor is non-stop when it comes to creating highly compelling solutions that provide distinct competitive advantages over both fellow suppliers and military adversaries.
These solutions need to be deployed in a wide range of trusted compute environments. A fairly recent innovation, containers are lightweight packages of application code coupled together with application dependencies, such as programming language runtimes and the operating system libraries required to run software services in enterprise or cloud environments. Containers share CPU, memory, storage and network resources at the operating systems level and offer a logical packaging mechanism where applications are abstracted from the environment in which they execute. Containers enable productivity by maximizing application compatibility to deployed operating system environments, while resulting in the fewest sacrifices in terms of performance and security properties. Container technology continues to evolve and mature, and provides the following four advantages: 1. Application isolation. Containers virtualize CPU, memory, storage, and network resources at the operating system level, providing developers with a view of the OS logically isolated from other applications. Whether deployed on hypervisors or natively on operating systems, containers maintain the property of isolation, where the container-deployed applications inherently have a strong level of independence between the host operating system and other containers deployed on the same compute platform. 2. Application / workload portability.
14 July/August 2023
the CNCF; containerd is the core container runtime of the Docker Engine.
Containers can run virtually anywhere, on any operating system, including Linux, Windows, and Mac operating systems. Containers exist on most enterprise computer environments, including virtual machines or on physical servers, from developer workstations to on- premises servers to cloud platforms. 3. Separation of responsibility. Containerization provides a clear separation of responsibility, as developers focus on application logic and dependencies, while IT operations teams can focus on deployment and management instead of application details such as specific software versions and configurations. 4. Manageability. The Open Container Initiative (OCI) community, an open governance structure for creating open industry standards around container formats and runtimes, has established a framework around the process of developing, testing, integrating, maintaining and fielding software components and APIs. In a DevOPs environment, containers can be viewed as a standard unit of “work”, where the work will vary as the container’s role transitions throughout the major lifecycle phase.
Containers in enterprise and mission systems
Containers are not virtual machines (VMs). Containers are much more lightweight than VMs, because containers virtualize at the OS level, while VMs virtualize at the hardware level. VMs are typically managed by a VM monitor, also known as a hypervisor, that creates and runs virtual machines (VMs), allowing host computers to support multiple guest VMs by virtually sharing their resources, such as memory and processing. How does one manage the deployment
Components in Electronics
www.cieonline.co.uk.uk
of containers? Today, most organisations use Kubernetes, an open-source container orchestration system, for dynamically automating software deployment, scaling, and management of containerized applications. The name Kubernetes originates from Greek, meaning helmsman or pilot. Kubernetes is often abbreviated as K8s, counting the eight letters between the “K” and the “s”, but either term is pronounced “coo-be-net-ees”. Google open-sourced the Kubernetes project in 2014 and the project is now maintained by the Cloud Native Computing Foundation (CNFC), which is part of the Linux Foundation.
What about Docker?
Docker is a commercial implementation of containers that is now supporting open source efforts for open standards for container technology. In June 2015, Docker donated the container image specification and runtime code now known as runc, to the Open Container Initiative (OCI) to help establish standardization as the container ecosystem grows and matures. Furthermore, in 2017, Docker donated the containerd project to
Airborne containers Containers dynamically managed by Kubernetes can also run in airborne systems. The best fit for these environments is “back of the airplane” mission systems that do not have strict real-time performance, high security demands, and/or high levels of RTCA DO-178C safety certification requirements. In many cases these mission systems run on enterprise, non-rugged hardware. Airborne systems also use container concepts in embedded edge devices in ruggedized airborne platforms that have more strict real-time requirements. Most of these systems are flight or mission critical systems that must support multiple levels of safety and security, requiring the development and deployment rigor to be much higher than enterprise compute systems.
Safety-critical containers/partitions In this embedded edge airborne environment, containers are called partitions, and they strictly follow an open avionics standard titled ARINC 653, that is proven in well over 100 different commercial and military aircraft types, including the helicopters from Airbus, Bell, Boeing, and Lockheed Martin Sikorsky, and commercial fixed wing aircraft from Airbus, Boeing, Embraer and more. These aircraft have a robust ecosystem of Tier 1 platform suppliers including Collins Aerospace, Elbit Systems, GE Aerospace,
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66
