ASAP - Shift to SDV

The ASAP shift to SDV project consists of 3 new Ankaios workloads and a webserver component to interact with via MQTT. The workloads fulfill the following use-cases:

1. fleet_manager: Applies manifests .yaml files, that it receives via MQTT to the Ankaios instance e.g. to start new workloads.
2. vehicle_state_log: Retrieves eCal information about the vehicles' dynamics, enriches the information with Ankaios execution state logs and publishes them to the MQTT broker
3. speed_limit_assist: The speed_limit_assist provides new functionality to the Ankaios runtime, evaluating whether the maximum speed is exceeded, and logs violations to the info log.

To orchestrate the workloads, we implemented a simple webserver. A user can upload a manifest .yaml file through the web UI. Simultaneously, while eCal is providing data, the UI displays the vehicle information and Ankaios execution state.

How to get this to run

1. start dev container
2. in separate terminal instances inside your devcontainer, run the following:
   1. restart-shift2sdv
   2. cd webserver && python3 manage.py runserver
   3. ecal_play -m measurements/2024-11-19_15-45-14.870_measurement/
      1. or wherever you have demo measurement data to play with eCal..
3. Open the webserver on localhost:8000

Running a local Mosquitto instance

When running on a local MQTT Broker (instead of ours hosted on Azure), run mosquitto from inside the dev container.

To reference the local broker, edit the "MQTT_BROKER_ADDR" env var inside the shift2sdv_manifest.yml as well as in "webserver/ankaios_deploy_manager/settings.py" to point to localhost instead.

Technologies used

• Ankaios
• eCal
• Mosquitto
• MQTT Protocol
• Podman
• Django
• Azure Cloud

Architecture