1 of 9

Management Plane in SDV

Haishi Bai

COPYRIGHT (C) 2023, ECLIPSE FOUNDATION. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)

THANK YOU!

COPYRIGHT (C) 2023, ECLIPSE FOUNDATION. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)

​

1

1

1

COPYRIGHT (C) 2023, ECLIPSE FOUNDATION. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)

​

2 of 9

SDV compute environment

  • Heterogenous, distributed environment
  • Various OS
  • Various hardware
  • Cloud and mobile phones
  • Various application formats, capabilities and constraints
  • Various communication protocols
  • Various safety zones

3 of 9

Three planes

​

Networking

Cloud

K8s

Management Plane

Manage and monitor networked devices and their configurations

Manage and monitor cloud resources

API Server, etcd, controller manager, scheduler etc.

Control Plane

Make routing and forwarding decisions

Orchestrate cloud resources to support various workloads

Data Plane

Where the actual data flows

Compute and storage resources

Container runtime, Kubelet, Kube-proxy, service proxy, etc.

4 of 9

Why Kubernetes (or not)?

Benefit

Single Node

Multi-Node

Single Fault Domain

Multi-Node

Multiple Fault Domains

Reality

High Availability

​

​

​

Resource constraints

Restart

Yes

Yes

Yes

​

Redundancy

Limited

Limited

Yes

​

Failover

No

No

Yes

​

Workload Elasticity

Limited

Yes

Yes

Predicable Workloads

Resource load balancing

No

Yes

Yes

Strong affinity

DevOps

Yes

Yes

Yes

Complexity of maintaining the cluster itself

5 of 9

What else is needed?

  • Payload formats other than OCI containers
  • Non TCP/IP network
  • Constrained devices
  • Fleet management
  • Cloud services

6 of 9

Characteristics

  • Technology Neutral
  • Adaptive
  • Extensible
  • Kubernetes native and standalone
  • Cloud-connected and autonomous
  • End-to-end observability
  • Secured and compliant
  • Low TCO

​

​

7 of 9

Technology-agnostic Abstractions

  • Microservices
    • List/graph of components
  • State Seeking
    • OS/firmware update
    • Runtime update
    • Payload deployment/management
    • Configuration
    • Policy
  • Virtualization
    • Virtualized infrastructure
    • Workload isolation

​

8 of 9

Modeling challenge

Flexibility

Complexity

templates

PaaS native features

PaaS

SaaC with templating

SaaC

primitives

Knowledge

Gap

9 of 9

9

THANK YOU!

COPYRIGHT (C) 2023, ECLIPSE FOUNDATION. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)

​

9

9