(WIP) WAII VISS: Add Apache IoTDB database to supported State Storage backends

[slawr]

Summary

Currently WAII supports the SQLite and Redis databases as State Storage backends. Extend WAII to support Apache IoTDB database as well.

As we are using a git submodule for the WAII VISS Data Server sources and the changes are not yet upstreamed we must point to a fork that carries the changes. Marking this as a WIP to see if it can be upstreamed before merge which would avoid the upstream CDSP project having to change submodule git reps. Of course anyone wanting to try the code can checkout my PR and build it.

Detail

Development environment:

• Apache IoTDB v1.2.2
• Apache IoTDB Go Client v1.1.7

Runtime assumptions:

• IoTDB server lifetime (e.g. startup and shutdown) is handled externally to WAII
• Management (e.g. creation/deletion) of the IoTDB timeseries containing VSS nodes is handled externally to WAII.
• Connection config is currently a build time setting in the Service Manager header. Runtime configuration will be added in a later commit. Runtime configuration is now supported via iotdb-config.json.

Sanity testing

Sanity testing was carried out within a Docker deployment of the COVESA Central Data Service Playground:

1. Create timeseries within database containing VSS nodes and populate some date.

IoTDB> show timeseries
+-------------------------------------------------------------+-----+---------------+--------+--------+-----------+----+----------+--------+------------------+--------+
|                                                   Timeseries|Alias|       Database|DataType|Encoding|Compression|Tags|Attributes|Deadband|DeadbandParameters|ViewType|
+-------------------------------------------------------------+-----+---------------+--------+--------+-----------+----+----------+--------+------------------+--------+
|          root.test2.dev1.`Vehicle.CurrentLocation.Longitude`| null|root.test2.dev1|   FLOAT|   PLAIN|     SNAPPY|null|      null|    null|              null|    BASE|
|           root.test2.dev1.`Vehicle.CurrentLocation.Latitude`| null|root.test2.dev1|   FLOAT|   PLAIN|     SNAPPY|null|      null|    null|              null|    BASE|
|root.test2.dev1.`Vehicle.Cabin.Infotainment.HMI.DistanceUnit`| null|root.test2.dev1|    TEXT|   PLAIN|     SNAPPY|null|      null|    null|              null|    BASE|
+-------------------------------------------------------------+-----+---------------+--------+--------+-----------+----+----------+--------+------------------+--------+

2. Using WAII HTML client connect to WAII and 'get' VSS node Vehicle.CurrentLocation.Longitude
3. Using WAII HTML client connect to WAII and 'set' VSS node Vehicle.Cabin.Infotainment.HMI.DistanceUnit
4. Check HTML client reports success and values set/returned match the data in the database.
   

Setup

If you wish to try it then using the default configuration WAII makes the following runtime assumptions when accessing the DB:

1. Your database is root.test2.dev1
2. That a timeseries exists in the DB with the VSS nodes you want to work with.

Both are easy to create in the DB cli:

1. With the Playground docker deployment running (see playground docker readme for instructions) connect to the DB CLI from your host:
   $ sudo docker exec -ti iotdb-service /iotdb/sbin/start-cli.sh -h iotdb-service
2. Create database from CLI command line:
   IoTDB > create database root.test2.dev1
3. Create timeseries from CLI command line:

IoTDB > CREATE ALIGNED TIMESERIES root.test2.dev1(`Vehicle.CurrentLocation.Longitude` FLOAT, `Vehicle.CurrentLocation.Latitude` FLOAT, `Vehicle.Cabin.Infotainment.HMI.DistanceUnit` TEXT)

4 Add some data into the timeseries:

IoTDB> insert into root.test2.dev1(`Vehicle.CurrentLocation.Longitude`, `Vehicle.CurrentLocation.Latitude`, `Vehicle.Cabin.Infotainment.HMI.DistanceUnit`) values(-42.4567, 22.1234, "MILES")

[slawr]

Updated PR to include support for configuring the Apache IoTDB connector via a config file. See commit 1ef2fef for details

[UlfBj]

WAII is now VISSR
https://github.com/COVESA/vissr

[slawr]

Closing pull request as the changes contained here have now been merged upstream in the VISSR project and the playground was rebased to use those changes in PR #30 which has now been merged.