Transcript of "Charlton Barreto - The OGF | Open Cloud Computing Interface"
All about cheap compute
All hype, no substance
Only about ‘public’ clouds
Cloud architectures deliver agility and a lower
cost of service delivery.
Cloud is an architecture, a business model,
and a way to operate IT.
Public clouds first, then Private clouds.
There is some security. But, limited security
limits the uses.
A simple SLA is still an SLA. Private clouds
demand better. Are three 9’s good enough?
Nothing new Clouds are an integrated evolution of utility
computing, automation, grid, and HPC.
Clouds use only open source Yep.With a few minor exceptions…
The Open Cloud Computing Interface (OCCI) is
now a Protocol (and an API soon)
It is designed to be modular & extensible
OCCI has a vivid communtiy with chairs from
Core REST,CRUD + Categories, Links,
OCCI Infrastructure Kinds,Actions,Attributes for IaaS
HTTP Header A HTTP rendering
RDF/RDFa (Work in Progress) A RDFa rendering
OCCI provides features to
identify, link and operate on
„dumb“ RESTful Resources
ID Description Usecases
B.3.1. No development tools or libraries should be needed by
A.2.12. A common interface should be used which can
be supported by many Cloud service providers
(regarding Infrastructure and Data interfaces).
A.2.11. Support a subset of all functions of today IaaS based
Clouds (e.g.Amaton EC2)
A.2.9. Support the usage of terminal, web, desktop and
automated management interfaces
A.1.9. Then requesting new resource(s) the request must
be fully complete/describing
... ... ...
Taken from Requirements & Use Cases Document http://ogf.org/documents/GFD.162.pdf
Known to work (especially with firewalls)
Easy to use in all programming languages
HTTP is the defacto standard of the Internet – so why
not use it?
Why didn‘t we chose XML, JSON, OVF ,*?
No lock-in – our community had different opinions
now you can use what suits you best (even OVF!)
▪ Also gives us freedom for PaaS and SaaS
HTTP Header is very easy & good for interop!
▪ Attributes (key-value) are simple to use for customization of existing
This was just the „tip of the iceberg“
OCCI is available for implementation (and is
Focus of work is now on refinements, Extensions
(Billing etc), RDFa, and an API
Can be used for not only IaaS bus also
PaaS/SaaS (Work in Progress)
Extend it:Write Kinds, Actions & Attributes (very
The core of OCCI has now been well defined.
The core is easily extendable by anyone.
Further refinement of the HTTP header
rendering specification will soon be completed
IRC channel running up on irc.freenode.net
#occi <- lots of work through that medium
5 separate implementations
All updates will be readied for OGF30 along