AGILE Cloud Communication

1. Agile Cloud Communication
ROMÁN SOSA
ATOS
AGILE 3rd F2F MEETING, 20-21 July 2016, Berlin, DE

2. WP4 Objectives
Provide connectors to extend the capabilities of the gateway by managing
data and deploying apps in existing cloud systems.
Gateway support for:
◦ public(*) clouds: IoT cloud services (Xively, Thingspeak…), DropBox, Google Drive,
CloudFoundry-based PaaSs…
◦ private (*) clouds: FIWARE PaaS GE, Object Storage GE, clouds developed for
pilots, 3rd party cloud systems used for device data exchange (FitBit, Withings…)
Define a way to integrate connectors to additional Cloud platforms in an
easy way.
Support pilot integration with the clouds
(*) Term to be changed
AGILE 3rd F2F MEETING, 20-21 July 2016, Berlin, DE

3. WP4 Tasks
T4.1. Collection of Cloud APIs, endpoints and Cloud enablers (M7-M12)
◦ Identify the APIs and enablers for the clouds to be supported
◦ Integration of clouds used by the pilots
T4.2. Integration of public cloud infrastructures (M13-M20)
T4.3. Integration of private cloud infrastructures (M13-M20)
T4.4. Integration with Pilots (M19-M36)
AGILE 3rd F2F MEETING, 20-21 July 2016, Berlin, DE

4. Task 4.1
Planning
1. Identification and classification of cloud providers [1]
2. Assignment of contribution from each partner [1]
3. Rewrite WP4 in DoW according to classification
4. Modularization
[1]:https://docs.google.com/spreadsheets/d/1Ft5Y1y5jWhtXP1hOu572tolZyFWMo8OuE-OYnpq4sCE/edit#gid=0
AGILE 3rd F2F MEETING, 20-21 July 2016, Berlin, DE

5. Identification of cloud
providers
Apps deployment
◦ Azure
◦ CloudFoundry
Storage
◦ Dropbox
◦ Google Drive
◦ Google Weave
◦ …
IoT platforms
◦ EDC
◦ Xively
AGILE 3rd F2F MEETING, 20-21 July 2016, Berlin, DE

6. Clouds diagram
AGILE 3rd F2F MEETING, 20-21 July 2016, Berlin, DE
IDE
Cloud Deployment
GW
Cloud Data Module
install_cloud_app() read()
write()
install_app()

7. Issues: Terminology
NIST definition of cloud [1]
Private cloud
Public cloud
PaaS
[1]: http://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-145.pdf

8. Issues: IoT platforms
Are we going to manage IoT platform capabilities?
Modularity

9. Contribution: iMinds
???

10. Contribution: resin.io
We have to find where resion.io fits into the cloud deployment (how do
we define cloud? J)

11. Contribution: Jolocom
Use of FreedomBox. Data is stored in the gateway. What do you want to
store in the cloud?

12. Contribution: TuGraz
Involved in T4.2 and T4.3.
Recommender should take clouds into account

13. Thanks!