3. Cloud
Standards
• Amazon
EC2
– de
facto
standard
– but
proprietary
• OpenStack
– open
source
reference
– but
IaaS
only
• ISO/IEC
OVF
– interna2onal
standard
– but
OS
image
only
• DMTF
CIMI
– interna2onal
standard
– but
IaaS
only
• OASIS
CAMP
– industrial
standard
– but
PaaS
only
• OASIS
TOSCA
– industrial
standard
– but
SaaS
only
No
universal
standard!
4. What
about
OCCI?
• Open
Cloud
Compu>ng
Interface
• Open
Grid
Forum
• Recommenda>ons
– Not
standard
but
could
become
• Not
IaaS
only!
• Extensible
by
construc>on
• Various
implementa>ons
10. OCCI
Issues
• Lack
of
a
formal
specifica>on
• Only
an
informal
defini>on,
aka
UML
+
English
• Inconsistencies,
ambigui>es,
incomplete
LLL
• Interoperability
issues
!!!
• Lack
of
so`ware
engineering
tools
• Only
run>me
frameworks
(erocci,
rOCCI,
pyOCNI,
OCCI4Java)
• How
to
model/develop/test/…
new
kinds
of
OCCI
en>>es
• Lack
of
standardisa>on
• Large
community:
Oracle,
…,
OpenStack,
CloudStack,
OpenNebula,
…,
Compa>bleOne,
…
• Excepts
three
big
actors
(Amazon,
Microso`,
Google)!!!
PIA
OCCIware
11. OCCIware
• A
formal
framework
for
OCCI
designing
– Think,
model
and
analyse
OCCI
extensions
• A
model-‐driven
tool
chain
for
OCCI
engineering
– Design,
develop,
test,
and
simulate
OCCI
extensions
• A
Models@run.>me
kernel
for
OCCI
deployment
– Deploy
and
execute
OCCI
models
directly
12. OCCIware
Formal
Framework
• Think,
model
and
analyse
OCCI
extensions
• Various
aspects
• Structural
• Behavioural
• QoS
• SLA
• performance
• etc.
• A
formal
specifica>on
of
OCCI
– Consistent,
unambiguous,
complete,
and
proved
13. OCCIware
Formal
Framework
• Implemented
with
Alloy
– a
lightweight
specifica>on
language
based
on
first-‐order
rela>onal
logic
– hWp://alloy.mit.edu