Requirements#
Lifecycle Requirements
|
status: valid
security: YES
safety: ASIL_B
|
||||
Launching Processes#
Support for launching processes
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall provide support for launching Processes. |
|||||
Process dependency handling
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall provide support for ordering the launching of Processes based on the dependencies. |
|||||
Launching processes in parallel
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall provide support for launching Processes in parallel. |
|||||
Control interface support
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall provide support to wait for configurable custom conditions, which can be signaled from applications via Control Interface. |
|||||
Conditional Launching#
Conditional launching
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall provide launching processes based on conditions. |
|||||
Process Management#
Process adoption
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall be able to control already running Processes. |
|||||
OCI Compliant
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall be compliant to the OCI Specification v1.2.0. |
|||||
Run targets#
Run target support
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall provide support for run targets to define collections of Processes that can be launched together. |
|||||
Launching run target
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall be able to start a named Run target. |
|||||
Switch between run targets
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall be able to switch between different run targets. |
|||||
Terminating Processes#
Terminating process
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall provide support for terminating Processes. |
|||||
Handling process dependency in termination
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall terminate the Processes based on the dependency order. |
|||||
Control Interface#
Control commands
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall provide support for run-target selection. |
|||||
Query commands
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall provide support for commands to query component states. |
|||||
Report "started/running/degraded"
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall be able to report status on components via the Control Interface. Note: status can be “started/running/degraded” - refer to documentation for details |
|||||
Request run target launch
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall be able to start a named Run target respecting the dependencies when requested. |
|||||
Monitoring, Notification and Recovery#
Process crash monitoring
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall provide support for monitoring abnormal termination of Processes. |
|||||
Recovery action
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall support Recovery Action for the abnormally terminated Processes. |
|||||
Run target switch as recovery action
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall support switching to a different Run target as recovery action in case a single process terminated abnormally or lost its Liveliness. |
|||||
Monitoring and recovery: watchdog support
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall support a smart Watchdog, configurable per process. |
|||||
Process liveliness detection
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall be able to detect and react to loss of Liveliness of the Processes it owns, by monitoring the state of the Processes as specified by the set of executables. |
|||||
Multi-instance
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall be able to run in multiple instances with its own configurations on a system. |
|||||
Launch manager self health check
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall implement time based cyclical monitoring of itself. |
|||||
Lifecycle programing language support
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall support Rust and C++ programming languages. |
|||||
Health Monitor deadline supervision
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall support deadline supervision to allow monitoring timely execution within applications to detect timing violations. |
|||||
Health Monitor logical supervision
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall support logical supervision to allow monitoring execution flow within applications to detect logical errors. |
|||||
Health Monitor checkpoint supervision
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall support checkpoint supervision to allow monitoring periodic execution within applications to detect failures. |
|||||
Logging#
Logging support
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall support logging of process launch, monitoring, and configuration activities. |
|||||
Configuration file#
Configuration file support
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall support modular configuration files to configure process attributes, including configurations coming from external formats such as OCI runtime configuration. |
|||||
Updating configuration
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall provide support for extending already running session with additional new configuration file. |
|||||
Component grouping configuration
|
status: valid
security: NO
safety: ASIL_B
|
||||
The Lifecycle Feature shall provide support for grouping sets of Components to share configuration. |
|||||
Configuration Dependency view
|
status: valid
security: NO
safety: QM
|
||||
The Lifecycle Feature shall have the means to generate the specified dependencies in a format that can be visualized. |
|||||