Skip to content

Glossary

Words used in the context of veHaaS are described here.

Cluster Partition

A named subdivision of a Cluster scoped to a specific Organization. A Cluster can be split into multiple partitions, each with a defined number of slots (Assemblies) and assigned to a different organization. Partitions allow a single physical rack to serve multiple organizations independently.

Device Sequence

An ordered list of device operations (such as power cycling, relay switching, or HAI state changes) saved against an Assembly. Sequences can be triggered manually from the UI or via the API to automate repetitive hardware interactions.

Jumper

A physical short-circuit connector on a relay card that routes a HAIGen2 channel to a specific device or signal (e.g. 5V, GND, or open line). Jumpers allow the physical wiring of an Assembly to be reconfigured without hardware disassembly. See Relay Card and Jumpers.

ReBAC: Relationship-Based Access Control

The authorization model used by veHaaS to determine what a user can access. Permissions are derived from the relationships between users, groups, organizations, and resources (assemblies, tokens, clusters) — rather than from static role lists. veHaaS implements ReBAC using OpenFGA.

Session Context

The state established when a user's reservation becomes active on an Assembly. The session context includes the user's VM access credentials, environment paths, and device ownership. It is initialized at session start and cleaned up when the session ends or is transferred.

Assembly

german: Entwicklungsaufbau,

Self-contained development system in veHaaS. It's a bundle of different hardware devices that are connected.

An Assembly consists at least of:

  • EvalBoard and Debugger
  • Optional devices:
    • Network interface (VNxx, VTxx, VIO, ...)
    • Measurement equipment
    • HAIs

Assemblies are modeled for automation via a JSON data description.

veHaaS: Vector embedded Hardware as a Service

veHaaS is the product name for a scalable managed customer service for embedded hardware access, tests, feature development and sharing. (Also supports MCAL, MCTs) Reachable via webservice: <https://vehaas.vi.vector.int>__

  • The customer shall be able to automate embedded hardware tests with the GitLab CI.
  • The customer shall be able to interact and test directly on embedded hardware.

Assembly Request Profile: The allocation request input data

It's used to define a filtered Assembly allocation request. For example, the Assembly that is needed must provide the debugger type isystem.

Assembly Profile: The modeling of one Assembly

The description of the model is text based with json.

Cluster: Rack

It's a rack with network connection, server connection and central PowerSupply Unit to provide a range of Assemblies.

HAI: Hardware Automation Interface

HAIs are used as part of an Assembly to switch remote devices on or off.

Proxy: veHaaS WebService

The main task of the proxy is the Assembly resource management and Assembly device control management. It provides a lot of features to support these tasks. The data model for the Assembly Profile is strongly integrated into the service itself.

vAS: veHaaS Application Service

The veHaaS application service is provided by CT Cerberus. The team is responsible for: * Development and operation of the veHaaS webservice * Design and maintain the assembly datamodel

vCS: veHaaS Cluster Service

The Cluster Service is provided by CTs vFit and HWcoord. The team is responsible for: veHaaS Cluster, Assemblies Development and Operation.

vEE: veHaaS Execution Environment

The Execution Environment is provided by CT CT62 (DOS). The team is responsible for: VM and Development Environment