Versions Compared

Old Version 6

changes.mady.by.user Gunnar Andersson

Saved on

compared with

New Version Current

changes.mady.by.user Gunnar Andersson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Link to repositories, comment on unmaintained projects


Info

November 2021 - the development of these frameworks was halted. Suggestions made to the Bosch developers to consider building on top of existing frameworks such as DAPR, that might provide similar functionality.


Git repositories (unmaintained, see above):  iot-event-analytics, vehicle-edge.

Announcement about this significant open source project creation initiated by Bosch can be found in this blog post

...

Containers overview and quick references

Hal-interface

- this
Container name

Purpose


(warning) These descriptions need to be checked and updated by Bosch

Container image / DockerfileOriginal source code
Hal-interface
Hal-interface-adaptertest-talentpipelinebuilt from 
pipeline/Dockerfile.amd64configmanagerkuksa-valamd64/kuksa
imported from Jenkins build server
e.g. kuksa-val-<hash>-amd64.tar.xz 

mosquitto-remote

mosquitto-local

built from mosquitto/Dockerfile.amd64

platform = ?platform/Dockerfile.amd64vss2ioteabuilt from vss2iotea/Dockerfile.amd64ContainerPurpose
This typically collects signals from a low level vehicle-specific signal source such as CAN bus.  For each technology, a different hal interface can be provided.

Hal-interface-adapter
 – this

This implements the necessary translation from the specific signal interface to the standard one used in this framework (VSS).   

(In CCS terms these have been referred to as "vss-feeder" components, something that feeds the system with VSS formatted data, from some source, that might not be VSS formatted, i.e. a translation occurs)



test-talent
 – shows

Shows an example of a "talent" i.e. a cooperating agent in the system.  A talent is....



pipeline
 – ... main

Main component of IOT-event-analytics? - details TBD 

ConfigManager

built from pipeline/Dockerfile.amd64
configmanager

Setting

 – ... setting

up the system together with pipelines? - details TBD  Written in

Kuksa.VAL



kuksa-val

Keeps

keeps are

the current value store and sits between VSS2IOtea and the hardware-specific parts.  Kuksa.VAL exposes data using the VISS protocol (v1, websocket) , but also provides other protocols like MQTT.

Mosquitto-local and -remote


amd64/kuksa
imported from Jenkins build server
e.g. kuksa-val-<hash>-amd64.tar.xz 

mosquitto-remote

mosquitto-local

MQTT brokers (well-known implementation and not unique to this project).

built from mosquitto/Dockerfile.amd64

VSS2IoTea


platform = ?

Only

 – only

an adapter between VISS and IoTea. 

built from platform/Dockerfile.amd64
vss2iotea
built from kuksa.val2iotea/Dockerfile.amd64 (question)




Software Components (not always 1-to-1 mapped to a container)

...