This document introduces OCCIware, which allows modeling and piloting all cloud layers from IoT to Big Data using the OCCI standard. It provides an overview of OCCIware, demonstrates its use in a smart city use case monitoring energy consumption from IoT sensors to linked open data analytics, and shows a quick demo of Docker Studio and a custom linked data extension. It concludes by discussing next steps for OCCIware and Eclipse.org.

1. OCCIware
Model and pilot all cloud layers with OCCIware, from
IoT to Big Data
Marc Dutoo, Smile
Eclipse Day Lyon 2017

2. Overview
Speaker
– Marc Dutoo, R&D projects lead at Smile
●
OCCIware coordinator, Data / API / Cloud expert, Eclipse SOA
committer
Schedule
– OCCI(ware) introduction – model & pilot all cloud layers
– Smart City use case – IoT to Big Linked Open Data analytics
– Quick demo – Docker Studio, custom Linked Data extension, runtime
and Playground, and more
– What's next for OCCIware – and Eclipse.org !

3. OCCI(ware) Introduction
model and pilot all cloud layers

4. A quick question...
Who uses multi cloud today ?

5. A quick question...
Who uses multi cloud today ?
… everybody
●
Docker in devops, and Kubernetes in
production
●
AWS, except when its Service – Task model
of scalability is not fine enough
●
National clouds to ensure data jurisdiction
●
… as soon as appears in your application a
new need that calls for a cheaper / faster /
more robust / more scalable / ... Cloud

6. Cloud Computing – the problem

7. Why OCCI ?
• So this makes for partitioning, lock-in...
• And a lot of technical glue, therefore
making it all hard to maintain
• The OCCI standard advocates a unified,
uniform architectural approach
- to separate this glue (connectors)
- from business logic consuming them
through the standard, generic OCCI REST
HTTP API
• ... the rise of the Cloud consumer platform

8. OCCIware Product

9. OCCI 101
OCCI Core
(metamodel)
Network
Container
Environment
Compute
- memory
- started
- start()
Database
Application
Storage
Router
Deployable
NetworkLink
DatabaseLink
EnvironmentLink
Everything
is Resource
or Link, be
it at …
Platform
level
Infrastructure
level
Application
level
OCCI Extensions (models)
+ flexible typing
thanks to Aspect-
like Mixins

10. OCCIware Objective
Managing Everything as a Service in the clouds
Software as a Service (SaaS)
Big Data as a Service (BDaaS)
Linked Data as a Service (LDaaS)
Platform as a Service (PaaS)
Container as a Service (CaaS)
Infrastructure as a Service (IaaS)
DataCenter as a Service (DCaaS)
Network as a Service (NaaS)

11. OCCIware Factsheet
• 72 man year, 5,6m€ budget, sponsored by
French ministry of Industry over 2015-2018
• 3 academics, 5 companies, 2 associations
• To lower Cloud Computing adoption costs and
break up barriers between its various
implementations, layers, domains
- Especially Data Center, deployment, Big Data, Linked
Data
• By bringing to OGF's Open Cloud Computing
Interface (OCCI) the power of formal languages
and model driven engineering (MDE)

12. Powered by

13. OCCI Designer
OCCI textual DSL
Docker
Designer
Wiki doc

14. OCCIware Runtime - end-to-end OCCI API call chain
Studio
XML-
based
Extensio
n
Cloud
Manager
OCCI
Requests
LDaaS
PaaS
IaaS
HTTP runtime
HTTP runtime
HTTP runtime
HTTP runtime

15. How did we get there ?
Eclipse Modeling approach

16. Occi tools creation with EMF
Ecore
Your Domain Model
Your Model
EClass, EReference
Occi standard
Occi Extension
Occi Configuration
Entity, Kind, Link
Docker, Infrastructure
Server 1, VM Foo

17. Occi tools creation with EMF
Occi standard
Occi Extension
Occi Configuration
Entity, Kind, Link
Docker, Infrastructure
Server 1, VM Foo
Ecore
Your Domain Model
Your Model
?
EClass, EReference
Ecore
EClass, EReference

18. Domain Model « Promotion »
Occi.ecore
MyExtension.occi
Entity, Kind, Link
Docker, Infrastructure
Ecore
EClass, EReference
Ecore
MyExtension.ecore
MyConfiguration.docker
EClass, EReference
Server 1, VM Foo
Docker

19. OCCIware Studio Factory
<<E>>
Designer
Skeleton
e.ecore
<<E>>
Extension
e.genmod
el
e.odesign
Occie2Ecore
Ecore2Sirius EMF genmodel
EMF Java
code
EMF Java
code
EMF Java
code
<<E>>
Configuration
<<E>>
Configuration
<<E>>
Configuration

