Persistency CFT [2025-05-15, 2:30 - 4:00 pm]

[guysagnes]

Agenda

Change of Cross Functional Team (CFT) to Functional Team (FT)

Participants:

• @guysagnes
• @joshualicht
• @bogdan Badicu
• @sbachmann-qorix
• @arsibo

Meeting reports

Cross CFT

File system feature priority
Missing statement of use spec. QNX.
-> initial implementation inside Communication to be aligned between CFT. (Ulirch Huber / Guy Sagnes)

Dependency
C++ Class Result dependency to common/base libs. Planned 2025.cw20 (BMW)
-> https://github.com/eclipse-score/baselibs/tree/main/score/result

Architecture

Address security definition / abstraction -
How to handle the security configuration related to ACL / SePol - Linux and SecPol under QNX?

Workpackages

Open Pull request
KVS Feature / Requirements
Feature: Persistency KVS - Feature Requirements
Feature: Persistency KVS - Feature Architecture
Feature: Persistency KVS - Component Requirements

Merged content

Architecture / Design

• Improvement: Adaptation of the open / build for KVS to allow process separation #1071

Open actions

• Requirement related safety qualification level (QM / ASIL_B) started @sbachmann-qorix (Pilot)

Meeting Minutes

Related Persistency CFT Board:
Persistency FT

Feature Request for Persistency · Issue #95 · eclipse-score/score

Focus:

• Walkthrough Requirements: https://eclipse-score.github.io/score/pr-1067/features/persistency/index.html
• => Walkthrough Architecture: https://eclipse-score.github.io/score/pr-1068/features/persistency/kvs/architecture/feature_architecture.html
• => Walkthrough Component: https://eclipse-score.github.io/score/pr-1069/features/persistency/kvs/requirements/index.html

Reference:

• requirements_inspection_checklist
• equirements_templates

[joshualicht]

Adding the following topic to the Agenda:

• Decision on the CPP implementation approach
• Initial (provisional) CPP Wrapper over Rust implemented (PoC) -> PR#11
  –> Findings and issues related to this approach need to be discussed

Presentation of the initial wrapper

Overview about the realization

Implementation separated in the different folder under sources (src)
src
+- kvs_rust
+- kvs_rust_ffi
+- kvs_cpp

Summary

• Proposed C++ api meets the expectation vs. Rust available API

• Presented function reset() and get_all_keys() and get_default_value()

• Additional memory allocation requested to allow conversion and handover of the ownership of memory

• Approach based on the box

• The responsibility to manage the allocation / deallocation of the memory has to be done controlled in the same context

• The transformation from Rust to C++ is handle over C generated converter header.

• Additional Classes:

  • Key-Class requested to allow handling of the deallocation during destruction of the class.
  • Filename-Class created with the same reason

• Remarks: Copy function from KVS Class disactivated, Mutex access managed on Rust level.

• Presented function Kvs::open()

Finalization of the example_usagemain.cpp implementation

Downsize of the wrapper implementation

• dynamic allocation
• no reuse of the strings from Rust in C++
• for complex data type 2 copies of the data is requested
• Additional helper classes

Benefit check the API Rust verified

Decision

We will go with separate and specific compatible C++ implementation additional to the Rust module deployment