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.
Difference between revisions of "Eclipse Unconference France 2015/Tiaki Hackathon"
(Created page with "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...") |
|||
| Line 13: | Line 13: | ||
[[File:2._provisioning.png]] | [[File:2._provisioning.png]] | ||
| − | As of now, using Kiaora, Scada could discover the services registered under its domain name. To connect to those services, it | + | |
| + | Ready for discovery ... Scada can use Kiaora (DiscoveryLibs) to discover services and eventually connect to them | ||
| + | |||
| + | [[File: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 | - generate a public/private key pair for Scada | ||
- publish the public key in DNS (using Verisign API) | - publish the public key in DNS (using Verisign API) | ||
| Line 21: | Line 29: | ||
[[File:3._adding_devices_and_keys.png]] | [[File:3._adding_devices_and_keys.png]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 04:11, 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).
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]
Ready for discovery ... Scada can use Kiaora (DiscoveryLibs) to discover services and eventually connect to them
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
