# *************************************************************************** # Copyright (c) 2025 Contributors to the Eclipse Foundation # # See the NOTICE file(s) distributed with this work for additional # information regarding copyright ownership. # # This program and the accompanying materials are made available under the # terms of the Apache License Version 2.0 which is available at # https://www.apache.org/licenses/LICENSE-2.0 # # SPDX-License-Identifier: Apache-2.0 # ***************************************************************************

Requirements#

Workload Lifecycle Management#

Standard Container Command Set
status: valid
security: YES
safety: ASIL_B
reqtype: Functional

The orchestrator shall support seven essential workload commands: create, start, pause, resume, stop, restart, and delete. All commands shall be delivered via remote procedure calls and follow a standardized response format.

Container State Model
status: valid
security: YES
safety: ASIL_B
reqtype: Functional

The system shall manage containers across five main states: Created, Running, Paused, Exited, and Restarting. State transitions shall follow strict rules and be tracked by the StateManager component.

Scenario-Based Automation#

Conditional Execution Engine
status: valid
security: YES
safety: ASIL_B
reqtype: Functional

The orchestrator shall automatically control services based on changes in vehicle state. Scenario information shall be retrieved from a distributed key-value store, and corresponding actions shall be executed automatically when conditions are met.

Resource Management and Isolation#

Container Security Isolation
status: valid
security: YES
safety: ASIL_B

User identifiers, group permissions, and Linux capabilities are strictly controlled according to the principle of least privilege. Restricting privileged mode and applying security contexts strengthens system-level protection.

Performance Optimization
status: valid
security: YES
safety: ASIL_B
reqtype: Functional

Processor and memory usage are tracked in real time, allowing early detection of resource shortages. Parallel container creation, asynchronous processing, and automatic scaling optimize startup times and maximize efficiency.

Monitoring and Recovery#

State Monitoring
status: valid
security: YES
safety: ASIL_B
reqtype: Functional

Comprehensive health checks continuously monitor process status, port connectivity, and application-level health. Changes in status are detected immediately, ensuring consistency across the entire system.

Automatic Recovery Mechanisms
status: valid
security: YES
safety: ASIL_B

Failure recovery is automated according to restart policies. Failed containers are automatically restarted, and state-based corrective actions minimize operational downtime. Customized recovery logic is applied depending on the error type.