Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Eclipse Unconference France 2015/Tiaki Hackathon"

Line 16: Line 16:
 
Ready for discovery ... Scada can use Kiaora (DiscoveryLibs) to discover services and eventually connect to them
 
Ready for discovery ... Scada can use Kiaora (DiscoveryLibs) to discover services and eventually connect to them
  
[[File:4._service_discovery.png]]
+
[[File:4._service_discovery.png]]
  
  
Line 28: Line 28:
 
- connect to the service
 
- connect to the service
  
[[File:3._adding_devices_and_keys.png]]
+
[[File:3._adding_devices_and_keys.png]]

Revision as of 04:12, 19 June 2015

This document explains the proposed work flow for the Eclipse Hackathon session.

The idea is to have Eclipse Scada discover available services using Kiaora (DNS-SD), connect to those services, and compute some values and push data to AirVantage.

Before Scada can actually start discovering services and use them, it is necessary to sign-up for those services ...

As describe below, Scada user would register with forecast.io (weather forecast), AirVantage (data platform) and the Verisign API (allows to easily provision service information in DNS).

1. signing up.png

Now that the user has signed up for the services, he can use the Verisign API to provision the services to be discovered. [TODO add URL to online documentation here]

2. provisioning.png


Ready for discovery ... Scada can use Kiaora (DiscoveryLibs) to discover services and eventually connect to them

4. service discovery.png



As of now, using Kiaora, Scada could discover the services registered under its domain name. To connect to those services, it uses the API Key that was created when the user has signed up for the service. In order to avoid having to send the API key to Scada, we could do the following: - generate a public/private key pair for Scada - publish the public key in DNS (using Verisign API) - encrypt the API key with the Scada public key and push it do DNS - let Scada retrieve the the encrypted API Key from DNS and decrypt it - connect to the service

3. adding devices and keys.png

Back to the top