Hololens Adapter

This is a simple Consumer for the Messaging Bus's data that pipes the messages to a websocket.

The Hololens Adapter is based on the components:

• Kafka Client librdkafka version 0.11.1
• Node Red Graphical programming framework node-red

Contents

1. Requirements
2. Deployment
3. Configuration
4. Trouble-Shooting

Requirements

1. Install Docker version 1.10.0+
2. Install Docker Compose version 1.6.0+
3. Clone this repository

Deployment

Testing

Using docker-compose:

git clone https://github.com/iot-salzburg/dtz_hololens-adapter.git
cd dtz_hololens-adapter
sudo docker-compose up --build -d

The flag -d stands for running it in background (detached mode):

Watch the logs with:

sudo docker-compose logs -f

Deployment in a docker swarm

Using docker stack:

If not already done, add a regitry instance to register the image

sudo docker service create --name registry --publish published=5001,target=5000 registry:2
curl 127.0.0.1:5001/v2/

This should output {}:

If running with docker-compose works, the stack will start by running:

git clone https://github.com/iot-salzburg/dtz_hololens-adapter.git
cd dtz_hololens-adapter
chmod +x st* sh*
./start-adapter.sh

Watch if everything worked fine with:

./show-adapter.sh
docker service logs -f hololens_adapter

The service will be available under hostname:1880/

Configuration

The flows are stored on the samba share il060 which can be defined in the docker-compose.yml. They can be modified in the node-red UI hostname:1880/.

All other configurations can also be made in the docker-compose.yml.

Trouble-shooting

Can't apt-get update in Dockerfile:

Restart the service

sudo service docker restart

or add the file /etc/docker/daemon.json with the content:

{
    "dns": [your_dns, "8.8.8.8", "8.8.8.4"]
}

where your_dns can be found with the command:

nmcli device show <interfacename> | grep IP4.DNS

Traceback of non zero code 4 or 128:

Restart service with sudo service docker restart

or add your dns address as described above