|Mark deVilliers e8a886233d correct path to image||3 years ago|
|client||3 years ago|
|cmd||3 years ago|
|docker||3 years ago|
|docs||3 years ago|
|metadata||3 years ago|
|node||3 years ago|
|storage||3 years ago|
|swagger-ui||3 years ago|
|tools||3 years ago|
|ui||3 years ago|
|utils||3 years ago|
|vendor||3 years ago|
|.gitignore||3 years ago|
|.licenses.yaml||3 years ago|
|LICENSE||3 years ago|
|Makefile||3 years ago|
|README.md||3 years ago|
|docker-compose.yml||3 years ago|
|glide.lock||3 years ago|
|glide.yaml||3 years ago|
|version.go||3 years ago|
This repository contains an early stage prototype working demonstrator which is capable of:
The purpose of the prototype is to demonstrate some of the concepts from the DECODE project grounded in an IoT use-case.
An introduction to concepts of data entitlements as well as a review of prior art was completed as part of the DECODE project.
From the review: Data entitlements could be thought of as an evolution of a traditional authorization scheme specialized for the securing of both personal, business and IoT data. Giving the data owner full control of the access and discovery of their data creates a system of empowerment whose currency is privacy….The relationship of privacy and data entitlement is subject to many nuances. Users might allow a party to search and access their data, but only under the understanding that they will not be personally identified or only under specific circumstances. For example, a driver of a motor vehicle with an on-board camera might want to entitle the emergency services access to his data when there is a road traffic accident. However, the driver might not want to be identified as being in a certain geographical area or that he was exceeding the speed limit at the time. Data,when available, can directly or indirectly compromise privacy in a way that would surprise a user. The full document, D3.1 Survey of Technologies for ABC, Entitlements and Blockchains, can be found here - https://desk.dyne.org/s/7gHFaUIoNEFB1Wx#pdfviewer.
For the purposes of the prototype any singular piece of data in our system will have a data entitlement in one of three logical states -
To qualify the terms used above :
It is important to note that the prototype does not, by design, implement authentication and as such all entitlements once given are applied globally.
An introduction to concepts of data entitlements as well as a review of prior art was completed as part of the DECODE project. This document can be found here.
The prototype is implemented as a set of HTTP services, written in golang, exposing various endpoints accepting various JSON messages in a REST-like manner. Each of the services is documented with a swagger api
An overview of a single node system.
In this diagram two IoT devices logically direct their data to the node service. As a convenience we have included fake IoT devices as part of the prototype. The output of these fake devices correspond to the output of the device-hub component as developed by thingful and open-sourced as part of the DECODE project.
The node service is the entry point for an instance of the storage service. The node has a relationship with the metadata service.
The node service is responsible for:
The node service has a storage service which is responsible for:
The node service corresponds to the concept of the DECODE node in the DECODE Architecture whitepaper. Please note this has not been made public yet.
The metadata service is responsible for:
Both the node and metadata service expose a user interface.
The architecture is designed to scale with multiple DECODE nodes using a single metadata service.
Please note the following:
To build the software ensure you have installed the following software :
Once you have a working installation download the code using the go get
go get gogs.dyne.org/DECODE/decode-prototype-da
The makefile contains helpers to build the environment plus some helpers for development.
To build all of the docker containers locally for docker compose to use
To run the application components via docker compose
The docker-compose tool will then map the ports exposed by the containers to local ports on you own machine.
The ports it will try and use are - 8080, 8081 and 8083.
If theses ports are already in use the docker-compose tool will display a warning.
The prototype should then be available at the following urls
'node' swagger api - http://localhost:8080/apidocs
'node' ui - http://localhost:8080
'metadata' swagger api - http://localhost:8081/apidocs
'metadata' ui - http://localhost:8081
'storage' swagger api - http://localhost:8083/apidocs
To stop the application components via docker compose you can either type Ctrl-C or from another window issue the command