Charlton Barreto - The OGF | Open Cloud Computing Interface


Published on

The OGF | Open Cloud Computing Interface. CloudCamp Hamburg 2010

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Charlton Barreto - The OGF | Open Cloud Computing Interface

  1. 1. CloudCamp Hamburg September 2010 Charlton Barreto
  2. 2. 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…
  3. 3. Open Cloud Open Formats Open Interfaces Open Data Open Source
  4. 4. 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. 5. 5 OCCI HTTP HeaderOCCI Core OCCI Infratructure „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
  6. 6. OCCI provides features to identify, link and operate on „dumb“ RESTful Resources
  7. 7. 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 can be 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 and automated management interfaces 2.10 A.1.9. Then requesting new resource(s) the request must be fully complete/describing ... ... ... 7 Taken from Requirements & Use Cases Document
  8. 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. 9
  10. 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. 11. 11 OCCI HTTP HeaderOCCI Core OCCI Infratructure 50 % 99 % 99 % 99 %
  12. 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 #occi <- lots of work through that medium  5 separate implementations  All updates will be readied for OGF30 along with demos
  13. 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. 14. 14 Push OCCI to DMTF? Sharing Requirements Other thoughts? How-to collaborate?
  15. 15. 15 Collaborations? If so:Who? With Demo! Other groups?
  16. 16. Thanks Charlton Barreto Resources: (Wiki) (Mailing List) Enjoy CloudCamp Hamburg! 16