KVS Assumptions of Use

KVS AoU		status: valid security: NO safety: ASIL_B
tags: Persistency KVS version: 1 realizes: wp__requirements_comp_aou
doc__kvs_aou		Generic Document

Assumptions of use resulting from KVS FMEA (doc__kvs_fmea) and KVS DFA (doc__kvs_dfa).

Component AoU

File System		status: valid security: NO safety: ASIL_B
tags: Persistency KVS, environment reqtype: Process version: 1 mitigates: comp_saf_fmea__kvs__unflushed_lost
The user shall ensure that the file system and storage used for the KVS directory provide deterministic operations with a bounded execution time (open, read, write, fdatasync, rename, directory creation and file queries) for the maximum storage size and the maximum number of snapshots configured for the KVS instance, that they persist written data once fsync/fdatasync has returned, and keep renamed files consistent across a reset, so that data reported as flushed survives a reset.
aou_req__kvs__filesystem		Assumption of Use Requirement

KVS Limits Configuration		status: valid security: NO safety: ASIL_B
tags: Persistency KVS, environment reqtype: Process version: 1
The user shall configure the maximum storage size and the maximum number of snapshots of each KVS instance, so that the execution time of the KVS operations is bounded.
aou_req__kvs__limits		Assumption of Use Requirement