20. IoT to Big Linked Open Data Analytics
Use case : monitoring energy consumption

21. Monitor energy consumption
• Not only per user, or per utility provider
company,
• but per city, region, country,
- and per activity, usage, number of
children, amount of hair on feet would
most probably help also.
Multi-point of view data... that calls for
an open world approach of data – that's
Linked Data.

22. Linked Data Primer
• Linked Open Data ? That's Open Data sets that can
be cross-queried because they have been
semantically reconciled together
• Enter Ozwillo Datacore :
- it holds data that is shared between applications of
the Ozwillo app store : geographical elements,
organizations, reusable app business data…
- it stores it in a shardable replicated MongoDB and
is built in Apache CXF / Spring & Java
- it provides it through a REST API that is both web-
friendly and semantic web-compatible thanks to
JSON-LD, and helps developers with a Playground.

23. Linked Data, as a Service

24. Linked Data as a Service
(LDaaS)
But not your dad's Linked Data. If you want it to save
the world, it has to scale up the whole way :
• at Infrastructure level - that's IaaS : provision
enough CPU & storage, for each city
• at Platform level - that's PaaS : deploy code - java and
data - mongo replicated cluster shards on each of them
• at Software level - that's SaaS : configure Linked Data
governance i.e. models and kinds of use :
- high write, non-robust data collection (home
energy consumption sensor notifications)
- read/query-heavy data analysis (aggregation per
energy consumer, provider, city, region, country)

25. Mongo
primary
Mongo
primary
Mongo
seconda
ry
Mongo
seconda
ry
Mongo
synchro
VMVM VMVM
Energy consumption
probes
Deep data
analysis
Datacore APIDatacore APILD OCCI APILD OCCI API
Ozwillo Infrastructure
Project
governance
LDProject
status:
published
LDProject
robust: false
LDProject
storage:
secondary
LDNode
name: main
VMVM
Mongo
seconda
ry
Mongo
seconda
ry
3.2.1. import bridge
Blynk
gateway

26. A point on the IoT integration

27. Quick demo – Docker Studio, custom
Linked Data extension and more

28. Cloud Studio, with Docker

29. Custom Studio for LdaaS
(Linked Data as a Service)

30. Docker Studio
IaaS - Virtual Box machine

31. Docker Studio
IaaS - Ozwillo machine

32. Docker Studio
… started !

33. SaaS - Linked Data with
dedicated analytics entry point
Linked
Data
Studio

34. … using a specific mongodb
replica within its cluster !
Linked
Data
Studio

35. …
piloted
live !
Big
news –
Now an
OW2
project !
OCCI web Playground
http://occinterface.herokuapp.com/

36. Allowing to not hamper data collaboration
performance when aggregating energy
consumption - results shown here :
...by consumer
...by his city

37. Deploying connectors
• The same connectors - for Docker, VMWare,
OpenStack, but also Roboconf, Datacore...
• Can be deployed embedded in the OCCIware
Studio during development
• But also exposed as OCCI HTTP in production
- either in the full Java MART server (Model@RunTime)
- or behind the scalable, erlang-based erocci server
• Where they can be tested, introspected and
managed using the OCCInterface web
playground
- works with any OCCI API implementation – try yours !

38. Latest news from OCCIware
- OCCI Studio : v2, contribute to Eclipse.org in 2018,
simulation plugins https://github.com/occiware/OCCI-Studio
- & Docker Studio & VMWare, OpenShift, Monitoring, SLA, QoS extensions
- Runtime : end-to-end, SaaS / PaaS / IaaS OCCI platform
with ActiveEon OW2 ProActive Multi-IaaS connector,
Linagora OW2 Roboconf PaaS manager, MART OCCI server
- live web Playground now an OW2 project, new features –
http://occinterface.herokuapp.com/
- OCCI monitoring (Tinom : OCCI monitoring for Java) for QoS (OCCI SLA
extensions) and scalability (on Roboconf)
- Complete use cases : Datacenter, Big Data, Deployment,
Linked Data (IoT, Big Data - new : app scalability demo)
- Inria-incubated startup, Smile LDaaS offering...
- … and contribute back to OCCI 2.0 standard !

39. Any questions ?
Thanks for your attention !
Contact : http://www.occiware.org - philippe.merle at inria.fr,
marc.dutoo at smile.fr, christophe.dorothee at smile.fr
Source : https://github.com/occiware
Partners :
Sponsors :
DGE (PIA) & System@tic, SCS, Images & Réseaux, PICOM, Minalogic clusters