Upload
symposia-media
View
572
Download
3
Tags:
Embed Size (px)
DESCRIPTION
The OGF | Open Cloud Computing Interface. CloudCamp Hamburg 2010
Citation preview
2
All about cheap compute
Perception
All hype, no substance
Only about ‘public’ clouds
No security
No SLA’s
Cloud architectures deliver agility and a lower cost of service delivery.
Reality
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…
OpenCloud
Open Formats
OpenInterfaces
OpenData
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
5
OCCIHTTP HeaderOCCI
Core
OCCIInfratructure
„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
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 the end-user
2.8
A.2.12. A common interface should be used which canbe supported by many Cloud service providers(regarding Infrastructure and Data interfaces).
2.13, 2.14
A.2.11. Support a subset of all functions of today IaaS based Clouds (e.g. Amaton EC2)
2.6
A.2.9. Support the usage of terminal, web, desktop andautomated management interfaces
2.10
A.1.9. Then requesting new resource(s) the request mustbe fully complete/describing
... ... ...
7
Taken from Requirements & Use Cases Document http://ogf.org/documents/GFD.162.pdf
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
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
OCCIHTTP HeaderOCCI
Core
OCCIInfratructure
50
% 99
%
99
%
99
%
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
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
to DMTF?Sharing
Requirements
Other
thoughts?
How-to
collaborate?
15
Collaborations?If so: Who?
With
Demo!
Other
groups?
www.intel.com
Thanks
Charlton Barreto [email protected]://charlton.typepad.com/webloghttp://twitter.com/charltonb
Resources:
http://www.occi-wg.orghttp://forge.ogf.org/sf/go/projects.occi-wg/wiki (Wiki)http://www.ogf.org/mailman/listinfo/occi-wg (Mailing List)
Enjoy CloudCamp Hamburg!
16