OGF Cloud Standards: Current status and ongoing interoperability efforts with DMTF, SNIA and other organizations


Published on

Presentation at Cloud Standards Customer Council Quarterly Meeting in Santa Clara, December 2011

Published in: Technology, Business
  • 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

OGF Cloud Standards: Current status and ongoing interoperability efforts with DMTF, SNIA and other organizations

  1. 1. OGF Cloud Standards:Current Status andOngoing Interoperability EffortsWith DMTF, SNIA and Other Organizations Alan Sill, Ph.D Vice President of Standards, Open Grid Forum Florian Feldhaus GWDG Göttingen©2011Open Grid Forum CSCC Meeting – Dec 2011
  2. 2. OGF  standards  are  part  of  the  Grid  Final  Document  series  (GFDs),  which  has  a  strong  track  record  of  adop=on  in  large-­‐scale  commercial  and  academic  distributed  compu=ng  products.  OGF’s success in cloud and grid standards development spans more than a decade. 2  
  3. 3. OGF Cloud Standards Background•  OGF has an extensive set of applicable standards and documents related to topics in cloud computing: -  Federated Identity Management -  Managing the Trust Eco-System (CA operations, AuthN/AuthZ) -  Virtual Organizations (VOMS) -  Job Submission and Workflow Management (JSDL, BES) -  Network Management (NMI, NSI, NSF) -  Secure, fast multi--party data transfer (GridFTP, SRM) -  Data Format Description (DFDL) -  Service Agreements (WS-Agreement, WS-Agreement Negotiation) -  Cloud Computing interfaces (OCCI) -  Firewall Traversal (FiTP) -  Others under development•  Working to gather this information to form an organized description of OGF work - an OGF Cloud Portfolio - and to start new working groups on related topics. © 2011 Open Grid Forum 3
  4. 4. OCCI Positioning 4
  5. 5. Status of OGF OCCI Standards•  GFD.183: Open Cloud Computing Interface - Core , GFD.184: Open Cloud Computing Interface - Infrastructure published April 2011; slight revisions to textual portions released June 2011 (no changes to normative content).•  GFD.185: Open Cloud Computing Interface - RESTful HTTP Rendering published June 2011•  These standards are now stable and complete and being implemented by the community.•  OCCI JSON Rendering being worked on now.•  Many implementations now exist - very strong uptake!•  InfoQ article summarizing interoperability published.•  Clients being written to supplement server implementations. © 2011 Open Grid Forum 5
  6. 6. Updates On RecentOCCI Implementations •  New OpenNebula implementation in progress - full OCCI v1.1 compliance! OCCI client tools, instructions and tutorials on OpenNebula developer site including examples •  uptake of OCCI work within SLA@SOI by FP7 Future Internet FI-Ware project. •  R2AD: New Android and JavaFX Cloud Client apps including OCCI and CDMI: design done, demos available and beta implementation in progress. •  occi-py Python framework developed by Ralf Nyren: RDBMs- friendly backend; draft JSON rendering implemented and demo instance available for testing. •  OpenStack implementation code work started, new client and server libraries available. •  More info at http://occi-wg.org/community/implementations/ © 2011 Open Grid Forum 6
  7. 7. New R2AD Cloud Client (Info. from Michael Behrens) Example Interfaces to•  Building to OCCI, CDMI, and Data Standardize other standards Transport Compute Desirable Features Pluggable Policy -  Goal: Interact with cloud Billing Scalable Secure providers using the Simple Dynamic standard RESTful APIs, Metadata RESTful thereby reducing the code development and Standardized IaaS/PaaS Layer maintenance cost OCCI CDMI OVF•  Participating in SNIA Plug- Fests for OCCI/CDMI/OVF Other Specs Integration Major Functions: • OCCI: Status/Control•  Visit http://r2ad.net Resources, Create and -  Info & Screen Shots Update Resources (VMs) -  Android and JavaFX up • CDMI: Create/Delete mock -  Beta: Nov 2011 Containers, Browse •  65% compete Storage Containers via CDMI, Upload content © 2011 Open Grid Forum 7
  8. 8. New OCCI Work in OpenStack•  Based on pyocci (Thijs Metsch/Platform Computing) w/ input from other developers•  Allows for the provisioning of VMs -  OCCI Infrastructure specification -  OCCI v1.1 compliance•  Implemented by EU FP7 SAIL project in cooperation with an industrial partner -  www.sail-project.eu•  Discussed at OpenStack Design Summit Oct 3-5, 2011; work currently in progress.•  Current goal is to be in Essex release, March 2012. © 2011 Open Grid Forum 8
  9. 9. Cloud Interoperability Efforts•  SNIA Cloud Plugfests have been used for combined interoperability efforts: April, July, Sept 2011, Spring 2012.•  Several active OCCI and CDMI implementations!•  Integration of OCCI and CDMI reportedly works well.•  OVF integration under active development & progressing.•  Next steps and new testing work planned: -  Feed back experience from implementations, write implementation experience documents and user guides. -  Develop combined OCCI / CDMI / OVF verification suite. -  Stress/scaling testing, performance studies at scale. -  Interoperability testing w/ OGF Cloud Interoperability efforts. -  Extending OCCI with monitoring / reservation capabilities. -  Integration with other OGF & relevant standards.•  OGF forming new Cloud Interoperability Working Group © 2011 Open Grid Forum 9
  10. 10. OCCI/CDMI/OVF InteroperabilityDemonstration: SLA     Webservice   Management   OCCI  /  CDMI  Client   Template   Storage   OVF   Network   OS   Resource   Compute   OCCI  Server   CDMI  Server   Credit:  F.  Feldhaus,  TU  Dortmund   10  
  11. 11. Why  OCCI?  •  mature,  open  standard  •  several  implementa=ons   – Python,  Ruby,  Java   – OpenNebula,  OpenStack,  libvirt   – DeltaCloud  (under  development)  •  very  flexible,  extendible  •  supports  vendor  specific  features  •  working  on  support  for  monitoring  and  SLAs  
  12. 12. OCCI  Extension  mechanisms   Vendor Specific Vendor Specific Feature Feature Mixin Mixin OCCI Link Link CDMI OVF 12  
  13. 13. OCCI  Query  /  Filtering  Mechanisms  •  OCCI  allows  the  discovery  of  provider  specific   features  /  extensions   –   customer  queries  OCCI  endpoint   –   OCCI  endpoint  returns  e.g.  special  hardware  for  HPC   or  graphics  extensions  for  VMs  •  OCCI  allows  filtering  a  subset  of  resources  /   en==es   –   customer  wants  to  manage  only  high-­‐availability  VMs   or  VMs  with  4  cores   13  
  14. 14. OCCI/CDMI  Interoperability  Demonstra=on   3. Create OCCI Compute object 4. Deploy VM OCCI  Server   OpenNebula   7. Access VM using VNC 1. Create CDMI Container 5. Deploy VM 2. Upload Image VM   to Container 6. Start VM 5.a Get NFS export forCDMI ContainerCDMI  Server   NFS   5.b Mount NFS export VM  Host   Server   5.c Acess image from NFS directory
  15. 15. OCCI/CDMI Interoperability Demonstration: Credit:  F.  Feldhaus,  TU  Dortmund   15  
  16. 16. OpenSource  Repository  •  Ruby  OCCI  Framework  with  OpenNebula  3.0   backend   –   h`p://dev.opennebula.org/projects/ogf-­‐occi/wiki/  •  OCCI  /  CDMI  Client  „Pollux“   –   h`ps://github.com/gwdg/Pollux   16  
  17. 17. Other Work and Publications•  A. Edmonds, T. Metsch and A. Papaspyrou, Open Cloud Computing Interface in Data Management-related Setups, Springer Grid and Cloud Database Management, Jul. 2011.•  A. Edmonds, T. Metsch and E. Luster, An Open, Interoperable Cloud, InfoQ article, http://www.infoq.com/articles/open-interoperable-cloud•  OpenNebula Interoperability group formed.•  OGF Cloud Interoperability working group (CI-WG) forming.•  OGF WS-Agreement, WS-Negotiation have been published.•  Firewall Traversal Protocol in Public Comment.•  OGF Distributed Computing Infrastructure Federation and Federated Security groups started. © 2011 Open Grid Forum 17
  18. 18. Summary and Conclusions•  OCCI and other OGF standards are gathering substantial implementation experience in real-world cloud and grid settings.•  Production e-Infrastructure and commercially-oriented projects are implementing these in a wide range of real-world settings for user communities, writing usage guides, deployment scenarios and instructions.•  OGF is engaged at several levels in developer outreach, standards interoperability demonstrations and ongoing roadmapping activities in cloud computing.•  We do NOT view this work as in conflict with other standards efforts due to the differing demands and needs of our user communities; stand ready to engage in mapping activities and other mutual work as other standards mature. © 2011 Open Grid Forum 18
  19. 19. More information•  OGF Standards: E-mail: -  http://ogf.org/standards standards@ogf.org -  http://ogf.org/documents•  OCCI WG website: http://www.occi-wg.org•  OCCI specifications: (for other OGF standards, see OGF documents link above) -  Core: http://ogf.org/documents/GFD.183.pdf -  Infrastructure: http://ogf.org/documents/GFD.184.pdf -  RESTful HTTP Rendering: http://ogf.org/documents/GFD.185.pdf•  OCCI Mailing List -  http://www.ogf.org/mailman/listinfo/occi-wg © 2011 Open Grid Forum 19
  20. 20. Full Copyright TextCopyright (C) Open Grid Forum (2011). All Rights Reserved.This document and translations of it may be copied and furnished to others, and derivative works that comment onor otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in wholeor in part, without restriction of any kind, provided that the above copyright notice and this paragraph are includedon all such copies and derivative works.The limited permissions granted above are perpetual and will not be revoked by the OGF or its successors orassignees. © 2011 Open Grid Forum 20
  21. 21. Backup Slides•  Screenshots and project descriptions for recent implementations of OCCI and other OGF standards 21
  22. 22. OpenNebula OCCI v1.1 Ruby Framework © 2011 Open Grid Forum 22
  23. 23. (New,  skeleton...)  *   *  (Note:  “OCMI”  is  just  a  name  given  by  the   authors  to  this  sofware  project;  it  does  not   denote  a  name  given  to  any  current  standard.)   Developer:  Ilja  Stevenson  (VENUS-­‐C)   with  input  from  OCCI-­‐WG   23  
  24. 24. Web  site  s=ll  shows  old  version;  new  version   and  examples  under  ac=ve  development  at     h`p://dev.opennebula.org/projects/ogf-­‐occi/   by  Florian  Feldhaus  and  TU  Dortmund  group  OpenNebula  3.0  predates  OCCI  v1.1  specifica=ons;  new  code  work  in  progress!   24  
  25. 25. FIware Project and OCCI •  FIware is an FP7 project that will provide a platform for several large use case projects. •  Within FIware there is the Cloud Hosting chapter in which provisioning of compute, storage and networking services will be demonstrated and accomplished. •  OCCI will be one of the APIs used to manageh`p://www.fi-­‐ware.eu/   resources in the Cloud Hosting chapter.   25  
  26. 26. D-Grid Scheduler InteroperabilityInitiative and OGF Standards: D-­‐GSI  Project  aims  to  integrate  latest  OGF   standards  for  informa=on  discovery,  job   submission,  infrastructure  management,   basic  execu=on  services  and  SLA  agreement   and  nego=a=on  into  a  single,  modern  up-­‐to-­‐ date  implementa=on  involving  mul=ple   partners  and  the  poten=al  for  reuse.   26  
  27. 27. OCCI Tools from CompatibleOne: http://www.compatibleone.fr - Described at OWF, ETSI and OpenStack In Action conferences by Iain James Marshall (PROLOGUE). - C libraries, example code - LGPL+CC Licensed. - OCCI interfaces for OpenNebula, OpenStack, Azure and several others. © 2011 Open Grid Forum 27