Dockerfile to create a Docker container image for Warp 10.
The easiest way to setup the Warp10 platform is to use Docker. Builds of Warp10's Docker image are available on Dockerhub. It is the recommended method of installation. A 'Continuous Integration' version has been provided. This version is available on Dockerhub with the 'ci' suffix. This version embeds a pair of READ/WRITE tokens named respectively 'READ', 'WRITE'.
Start your image binding the external ports 8080 and 8081 in all interfaces to your container.
Docker containers are easy to delete. If you delete your container instance, you'll lose the Warp10 store and configuration. So by default you should add a volume mapping to the containers /data folder.
docker run --volume=/var/warp10:/data -p 8080:8080 -p 8081:8081 -d -i warp10io/warp10:x.y.z
Where x.y.z is the image version (the current one being 1.2.9).
In this example you bind the container internal data folder, /data to your local folder /var/warp10.
You must use the same --volume option in all your other docker commands on warp10 image.
The Warp 10 platform is built with a robust security model that allows you to have a tight control of who has the right to write and/or read data. The model is structured around the concepts of data producer, data owner and application, and WRITE and READ tokens.
The 'ci' version embeds a pair of pre-generated READ/WRITE tokens named respectively 'READ', 'WRITE'. These tokens are in the predictible-tokens-for-ci/ci.tokens file.
Otherwise, for the purposes of this setup, you need to generate write and read tokens for a test application for a test user that is both the producer and the owner of the data. In order to interact with the user/token/application system, you need an interactive access to Warp10's Worf component. You get it by executing warp10-standalone.sh worf on the running container.
First, get the container id for your running Warp 10 image:
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
dc6e541e79d8 warp10io/warp10:1.2.9 "/bin/sh -c ${WARP10_" 55 seconds ago Up 55 seconds 0.0.0.0:8080-8081->8080-8081/tcp hopeful_einstein
Then run docker exec to run Worf on that container id:
docker exec --user warp10 -t -i dc6e541e79d8 warp10-standalone.sh worf appName ttl(ms)
Where appName is the choosen application name and ttl(ms) the time-of-life of the token in milliseconds.
For example, let's generate a pair of tokens for an application called test, with one year of livespan:
$ docker exec --user warp10 -t -i dc6e541e79d8 warp10-standalone.sh worf test 31536000000
default options loaded from file:/opt/warp10/etc/.conf-standalone.conf.worf
{"read":{"token":"1Uol41cpikTrY5IGUgtwHG4kZ0puh5clethlBuq2Qjs5kWaRhvQOsHKHXsnpH5.lU7GePUIZowFTblA5lkeuDeqFZGgzrmVp1RTWghrA.f5ahLbUVO0S2.","tokenIdent":"ef8cd2a9e3e15fd9","ttl":31536000000,"application":"test","owner":"d7d310cf-254e-4065-87ae-47e83a050ab3","producer":"d7d310cf-254e-4065-87ae-47e83a050ab3"},"write":{"token":"yCY6J7jKJTWgQVrNJpsgPav7ubqiZIlx0jtDibNYO5cJNzq8EziSGOszoXGmFgXFnXbI_Yq3WXg53ry4qXkWU4vkjK9tmE3cWccPbzWvo9c","tokenIdent":"cc3a63e7b7d5ca1b","ttl":31536000000,"application":"test","owner":"d7d310cf-254e-4065-87ae-47e83a050ab3","producer":"d7d310cf-254e-4065-87ae-47e83a050ab3"}}
To test the running container, push a single GTS containing one data in the platform using your WRITE token.
curl -v -H 'X-Warp10-Token: WRITE_TOKEN' --data-binary "1// test{} 42" 'http://127.0.0.1:8080/api/v0/update'
If everything is OK, you should receive a HTTP 200
When using Docker on Mac OS or Windows, there is no binding between Warp 10 API address and the host (docker is runned throw a Virtual Machine). To reach Warp10 you need to replace 127.0.0.1 by the real Ip address of the container. To get it, use a simple
docker-machine ip default>, the container address is also shown in the Settings/Ports page of your container. If you used the shared volume between the container and the host, you can access to the virtual machine usingdocker-machine ssh default>and inspect the repertory/var/warp10. Don't hesitate to check on docker-machine documentation.
Get this data using your READ tokens.
curl -v --data-binary "'READ_TOKEN' 'test' {} NOW -1 FETCH" 'http://127.0.0.1:8080/api/v0/exec'
If everything is OK, you should receive a HTTP 200 OK with your datapoint in JSON format.
A full getting started is available to guide your first steps into Warp 10.
Warp 10's Quantum is a web application aiming to allow users to interact with the platform in an user-friendly way, offering an alternative to command-line interaction.
A standalone version of Quantum is packaged in the Docker image you have just installed, listening on the port 8081. In a Linux system (with binding between Warp 10 API address and the host) you can access Quantum at
127.0.0.1:8081. In Mac OS or Windows, there is no binding between Warp 10 API address and the host, you need to replace 127.0.0.1 by the real Ip address of the container as explained in the precedent section.
If you want to build your own Warp10 image, clone this repository
git clone https://github.com/cityzendata/warp10-docker.git
Execute docker build inside your local copy
cd warp10-docker
docker build -t myrepo/warp10:x.y.z .