The OGF | Open Cloud Computing Interface

1. CloudCamp Hamburg
Charlton Barreto
charlton.barreto@intel.com September 2010

2. Perception Reality
All about cheap compute Cloud architectures deliver agility and a lower
cost of service delivery.
All hype, no substance Cloud is an architecture, a business model,
and a way to operate IT.
Only about ‘public’ clouds Public clouds first, then Private clouds.
No security There is some security. But, limited security
limits the uses.
No SLA’s 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…
2

3. Open Formats
Open Open Open
Data Cloud Interfaces
Open Source

4.  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
commercial providers
4

5. OCCI
Infratructure
OCCI
OCCI HTTP Header
Core
„Module“ Description
Core REST, CRUD + Categories, Links,
Registries
OCCI Infrastructure Kinds, Actions, Attributes for IaaS
HTTP Header A HTTP rendering
RDF/RDFa (Work in Progress) A RDFa rendering
5

6. OCCI provides features to
identify, link and operate on
„dumb“ RESTful Resources

7. ID Description Usecases
B.3.1. No development tools or libraries should be needed by 2.8
the end-user
A.2.12. A common interface should be used which can 2.13, 2.14
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 2.6
Clouds (e.g. Amaton EC2)
A.2.9. Support the usage of terminal, web, desktop and 2.10
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
7

8.  Why REST/HTTP?
 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
templates
8

9. 9

10.  This was just the „tip of the iceberg“ 
 OCCI is available for implementation (and is
implemented)
 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
easy!)
10

11. 50
% 99
%
OCCI
Infratructure 99
OCCI %
99
OCCI % HTTP Header
Core
11

12.  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
with demos

13. 1. OCCI
 RDFa/XHTML5 rendering
2. Extensions
 Collections
 Monitoring
 (Snappshotting, Advanced Reservation)
 ...
3. Implementations
 Demonstrate 2 interoperable implementations
 5 implementations presently
4. Collaboration with other groups
 DMTF
 DRMAAv2, WS-Agreement, ...
13

14. Push OCCI Sharing
to DMTF? Requirements
Other How-to
thoughts? collaborate?
14

15. Other
groups?
Collaborations?
If so: Who?
With
Demo!
15

16. Thanks
Charlton Barreto
charlton.barreto@intel.com
http://charlton.typepad.com/weblog
http://twitter.com/charltonb
Resources:
http://www.occi-wg.org
http://forge.ogf.org/sf/go/projects.occi-wg/wiki (Wiki)
http://www.ogf.org/mailman/listinfo/occi-wg (Mailing List)
Enjoy CloudCamp Hamburg!
16
www.intel.com